Updated to 2022.3.24.0 - Now unable to connect to Ultra VNC clients

I reverted to 2022.2.29.0 and have no issues

Hello

Thank you for reporting the issue and sorry for the inconvenience. We are looking into that and I'll write back with an update.

Thanks and kind regards,

Hello again

I did some investigation and saw that the error message is coming from inside the DSM encryption plugin rather than UltraVNC itself.

Do you use a client authentication key? Normally this is a key pair generated on the server; and the private key file is copied to the client.

Where is your client authentication key (the .pkey file) file located on the client computer (the one running RDM)? In the move to 2022.3.x some installation paths have changed in RDM so I'm wondering if your key file is no longer in the expected location.

Please don't hesitate if you have any questions or further comments

Thanks and kind regards,

Hello again

I've done some more testing on my side and believe this to be the case.

After upgrading to RDM 2022.3.x, take the following steps:

• Open C:\Program Files (x86)\Devolutions\Remote Desktop Manager
• (Note that the path might be different if you don't use "C:" or the free version will be "Remote Desktop Manager Free")
• Locate any files with the ".pkey" extension
• Move or copy the ".pkey" files to RDM's new home, which will be C:\Program Files\Devolutions\Remote Desktop Manager
• Note that the new path is "Program Files" rather than "Program Files (x86)" and there is no longer any distinction between the Team and Free editions

When using client-server key pairs, UltraVNC looks in the current application directory for the client private key files. Although you had this setup correctly for the 2022.2.x versions, the installation path for RDM changed in the 2022.3.x version. So the files need to be relocated accordingly.

Please don't hesitate to post back if you have any trouble following these steps, additional questions, or if this does not resolve the issue.

Thanks and kind regards,

Thank you, Richard. I do have a PKEY located here: "C:\Program Files\uvnc bvba\UltraVNC\GMMFG_Viewer_ClientAuth.pkey"

I will copy to the new location and see how it goes!

Hello again

That confirms why the external UltraVNC Viewer is still able to connect.

From further investigation; it looks like resolution of the private key file is baked into the DSMPlugin itself. The plugins are closed source so we can't control them; however in our own FreeVNC application we can load them from arbitrary locations. I'll bear this in mind for future improvement (it would be nice to locate the DSMPlugin and private keys separately from the RDM installation directory, to prevent issues like this arising in future).

Thanks and kind regards,