-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"deadline has elapsed". Can't connect to remote server #732
Comments
honestly, i have no clue for now before i can reproduce. |
End user here with seeing similar issue. @rustdesk, is there something you recommend we can do to troubleshoot this? thank you |
I have no clue either before I can reproduce. Help wanted, looking for contributors. |
One additional information: this is apparently an issue with the Windows client. I've successfully connected to a linux box on. a different network using a Mac. |
Have same issue when connecting from windows (10) to linux client (Linux mint) |
I had the same issue after a couple days of use with no issues, but what fixed it for me was a simple Uninstall and Reinstall. I'm also running Windows 10. |
I had the same issue on Windows 11. I uninstalled client, then installed again and everything works fine. |
Reinstalled as well but no go. |
Reinstalling without uninstalling first, doesn't help. |
I've deployed the server again, uninstalled rustdesk and issue remains unfortunately. Using the Web functionality also returns the same behavior. Trying to be clearer:
Issue persists even with OpenVPN connection between networks. |
Interesting |
I am experiencing same issue with two computers. One is Windows 7 and another is Windows 10. If I try to reach any of these computers from Windows client, keep getting "deadline has elapsed" message with [2022-08-09 21:53:55.693582 +03:00] INFO [src\client.rs:341] 26.0081ms used to establish connection logs, but I can successfully connect either of these machines from web client (web.rustdesk.com). If there is any way I can help please let me know. |
@21pages similar to 10054 problem |
Can I connect to your computer for diagnose? password is not needed, just check the connection initialization process. |
Sure, it's running our selfhosted server but i can share needed info with you, could you share an email address with me? |
My email is pages21@163.com . Your help will be important to us. |
Sent connection info to your mail address. |
Hi! Newbie to Rustdesk. I'm having the same problems connecting 2 computers using Windows 10. When I try to connect to the remote computer from Rustdesk WEB, it works perfectly, but when I try to connect from my windows computer, I get the mentioned error (deadline has elapsed). Where can I check the logs? What can I try to fix it? I'll try to reinstall. |
Go to discord please, there may be some one can help you. |
Had a struggle too, with self host and clients in same LAN - there is some confusion with LAN and WAN addresses. |
good try |
Didn't work for me either. LAN to same LAN connections worked most of the time but Internet connections rarely connected. Got rendezvous, offline, and deadline errors. All working and fast when I finally got my own server running over gig fiber. The recent Anydesk debacle has RustDesk servers overloaded. Run your own server or don't bother. The current instructions are too sparse for all but the Internet mavens to get working. Own server will get easier when more people get it working and write better guides. |
The issue occurs with self hosted servers. |
Like I said in the post, at least in 1.1.9. The issue occurs also in public servers. |
From discord:
|
I get the deadline has elapsed message on one out of 6 computers while self hosting. It doesnt happen on that connection if its inside the LAN but when I attempt the same connection ouitside the LAN it doesn't connect and gives that message. |
After adding more peers and more testing I ended up with a few pairs on different LAN that wouldn't connect. Error is "deadline has elapsed." Seems to be routers specific as all pairs behind the same two LAN cannot connect yet I have other pairs on one same and one different LAN that do connect. No home peer connects to any peer at office 2. Any home peer connects to every peer at office 1 and 3. Office 2 connects to office 1 but not office 3 or home. Office 1 hosts the server and connects to all. Office 3 connects to office 1 or home but not office 2. So far as I can tell connections always work between peers in same LAN. Home: Cable Fortigate 60D Upgrading both peers to 1.2.0 nightly fixed the problem, or at least fixed the problem enough that they can connect. On first connect I get error "Connection reset by peer (os error 104)". Something is written to the Linux saved session Own server or public server made no difference. Windows 1.1.9 or Linux 1.1.9 have the same connection problem. Moving own server to subnet not accessible by office 1 peers made no difference. No log entries appear in hbbr server for failed connections. May be related to #1597 Edit: I moved the laptop from Home to Office 1 where everything connects. It now connects to Office 2 with version 1.1.9. |
Can you try out nightly build? There is a fix, though not good enough, not sure if it works in your scenario. https://github.com/rustdesk/rustdesk/releases/tag/nightly |
Hi, I have the same issue here (self hosted server), multiple sites connected with VPN...SITE A to Site B we got the deadline has elapsed error... Tested on multiple PCs in SiteA without success |
Settings that work with opnsense:
|
What ports should be forwarded for normal work? And why it work on Common Servers but not work if it local (under NAT)? Common Servers under the same NAT. And in local net where this server placed - it work OK, but outside of NAT it's not... but it see units. Problem just when I try connect to outside. |
Describe the bug you encountered:
It does not connect to RustDesk instances that are on different network
How did you install
RustDesk
?Github release 1.1.9. Tested multiple computers, Windows and Linux. The PC's I want to connect to are all Windows machines.
log/connect
I've tried with the default relay public servers and also with the selfhost server, same results. Only working for computers in the same network.
I've tried adding an allow rule in windows advanced firewall.
While connecting if flashes an error for about 0.5s that says: "deadline has elapsed".
The text was updated successfully, but these errors were encountered: