Replies: 8 comments 4 replies
|
Same here. "Not Ready. Check your connection." Couldn't connect to my home PC anymore when I did so succesfully just an hour or two prior. Thought I'd remove the account and login again. Now, I just can't login with anything. Google gives an Error 400 at the end of the process and Github gives a 502 Bad Gateway. Using 1.4.5 (last version I'm willing to use for personal reasons). |
|
I am getting Failed to secure tcp: deadline as expired. But I am on a purely local connection. Have tried uninstalling/reinstalling Rustdesk on both ends of the connection. I do not have a Rustdesk server running - this is strictly point-to-point. All three of my local Rustdesk connections have stopped working with this error. They worked yesterday. |
|
I'm seeing the same "Failed to secure tcp: deadline has expired" message when I try to connect to a system I know is online. Additionally, none of my saved systems show as online - they all have the orange dot. I just noticed now that the bottom of the main window also has "Not ready. Please check your connection." |
Didn't notice that before, but it's true for me too. |
|
Mysteriously started working 9/30/26 10PM Pacific time. I changed nothing. |
|
Me too facing: "Failed to secure tcp: deadline has elapsed". Never faced this till now. |
|
Same for me! Today 7-8AM (mesz) everything worked. 9:40 AM right now everything is down. |
|
Same here!! Any news on this? |
|
Regard from Italy. Rustdesk report to me "Not ready. Verify your connection" PS C:\WINDOWS\system32> Test-NetConnection rs-ny.rustdesk.com -Port 21116 ComputerName : rs-ny.rustdesk.com PS C:\WINDOWS\system32> Test-NetConnection rs-ny.rustdesk.com -Port 21117 ComputerName : rs-ny.rustdesk.com Marco |
|
Same here from Italy. |
|
Why does it say "Check your connection"? Should say "Rustdesk servers are down" in app. |
|
Down.rustdesk reports their servers are down, though the problem seems to be resolving slowly. |
Uh oh!
There was an error while loading. Please reload this page.
Same symptom here. Measured it, and it's not client-side:
rs-ny.rustdesk.com:21116(signal) → 19/20 nodes OK (13–2140 ms)rs-ny.rustdesk.com:21117(relay) → 0/20 nodes, 19× connection refusedrs-ny.rustdesk.com:21119(WS relay) → 0/20, 16× connection refusedConnection refused= the host answers but nothing is listening on that port. Same machine serves 21116 fine, so it's not network/firewall/DNS — the relay process (hbbr) is simply not running.Also:
rs-sg,rs-cn,rs.rustdesk.comno longer resolve. Only one public node left.Reports: signal · relay · ws
It worked for me ~15 min before failing, same account/devices — so nothing changed on my side.
Is the relay down, or being decommissioned? And is there any status page?
status.rustdesk.comdoesn't resolve, so there's currently no way to track it.All reactions