Error after switching account on same laptop
A client has a laptop running RDM but they wanted to change the email address used for the Devolution account. As it's not possible to change the email address, the vault was exported, a new Devolutions account created with the plan to import the vault. Switching account wasn't easy in RDM - I could sign out of the old account and back in as new, but the old workspace was still there. Worked how to add a new workspace (host Url being the tricky point) but same error. In the end I renamed %localappdata\Devolutions and this went through the onboarding but same error.
If I install RDM on a new computer (virtual machine), it works fine so there is clearly something lingering from the previous account. BTW the previous account had a very different host address.
Status: 401
Response:
Stack:
at Devolutions.Hub.Clients.HubClient.PreLoginAsync(CancellationToken cancellationToken)
at Devolutions.Hub.Clients.HubClient.<PreLogin>b__36_0()
at Devolutions.Hub.Clients.HubClient.PreLogin()
at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.Connect(HubConnectionDataSource dataSource, String privateKeyBase64Url, Byte[] privateKeyBytes, Boolean useEncryptionService)
All Comments (6)
I'm pretty sure it's something do with authentication. I've tried clearing all data in Edge browser.
Hello,
We have created a ticket to investigate and fix this issue. We will keep you updated on any progress and contact you if we need more information.
Best Regards,
Michaël Beaudin
Hello @rob02,
To create a new workspace in RDM, you can click File -> Workspaces -> Add. The 401 could mean that the entered email is not in the Devolutions Cloud workspace. Could you confirm please that you have entered the right one?
Could you also please confirm the RDM version you are using?
Best regards,
Yes, that's the process I used to add the workspace. The correct address was entered. The version is 2026.2.9.0.
In the spirit of turn it off and back on again, I deleted the workspace entry and added it back. This has worked :-) The only obvious difference is that I left the name as "Devolution cloud". Previously, I'd changed it to "My cloud". Not sure this would have made any difference but don't want to remove and re-add to test as I've got it working :-)
@rob02 I am glad to hear that the issue has been resolved for you.
We will investigate on our end to determine why the email change feature is not working as expected.
Thank you for bringing this to our attention. Have a great day!
The other bit of maybe pertinent information is that the old account was using a personal cloud and I suspect, due to timing, that the new account is using the new cloud mechanism (I've seen the prompts but can't remember the new name). The old account was using https://hub.devolutions.com but the new one was https://fr.devolutions.app/guid format.
