Failed to connect to rs-ny.rustdesk.com:21116 #5538
Replies: 41 comments 40 replies
-
|
Build your own server instead. |
Beta Was this translation helpful? Give feedback.
-
|
Get a free docker container https://aws.amazon.com/en/free/containers/ then install your own server: https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/docker/ |
Beta Was this translation helpful? Give feedback.
-
First, learn how to install docker on your system, if you're using Ubuntu, it is convenient to install it though snap. sudo snap install dockerFeel free to asking more server or Docler problems. |
Beta Was this translation helpful? Give feedback.
-
|
Seems like AWS servers have limited hours for free. AFAIK 1 year has more than the free 750 hours. |
Beta Was this translation helpful? Give feedback.
-
|
750 hours a MONTH, and one year for free. And yes, it works flawless - at this moment - while rs-ny.rustdesk.com is down. Point ID-Server and Relay-Server in the network settings to your AWS host on ALL MACHINES running rustdesk, and you're back online. |
Beta Was this translation helpful? Give feedback.
-
|
I could have swear it didn't say monthly. Ended up setting it in up in a windows PC + port forwarding + dynamic dns. |
Beta Was this translation helpful? Give feedback.
-
|
I am also getting this error "Failed to connect to rs-ny.rustdesk. com:21116" today, Jan 31st, 2024. Rustdesk worked perfectly 12 hours ago, and now is non-functional. I have tested on versions 1.2.3-1 and 1.2.3-3 and both have the issue. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having exactly the same problem - worked fine a few hours ago and now get "Failed to connect to rs-ny.rustdesk.com:21116: Please try later". I switched to the newest version because the prior installation also stopped working. Can anyone suggest an alternative service? |
Beta Was this translation helpful? Give feedback.
-
|
我今天刚玩这个，我是类似情况，是不是还要搞什么ID服务器API之类的 |
Beta Was this translation helpful? Give feedback.
-
|
@xiadaren HBBS(ID) HBBR(Relay 中繼) @RDG58 host your own server instead to avoid this problem. |
Beta Was this translation helpful? Give feedback.
-
|
same here |
Beta Was this translation helpful? Give feedback.
-
|
i have the same problem. |
Beta Was this translation helpful? Give feedback.
-
|
I'm hoping this gets resolved shortly, it's affecting quite a few of us. |
Beta Was this translation helpful? Give feedback.
-
|
same here... hope they will fix it soon - thanks |
Beta Was this translation helpful? Give feedback.
-
|
yo igual pense que era mi pc pero por lo que veo es el servidor. el problema lleva mas menos 12 horas. |
Beta Was this translation helpful? Give feedback.
-
|
They still being DDoS |
Beta Was this translation helpful? Give feedback.
-
|
same here！ |
Beta Was this translation helpful? Give feedback.
-
|
same here! |
Beta Was this translation helpful? Give feedback.
-
|
Yup, same here....I have been planning on building a server for my connections out for a while now, maybe this is the time to do that...but in the meantime hopefully this gets sorted soon |
Beta Was this translation helpful? Give feedback.
-
|
Yep, downloaded teamviewer now to survive while i learn and try to set a personal server Ended up setting it up in windows. Wasted hours following the self host guide. Then being curious executed the setup executable (which was never mentioned in the guide) and it set itself up in 5 minutes... Only had to add the public key manually at the end. |
Beta Was this translation helpful? Give feedback.
-
|
5 minutes and it was up and running? What version of the server did you use? 1.1.10-3? |
Beta Was this translation helpful? Give feedback.
-
|
More or less. I went to the download site mentioned in the guide and downloaded the last package for windows. Then executed the "RustDeskServer setup.exe". The installer version is 1.1.10.0 (from details tab), the rar didn't have the version on the filename. You need to have the PC visible from the internet, that means static IP (or dynamic DMS) and portforwarding, that you have to do by yourself (I did it previously for Jellyfin). |
Beta Was this translation helpful? Give feedback.
-
|
I've done setups with NoIP and DynDNS + port forwarding so it shouldn't be too bad. I'm wanting to do a Linux setup but Windows is more available at my org. I'll have to try with both and see which works better for our needs. |
Beta Was this translation helpful? Give feedback.
-
|
same here! |
Beta Was this translation helpful? Give feedback.
-
|
Using direct IP access can solve this problem temporarily. |
Beta Was this translation helpful? Give feedback.
-
|
You need to input IP in Control Remote Desktop input box. |
Beta Was this translation helpful? Give feedback.
-
|
I think this man has no idea how a server works. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, It works for local connections and for computers than can be exposed to internet through port redirection (i use brynhildr for that though). But for the computers at my lab, no luck :( |
Beta Was this translation helpful? Give feedback.
-
|
No, EZElkins is right. If a machine is on the >same network< as your PC, type in it's IP into the Control Remote Desktop field and it will connect. |
Beta Was this translation helpful? Give feedback.
-
|
@EZElkins is right, @playbackandrewind need to do some research on this software. |
Beta Was this translation helpful? Give feedback.
-
|
i am facing same issue |
Beta Was this translation helpful? Give feedback.
-
|
Same Problem here 🙁 |
Beta Was this translation helpful? Give feedback.
-
|
Uh oh, 9:14PM CST...I see it's up? |
Beta Was this translation helpful? Give feedback.
-
|
Oh ...It's back!? |
Beta Was this translation helpful? Give feedback.
-
|
Back is probably too strong a word to use. It's slow so probably still getting hammered but didn't error out on rs-ny.rustdesk.com so maybe it's trying to come online again. Have to wait and see. |
Beta Was this translation helpful? Give feedback.
-
|
Final note from me. For my needs, the direct ip connect setup is all I need. I suggest the RustDesk team make this option main stream in the initial configuration and use the VPS server (AWS or whatever it is) a more advanced configuration. Basically, the opposite of what is coded in the UI now. The most important thing is that you don't want to suffocate all of the outstanding work that has been done on this project with unreliability issues. If you insist on using the VPS method as a default, you should add a load balancer and add an auto scalable VPS service. Not free, but if configured correctly it wouldn't be very expensive. The direct connect configuration (mentioned above) would greatly reduce much of the normal traffic and the scalable VPS on a load balancer would afford you stability for those that need connections to more than single direct connects. Although, there's nothing stopping someone from port mapping multiple machines with the direct connect method. A comment from someone earlier about that is confusing to me, but probably some level of ignorance on my behalf. |
Beta Was this translation helpful? Give feedback.
-
|
If the bad actors are hammering just the IP, that's one thing. But if they're hammering the common Rustdesk TCP/UDP ports to death, then maybe code that dynamically throttles incoming connections requests based on heuristics that evaluate abnormal behavior (1000s of requests/sec, etc.) coming from a certain IP repeatedly and drops incoming packets from that IP until it stops or limits requests to one every 60 seconds. Just spitballing thought here. I know zero about how to code something like that but know that there are firewalls and appliances made the likes of Barracuda that have user configurable parameters that can do this. I've seen it in our own Barracuda appliance for incoming/outgoing email. |
Beta Was this translation helpful? Give feedback.
-
|
@kozman1000 .. that's a good solution. I've used ConfigServer csf firewall before. |
Beta Was this translation helpful? Give feedback.
-
|
Very important to know, RustDesk's public server is for demonstration and charitable purpose, they shouldn't take much time for this. For DDoS problem, I agree implement some firewall based on rate limit is a great idea, but don't know is it difficult to deploy on OS itself ? |
Beta Was this translation helpful? Give feedback.
-
|
ConfigServer setup Ubuntu |
Beta Was this translation helpful? Give feedback.
-
|
CSF would be good to help mitigation but bad actors would likely pump up their ingress traffic to the server and try to exhaust system resources. If CSF is constantly busy filtering traffic, CPU could get pegged at or near 100% just trying to protect you or your RAM would get chewed up because the queue gets huge. They already know most tactics an admin would do to try and stop them. That's why it's always better to tracert to the origin and reach out to downstream providers to cut off the source. Free IPs are rare as hens teeth so any ISP out there who's also hosting other customers on the same public IP where the attack is coming from would not want someone like the ICANN to get them kicked off the Internet. But, if all else fails: https://www.icann.org/en/blogs/details/how-to-report-a-ddos-attack-25-4-2013-en A good defense also means having good offense as well. |
Beta Was this translation helpful? Give feedback.
-
|
I can see how you got there. CSF does monitor traffic but once a bad actor has exceeded the threshold CSF blocks the address from the Read through these feature bullets. Don't be intimidated by what all it can do, just know that it can do exactly what you need it to do and there's more if you want to dive further later down the road. |
Beta Was this translation helpful? Give feedback.
-
|
That does sound like a useful tool then if the Rustdesk guys were to run it on their Linux server. Every ounce of mitigation would help I would think. I'm thinking that when Ubuntu 24.04 comes out, I might try and set up my own server (even though I am primarily a Windows guy) and play with CSF. I play with Mint more than Ubuntu TBH and since Mint is Ubuntu based I would surmise CSF should work there as well. It does sound like a nifty tool. Thanks for the info about it. |
Beta Was this translation helpful? Give feedback.
-
|
does the problem still persist for everybody? I seem to still experience the issue.. |
Beta Was this translation helpful? Give feedback.
-
|
*It was working fine for me until about an hour ago and now will not
connect.*
…On Wed, Feb 7, 2024 at 5:16 AM Emile ***@***.***> wrote:
does the problem still persist for everybody? I seem to still experience
the issue..
—
Reply to this email directly, view it on GitHub
<#5538 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFYH7OOBXBDY4T757BYOSTDYSN5DTAVCNFSM6AAAAABCTUDXP6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGOJVGAZTO>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Once again, I'm getting the "Failed to connect to rs-ny.rustdesk.com:21116:
Please try later" error.
…On Wed, Feb 7, 2024 at 8:12 AM Robert Gray ***@***.***> wrote:
*It was working fine for me until about an hour ago and now will not
connect.*
On Wed, Feb 7, 2024 at 5:16 AM Emile ***@***.***> wrote:
> does the problem still persist for everybody? I seem to still experience
> the issue..
>
> —
> Reply to this email directly, view it on GitHub
> <#5538 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BFYH7OOBXBDY4T757BYOSTDYSN5DTAVCNFSM6AAAAABCTUDXP6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGOJVGAZTO>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
|
i have the same problem, do you fix it yet? |
Beta Was this translation helpful? Give feedback.
-
|
I got the same problem. Not interested in hosting my own server at home. |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem as you for two days now. |
Beta Was this translation helpful? Give feedback.
-
|
The same problem. Seems, that communication is blocked by source address range(s). yesterday all nodes, connected via the same provider, was down, another provider was OK. Today all connections doesn't work |
Beta Was this translation helpful? Give feedback.
-
|
Me too... Again... 
|
Beta Was this translation helpful? Give feedback.
-
|
Me too... :( |
Beta Was this translation helpful? Give feedback.
and others
-
Bug Description
I'm having trouble connecting from a desktop PC 1 (Ethernet) to another desktop PC 2 (Wi-Fi). I should clarify that the computers are in different places and connected to different networks or ISPs. I had no problems before but recently from PC 1 I have not been able to connect to PC 2. Last week I was getting an error message saying "deadline has elapsed" and now I am getting an error message "Failed to connect to rs-ny.rustdesk. com:21116". While on PC 1 it says "Not ready. Check your internet connection", on PC 2 it says "Ready". When I try to connect from PC 2 to PC 1, Rustdesk on PC 2 says that the remote computer is not online despite being connected to the internet, and while I have problems on PC 1, from an Android phone (connected to the same network as PC 1) I can connect to PC 2. What can be wrong on PC 1? The Rustdesk version currently installed on PC 1 is 1.2.2 (I reinstalled thinking that this would fix the problem) but previously I was using version 1.1.9 (same as installed on PC 2).
How to Reproduce
Installed
Expected Behavior
It should get connected
Operating system(s) on local side and remote side
Windows 10 -> Windows 10
RustDesk Version(s) on local side and remote side
1.2.2 (nightly) -> 1.1.9
Screenshots
Additional Context
This is the log of PC 1 (I didn't know how to get it until I found the path in another thread)
[2023-08-28 11:06:19.836085 -05:00] DEBUG [libs\hbb_common\src\config.rs:434] Configuration path: C:\Users\namehide\AppData\Roaming\RustDesk\config\RustDesk_default.toml [2023-08-28 11:06:37.839480 -05:00] DEBUG [src\rendezvous_mediator.rs:594] Failed to connect to rs-ny.rustdesk.com:21115 [2023-08-28 11:06:37.839539 -05:00] DEBUG [src\rendezvous_mediator.rs:599] query onlines timeout 3s [2023-08-28 11:06:37.872447 -05:00] DEBUG [src\rendezvous_mediator.rs:594] Failed to connect to rs-ny.rustdesk.com:21115 [2023-08-28 11:06:37.872509 -05:00] DEBUG [src\rendezvous_mediator.rs:599] query onlines timeout 3s [2023-08-28 11:06:37.872447 -05:00] DEBUG [src\rendezvous_mediator.rs:594] Failed to connect to rs-ny.rustdesk.com:21115 [2023-08-28 11:06:37.872567 -05:00] DEBUG [src\rendezvous_mediator.rs:599] query onlines timeout 3s [2023-08-28 11:06:37.874447 -05:00] DEBUG [src\rendezvous_mediator.rs:594] Failed to connect to rs-ny.rustdesk.com:21115 [2023-08-28 11:06:37.874503 -05:00] DEBUG [src\rendezvous_mediator.rs:599] query onlines timeout 3s [2023-08-28 11:06:37.884051 -05:00] DEBUG [libs\hbb_common\src\config.rs:434] Configuration path: C:\Users\namehide\AppData\Roaming\RustDesk\config\RustDesk_default.toml [2023-08-28 11:06:37.885508 -05:00] DEBUG [libs\hbb_common\src\config.rs:434] Configuration path: C:\Users\namehide\AppData\Roaming\RustDesk\config\RustDesk_default.toml [2023-08-28 11:06:37.905868 -05:00] DEBUG [libs\hbb_common\src\config.rs:434] Configuration path: C:\Users\namehide\AppData\Roaming\RustDesk\config\RustDesk_hwcodec.toml [2023-08-28 11:06:37.921806 -05:00] INFO [src\flutter.rs:794] Session 521327037 start, render by flutter texture rgba plugin [2023-08-28 11:06:37.935056 -05:00] INFO [libs\scrap\src\common\codec.rs:549] cpu num:4, cpu usage:None, codec thread:1 [2023-08-28 11:06:37.935819 -05:00] DEBUG [libs\hbb_common\src\config.rs:434] Configuration path: C:\Users\namehide\AppData\Roaming\RustDesk\config\RustDesk_hwcodec.toml [2023-08-28 11:06:37.958772 -05:00] DEBUG [libs\hbb_common\src\config.rs:434] Configuration path: C:\Users\namehide\AppData\Roaming\RustDesk\config\RustDesk_hwcodec.toml [2023-08-28 11:06:49.621662 -05:00] DEBUG [libs\hbb_common\src\config.rs:434] Configuration path: C:\Users\namehide\AppData\Roaming\RustDesk\config\RustDesk_default.toml [2023-08-28 11:06:55.842863 -05:00] DEBUG [src\rendezvous_mediator.rs:594] Failed to connect to rs-ny.rustdesk.com:21115 [2023-08-28 11:06:55.842947 -05:00] DEBUG [src\rendezvous_mediator.rs:599] query onlines timeout 3s [2023-08-28 11:06:55.985957 -05:00] INFO [src\client.rs:280] rendezvous server: rs-ny.rustdesk.com:21116 [2023-08-28 11:06:55.986120 -05:00] ERROR [src\client.rs:2409] Connection closed: Failed to connect to rs-ny.rustdesk.com:21116: Please try later [2023-08-28 11:06:55.986177 -05:00] INFO [src\client\io_loop.rs:853] sync transfer job status [2023-08-28 11:06:55.986654 -05:00] DEBUG [libs\hbb_common\src\config.rs:434] Configuration path: C:\Users\namehide\AppData\Roaming\RustDesk\config\RustDesk_default.toml [2023-08-28 11:06:55.986835 -05:00] INFO [src\client\io_loop.rs:864] meta: TransferSerde { write_jobs: [], read_jobs: [] } [2023-08-28 11:06:55.986883 -05:00] INFO [src\client.rs:1856] Video decoder loop exits [2023-08-28 11:06:55.986887 -05:00] INFO [src\client.rs:1884] Audio decoder loop exits [2023-08-28 11:06:56.012415 -05:00] DEBUG [libs\hbb_common\src\config.rs:434] Configuration path: C:\Users\namehide\AppData\Roaming\RustDesk\config\RustDesk_hwcodec.toml [2023-08-28 11:06:58.230957 -05:00] DEBUG [src\rendezvous_mediator.rs:594] Failed to connect to rs-ny.rustdesk.com:21115 [2023-08-28 11:06:58.231018 -05:00] DEBUG [src\rendezvous_mediator.rs:599] query onlines timeout 3sBeta Was this translation helpful? Give feedback.
All reactions