-
-
Notifications
You must be signed in to change notification settings - Fork 8.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
Connection error : Connection reset by peer OS error 104 #1597
Comments
try this master build |
I'm also facing the exact problem.
Would you mind doing some explanation before I try that? BTW, I'm on Linux... |
This problem has been fixed on master branch. I'll put a linux build on that link later. |
Okay, thanks for the fix. I'm using my Linux machine to setup a server and letting my windows enjoyer friend using mine, for a better direct connection. Does he need to update his client software or do I need to update my Linux server for the fix to work? |
Just update client, but can't connect by direct connection. It's solution is changing direct to relay. |
thanks, i'll try |
Can you try out nightly build? There is a fix, though not good enough, not sure if it works in your scenario. |
The nightly build works better, but clicking or using the keyboard causes the os error 104 |
What env on controlled side? |
Same thing here (on debian unstable), with latest nightly .deb and APK.. this comes up in the system log:
|
Surprisingly, anydesk has the same problem right now when it previously worked. Their hint to
helped.. both devices are connected to an OpenWRT router (phone via wifi, desktop via LAN) but haven't changed the configuration for quite a while.. 🤔 |
@21pages let's add this also. We have "always use relay" already, for us, it should be try "always use relay". |
Could you please try out the nightly build? add "/r" suffix to the id. https://github.com/rustdesk/rustdesk/releases/tag/nightly |
please try out the new fix |
It's late, but those patches did indeed fix the error 104 that I was having. |
Hi, just got twice issue get connected to client. I dont know what its, but i think related to security because its somehow blocked by router/firewall.
The day before its okay, nothing got wrong, but accidently its cant connect to a client, others clients is ok.
Im using debian on both side and installed correctly on x11 desktop.
Rustdesk version 1.1.9
The text was updated successfully, but these errors were encountered: