RDM 2022.1.12 cannot authorize in Devolutions Server 2022.1.7
RDM 2022.1.12 cannot authorize in Devolutions Server 2022.1.7
Hi,
Yesterday we updated Devolutions Server to the latest version 2022.1.7. The update was successful, without a single problem. To do this, I updated RDM to version 2022.1.11 and I am not able to log in to Devolutions Server with it. When start authorization process, RDM opens default browser and in this browser is showing error page. As you can see below.
At the same time, when I go with the same browser to the Devolutions server's web console, I log in without any problems.
I tried to log in from several computers and always the same result.
When I try to connect to the our test Devoutions Server from the same RDM, everything works.
I also tried changing the default browser and without any add-ons and it didn't help.
Today I installed the RDM update on 2022.1.12 and it didn't help. Thus, authentication on one of the computers worked until the computer was restarted. Then not again.
I have tried downgrade RDM version to 2021.2.28 and after downgrade I am able to authorize to our production Devolutions Server.
Other information: We have Devolutions server for production environment installed. It is built of 2 Devovolutions servers and a DB cluster. Access to Devolutions Servers is balanced using a balncer.
We also have 1 test Devolutions server without balanced access.
Furthermore, I have Windows 10 20H2 installed on all computers with all Windows updates. I have MS Edge as my default browser.
We have chcecked logs in Devolutions Server and we are not able to find any event about this casue.
Is it possible to find a log that would more precisely why I can't log in or any advice?
Thank you.
dev_auth.jpg
All Comments (5)
I was able to login up to update to version 2022.1.12.0. Now I am in the same issue :-(
Hello,
Have you both verified if the URL set in the DVLS data source in RDM is the same as the Access URI set in the IIS tab of the DVLS settings? Please note that this is case sensitive.
@jvacha As you are using DVLS behind a Load Balanced environment, ensure that you have set the Access URI to reach the main node of the Load Balancer.
Best regards,
Érica Poirier
Hello Erica,
thank you for your response.
All URIs are set same like in Access URI and RDM. Balancer works correct.
We have set additional Access URI to Devolutions server. We added the FQDN of each server to the Access URI. Then we tried to connect to individual DVLS servers and one works fine and the other returns this error. After that We tried stop DVLS server with error and we tried connect to working DVLS server throught balancer and this work fine too.
Tomorrow we will compare the settings on both servers.
Best regards
Jakub Vácha
Hello Erica,
We tried install update DVLS 2022.1.7.0 again on problematic server. We did not notice any problem again during the installation.
After installing this update, the server started working. Now the authentication process is working fine on this server.
We didn't find any error in event logs before installation this DVLS update.
Best regards
Jakub Vácha
Hello Jakub,
Thank you for your feedback and glad that the new installation is now working properly.
Best regards,
Érica Poirier