Alex.kletzl

Hi @Alex.kletzl,

It looks like the issue is related to your DVLS system settings enforcing locking options on Workspace. To fix this, make sure your new Workspace installation uses the same enforced settings. We’ll also look into improving how this is handled on our side.

Best regards

@Marc-Olivier Lalonde

Your right.

Case closed.

Would be nice if the app clould sync the settings on the first connect.

Looks like workspace is trying to open a Browser tab but cant do it.

Hello,

new installs of the Workspace app (windows) dont connect to the DVLS (Server is unreachable - requies additonal auth)

evene IOS APP not connecting (Server is Locked)

RDM Works fine and Browser works also fine.

Old installs that are upgraded work fine

Hello,

I am currently having an issue with the new Workspace app.

The app is not able to connect to my Hub Business environment. It always fails with a generic “can’t connect” type of error.

What is strange is that everything else seems to work normally:

• DVLS is working fine

• Hub Personal is also working fine

• only Hub Business does not connect through the new Workspace app

Because of that, it does not look like a general connectivity issue on my side. At the moment, the problem appears to be specific to the Workspace app in combination with Hub Business.

Has anyone else seen this behavior?

Is there a known issue, or are there any logs, settings, or troubleshooting steps I should check first?

Thank you.

Hello

That's really strange. What specific version of RDM do you have? It it at least 2026.1.9 (I want to understand you're not using an earlier beta). What kind of data source do you use?

In terms of getting things unblocked for you right now, do you have more than one jump host? On the client-side RDM, on the Jump setting page for the Jump Host RDP connection please try changing the "Jump Approach" to "Legacy". Please try it on at least one Jump Host and let me know if it unblocks things for you.

And let me know if something isn't clear or you have another question

Thanks and kind regards

@Richard Markiewicz

Hi Richard,

Argh... just lost my Reply-Window... okay propably better, that the shorter Reply with lover prose-Level :-), because running out of spare-time :-)

• Data Source - XML Local

• Upgrade from 2025.3.32.0 no Beta, never ever...unfortunately not the time for that.

• RDM runns on both Machines (Jumpserver and my Workstation) as "Portable" (has to be), you know, this override.cfg - Version

• Tried the Legacy, I think its Properties (for the jumpserver) -> Jump -> Is Jump host -> Legacy restarted everything (RDM; Jumptool etc.) nop.. neither a SSH-Jump nor a RDP-Jump works

I gave it a try Client 2025.3.32.0 -> Jump Host 2026.1.10.0 this is working, seems you have some trouble with 2026.1 -> 2026.1 (on 2025.3. is no Legacy-Switch ;-))

Normally I would check it with some wireshark to see what traffic is running, if there is some sort of handshake, but running out of time for Debugging... I give it a try later the day...

As Alex mentioned, rollback all to 2025.3 and there is not a problem... what is not suppring :-)

Since we have two Posts with the same trouble, perhaps its possible to join them?

cheers

Matthias

@matthiasgruber

Hi Matthias,

in my topic Devolutions mentioned that this is a known issue atm and a Fix is on its way.

I Downgraded jump host to 2025 version an it works again. (Client still 2026)

Hi Richard

Alex has posted more than me (a new post).. But I did the same... concerning your questions, I will do my best to fullfill them asap, hopefully on Monday.

cheers

Matthias

@matthiasgruber

I Downgraded jump host to 2025 version an it works again. waiting for new releases

Hello,

after the update to version 2026.1.10.0 our jump host doenst work anymore.

Agent is not connecting.

Error log

[06.03.2026 09:21:38] RDMJump: 2112198948928

[06.03.2026 09:21:40] Ungültige Serialisierungsassembly: der erforderliche Typ Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializerContract ist nicht in der generierten Assembly 'RemoteDesktopManager.Core.XmlSerializers, Version=2026.1.10.0, Culture=neutral, PublicKeyToken=null' vorhanden.

[06.03.2026 09:21:40] bei System.Xml.Serialization.TempAssembly.GetTypeFromAssembly(Assembly assembly, String typeName)

bei System.Xml.Serialization.TempAssembly.LoadGeneratedAssembly(Type type, String defaultNamespace, XmlSerializerImplementation& contract)

bei System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)

bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.GetSerializer(Type type, String nameSpace)

bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SaveObjectToBytes(Object value)

bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SendMessage(JumpMessage message)

[06.03.2026 09:21:47] RDMJump: Acknowledge timeout

[06.03.2026 09:21:47] Started

[06.03.2026 09:34:13] RDMJump: 2082568376496

[06.03.2026 09:34:14] Ungültige Serialisierungsassembly: der erforderliche Typ Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializerContract ist nicht in der generierten Assembly 'RemoteDesktopManager.Core.XmlSerializers, Version=2026.1.10.0, Culture=neutral, PublicKeyToken=null' vorhanden.

[06.03.2026 09:34:15] bei System.Xml.Serialization.TempAssembly.GetTypeFromAssembly(Assembly assembly, String typeName)

bei System.Xml.Serialization.TempAssembly.LoadGeneratedAssembly(Type type, String defaultNamespace, XmlSerializerImplementation& contract)

bei System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)

bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.GetSerializer(Type type, String nameSpace)

bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SaveObjectToBytes(Object value)

bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SendMessage(JumpMessage message)

[06.03.2026 09:34:21] RDMJump: Acknowledge timeout

[06.03.2026 09:34:21] Started

[06.03.2026 09:38:20] RDMJump: 2557481874784

[06.03.2026 09:38:20] Ungültige Serialisierungsassembly: der erforderliche Typ Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializerContract ist nicht in der generierten Assembly 'RemoteDesktopManager.Core.XmlSerializers, Version=2026.1.10.0, Culture=neutral, PublicKeyToken=null' vorhanden.

[06.03.2026 09:38:20] bei System.Xml.Serialization.TempAssembly.GetTypeFromAssembly(Assembly assembly, String typeName)

bei System.Xml.Serialization.TempAssembly.LoadGeneratedAssembly(Type type, String defaultNamespace, XmlSerializerImplementation& contract)

bei System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)

bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.GetSerializer(Type type, String nameSpace)

bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SaveObjectToBytes(Object value)

bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SendMessage(JumpMessage message)

[06.03.2026 09:38:26] RDMJump: Acknowledge timeout

[06.03.2026 09:38:26] Started

I Have already reinstalled cleanly everything nothing helps here.

Also switching the rmd jup to legacy doenst help.

I Updated also everything from .net no help

Hi,

The upcoming version of Devolutions Workspace Browser Extension will include a fix for both your issue.

Best regards,

Any news on the Update? When?

Hi,

The upcoming version of Devolutions Workspace Browser Extension will include a fix for both your issue.

Best regards,

Great news, thanks a lot. Can't wait for the Update to finally use it

I just set up another Hub Personal account with another mail address for other stuff. Here, everything works just fine!

Cloud it be about the mail domain? My personal Hub mail which doesn't work need to be whitelisted

Hi,

I will send you a Direct Message with steps to follow that might resolve your issue.

Best regards,

HI I have the Exact same problem can you dm me the solution too?