Slowdowns or connection timeout message when connecting to a Devolutions Server workspace

Connecting to a Devolutions Server workspace with Remote Desktop Manager can sometimes be slow. There are multiple ways to resolve this issue. The error message related to this problem should look like this:

System.TimeoutException: The request timed out.
at Devolutions.Server.ApiWrapper.RDMSWebClient.RunSynchronous[T](Task`1 task)
at Devolutions.Server.ApiWrapper.RDMSWebClient.GetPublicWebInstanceInformation()

Disabling Internet connection

When in an environment where internet access is not allowed, enable No Internet connection in File – Settings – Advanced. Doing so prevents Remote Desktop Manager from making calls to the internet that could cause timeouts or slowdowns.

By enabling No Internet connection, some security services will also stop working (e.g., Compromised (Pwned) password check or Show compromised password (pwned) in the Entry security analyzer).

Disabling certificate revocation checks

Disable Enforce certificate revocation check found under File – Settings – Security. This prevents Windows from trying to reach the revocation servers configured in the certificate. In most cases, revocation servers should be allowed through the firewall unless they are also managed locally. In specific situations this can resolve the Unable to connect to your data source or Devolutions Server did not respond in time error messages.

The Windows online certificate revocation check will not use configured proxies on the host for security reasons.

Alternatively, enabling Enhanced certificate validation can prevent disconnects in some cases. Activating this feature causes Remote Desktop Manager to validate certificates using a different method, potentially circumventing the source of the slowdowns.

Using the built-in Performance profiling to troubleshoot connections

Use the Remote Desktop Manager Profiler to diagnose certificate validation length.

1. Click on the Help tab and select the Profiler.
2. Set the Debug level to 4.
3. Go to the Debug only tab and click the ellipsis button (...).
4. Check the Stop watch option.
5. Lauch a remote connection and look for the Certificate Validation – Chain.Build line. This will provide the time it took to connect in milliseconds (ms).