Certificate issue with RDM 2025.3 beta

Hello,

Thank you for reaching out!

My name is William, and I'm here to assist you in any way I can.

This error is related to the certificate attached to your Devolutions Server. It looks like RDM sees that the URL used by the Devolutions Server doesn’t match the certificate’s CN/SAN issuer. Could you confirm that the URL used by the Devolutions Server matches the Hostname listed in the certificate?

Best regards,

Hello,

Thank you for reaching out!

My name is William, and I'm here to assist you in any way I can.

This error is related to the certificate attached to your Devolutions Server. It looks like RDM sees that the URL used by the Devolutions Server doesn’t match the certificate’s CN/SAN issuer. Could you confirm that the URL used by the Devolutions Server matches the Hostname listed in the certificate?

Best regards,

@William Alphonso
Hi William

Yes, I can confirm that the URL used for our Devolutions Server matches the hostname within the certificate. The Edge Browser or any other browser does not complain about the certificate not being valid.

It's a certificate of our internal Certification authority, the root Certificate is available on the machine.

And as I told, all 2025.2 version do not show any error.

Best regards

Hello,

Thank you for reaching out!

My name is William, and I'm here to assist you in any way I can.

This error is related to the certificate attached to your Devolutions Server. It looks like RDM sees that the URL used by the Devolutions Server doesn’t match the certificate’s CN/SAN issuer. Could you confirm that the URL used by the Devolutions Server matches the Hostname listed in the certificate?

Best regards,

@William Alphonso


Hi William

Meanwhile I guess I figured out what the issue is. Our access URI has uppercase and lowercase letters but not within the domain, only after the domain.

Changing the Access URI to all lowercase letters seems to fix the issue, but that's not a solution, since I would have to update all the configurations on our RDM user installations.

And to be honest, it does not make any sense to check for the part behind the FQDN if it's "matching" the certificate, since the certificate only contains the FQDN (in lowercase) of the server, nothing behind.

It seems that RDM 2025.3 has changed something in certificate checks, because RDM 2025.2 does not complain about this uppercase/lowercase issue.

Hello,

Thank you for the confirmation. An internal ticket has been opened with our development team to assess potential solutions. However, it's important to note that we are unable to provide a precise release date due to the intricate nature of our release process, which encompasses Build, Quality Assurance, and Release stages. Rest assured that we will be in touch as soon as we have an update to provide.

In the meantime, if you'd like to stay updated on the latest fixes, improvements, and release notes, you can access our Release Notes page by following the link below:
RDM Windows - https://devolutions.net/remote-desktop-manager/release-notes/.

Best regards,

Hello,
any update on that topic?

Hello,

Sorry for the delayed response. This should be fixed in the latest version of Remote Desktop Manager (RDM).

We recommend upgrading your RDM to the latest version and verifying if you are still experiencing the issue.

Best regards,

Hi,
i updated today from 2025.2 to 2025.3 and had the same issue.
I had to add the access uri in lowercase in Devolutions Server Console and the Redirect URI on the Entra ID site.
After that everything worked for me. If you add the lowercase urls to the existing configuration, then you don't have to change it in the clients configuration.

Hello,

Thank you for the confirmation. I'm glad you were able to fix the issue.

I will mark this case as resolved.

Best regards,