RDM hangs when any action is done - often when initially opening and for some reason not loggin in in time?!
So, up to the super switch to the hub, everything worked perfectly with devolution based file db.
I have 3 laptops, often connecting from one laptop or another based on where i am during the day (at home, at my parents house or at my girlfriends place).
I'm not worried about the access to the laptops as that is not the issue...the issues is that ever since forced to migrate to the hub, even opening the app is like a roulette because it either is able to connect or not. if it does not, it hangs (to be read as freezing) for more than a minute before any button would work (like the refresh button in order to reconnect. I know its not the password being the issue, cause from time to time it gives out and error about http something and could connect because some 100 seconds passed... will update with a print screen the first time I'm going to see it after this initial posting...
Is there any way i can debug this?
Thank you all for your time and replies...
Update 1:
This is a new one:
===
at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.AuthenticationHelper.SendWithNtAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean isProxyAuth, HttpConnection connection, HttpConnectionPool connectionPool, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.AuthenticationHelper.SendWithAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean preAuthenticate, Boolean isProxyAuth, Boolean doRequestAuth, HttpConnectionPool pool, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at Devolutions.RemoteDesktopManager.Business.DataSources.HubClientDelegate.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
at Devolutions.Hub.Clients.HubClient.DeleteOpenEntryAsync(Guid openEntryId, OpenedEntry openEntry, CancellationToken cancellationToken)
at Devolutions.Hub.Clients.HubClient.<>c__DisplayClass368_0.<<DeleteOpenEntry>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Devolutions.Hub.Clients.HubClient.DeleteOpenEntry(Guid openEntryId, OpenedEntry openEntry)
at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.CloseConnection(Guid dataSourceID, LogConnectionClosedInfo log)
at Devolutions.RemoteDesktopManager.Business.DataSources.HubLogSubDataSource.LogConnectionClosed(LogConnectionClosedInfo log)
===
comms-breakdown.png
Hello,
This is very strange.
What version of RDM are you running?
Best regards,
Jeff Dagenais
Hi Jeff,
According to the about submenu, running 2024.1.30.0 64-bit
Am i to assume, you saw something in the stack trace error?
Update 2: This is the issue i was complaining initially:
System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
---> System.TimeoutException: A task was canceled.
---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.AuthenticationHelper.SendWithAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean preAuthenticate, Boolean isProxyAuth, Boolean doRequestAuth, HttpConnectionPool pool, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at Devolutions.RemoteDesktopManager.Business.DataSources.HubClientDelegate.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
at Devolutions.Hub.Clients.HubClient.GetHealthzAsync(CancellationToken cancellationToken)
at Devolutions.Hub.Clients.HubClient.<GetHealthz>b__230_0()
at Devolutions.Hub.Clients.HubClient.GetHealthz()
at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.Connect(HubConnectionDataSource dataSource, String privateKeyBase64Url, Byte[] privateKeyBytes, Boolean useEncryptionService)
at Devolutions.RemoteDesktopManager.Business.DataSources.HubWebAuthentication.Login(ServerConfiguration serverConfiguration)
at Devolutions.RemoteDesktopManager.Business.DataSources.HubConnectionDataSource.Login()
After this, if i attempt to "refresh" takes about 2 to 3 minutes to actually do something aka login (again) and imediately after login is successfull, it freezes over for another 2 to 3 minutes.
I hope with every update since the migration that this would get fixed. :(
unable-to-connect-to-data-source.png
Hello,
Thank you for your reply,
I've not seen other reports of such a behavior, Would it be possible for you to create a portable installation of the latest version of RDM and see if this issue still occurs? To do so, you will need to do the following:
1- Download the .zip file below:
https://remotedesktopmanager.com/home/thankyou/rdmbin
2- Create a new folder on your Desktop
3- Extract the content of the .zip file into the folder created at #2
4- Go to this folder once the .zip file has been extracted and run remotedesktopmanager.exe
5- Connect to your data source
I understand that you're encountering this issue on multiple workstations, but I believe this test will be helpful, as it uses a fresh configuration of RDM.
Best regards,
Samuel Dery
Hi Samuel,
I've done what you said...But...
This is what I'm getting after I add the data source...
System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
---> System.TimeoutException: A task was canceled.
---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.AuthenticationHelper.SendWithAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean preAuthenticate, Boolean isProxyAuth, Boolean doRequestAuth, HttpConnectionPool pool, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at Devolutions.RemoteDesktopManager.Business.DataSources.HubClientDelegate.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts)
at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
at Devolutions.Hub.Clients.HubClient.GetHealthzAsync(CancellationToken cancellationToken)
at Devolutions.Hub.Clients.HubClient.<GetHealthz>b__230_0()
at Devolutions.Hub.Clients.HubClient.GetHealthz()
at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.Connect(HubConnectionDataSource dataSource, String privateKeyBase64Url, Byte[] privateKeyBytes, Boolean useEncryptionService)
at Devolutions.RemoteDesktopManager.Business.DataSources.HubWebAuthentication.Login(ServerConfiguration serverConfiguration)
at Devolutions.RemoteDesktopManager.Business.DataSources.HubConnectionDataSource.Login()
I've replicated the same behavior to one of the other 2 computers I use using the same portable installation procedure you suggested.
If I click ok on the pop-up window having the above error message, then refresh in the main window, it just...freezes...for a while...(haven't timed it) then the same error message pops up - so at this point I'm guessing its getting stuck somewhere after my authentication takes place on web step and downloading the content data from my hub thing.
Some things to mention, the only common denominator between all three locations is Cloudflare DOH DNS service. Cant see how this is connected to the above issue, but I though it worth mentioning. But then again, no other service I use didn't encounter any issue until now. Plus, I've been having the DOH setup for a few years now and that included the pre-hub era whiteout any issues.
PS: Sorry for the late reply. Been a few hectic days on my end... Also, I plan on testing the Linux version of the RDM as well as the mobile version using a Samsung Dex setup
Hello,
Thank you for your reply,
No problem, I see, that is indeed odd, when you encounter this issue are you able to access the Hub from the web interface without any issues?
https://hub.devolutions.com/
Let me know,
Best regards,
Samuel Dery
Hi Samuel,
I'm afraid I haven't noticed any issues with the hub website, meaning no observation has been made for this until now.
Will update if I notice something peculiar.
Best regards,
Bogdan
Hello Bogdan,
Thank you for your reply,
No problem, I will wait for your return regarding this,
Best regards,
Samuel Dery