Same problem in all the machines. All showing the same message Connection error "ID does not exist".

Not so sure it is a server issue... maybe a client issue as well or instead? Reason I say this is I think I have seen "ID not found" and/or other issues like client hanging at "generating ID" if more than one copy of rustdesk client is running and/or hanging. I think upon launch, rustdesk should check to see if there are already existing rustdesk process(es), and just try to open the existing process. If it sees more than one processes already running, or there is a timeout trying to open existing process, it should suggest a reboot, and/or to try these commands in the Terminal (in MacOS or Linux):

  pkill  rustdesk
  sleep 5
  pkill  -9  rustdesk
  sleep 5
echo "    Now relaunch rustdesk  ... Or on linux, just type:   rustdesk       "
echo "    On macos:    open   /Applications/RustDesk.app  "
echo "    If it fails to launch on Mac, then try this command in Terminal "
echo "        /Applications/RustDesk.app/Contents/MacOS/rustdesk "
   /Applications/RustDesk.app/Contents/MacOS/rustdesk

If launched from Terminal on macos, then you have to give the Terminal same permissions as Rustdesk for viewing screen, etc (in SysPrefs->Security->Privacy).

OK - So I ran into this issue when I replaced my server. Not guaranteed to work in your case, but I found that restarting the RustDesk service on the problem PC (the one you can't connect to) does the trick.

My guess is that IDs are only registered when the service starts. I will hope that they change that so that every time the config is updated (settings change), it will re-register with the server. This would prevent a lot of headache and force reboots of servers...

Sometimes if there is "ID does not exist" its because You or the other Side is on a different Server.

I have the same issue connect from pc A -> pc B, so in pc B, after I click "Start" in the General Settings -> Service, then I can connect

Cutt-off the old signal-server and all clients register to the new one!

That was the trick in my situation. I changed the DNS IP (A) record for the signal-server and wait... but no client ID exists on the new server until a rustdesk-service restart on the client. The real problem: the old signal-server was still online (IP and Ports) and that's why no client reconnect/register to the new server.

I have the same issue. It seems to be a client issue since self hosted and public servers both gave the same result.

Client A (macOS 14.5 aarch64) can not connect to client B (macOS 12.7.5, x86/64) but client B can connect to client A.

I had the same issue, what worked for me is the following.
I’m using version 1.2.3-2
Self hosted.
And you are right its a Client issue, so all below is on the client.

1 I removed the ID server (ip address) and key, so removed my self hosted server info on the client.
2 Stopped the (client) server via general tab
3 Closed the rustdesk client software
4 I renamed the Rustdesk.toml file ( C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\RustDesk\config) So software couldn’t find it anymore (not sure if this step is needed)
5 Started the client software and restarted the server.
So it had to connect to the public server
And the ID changed.
6 Then put back my own server info and it worked.

I use the portable client, if you have installed it, you may have to stop the rustdesk service(?)

Hope this helps you.

I've been having trouble recently with this as well but have fixed mine with just the simplest way possible. I think one of the issues is that the IDs have a different format when typing it in.

Like PC 1's ID is like 12 345 678 900 (11 digits), and PC 2 is 123 456 789 (9 digits). When I type in PC 2's ID it follows the pattern/format of PC 1's ID like it would be 12 345 678 9 and it shows it does not exist.

So I copied the ID from PC 2 so it should say 123 456 789 and it connected. Hope this makes sense and helps anybody.

Same problem here, I even copied the ID to .txt and pasted it on another machine. "ID does not exist" which is clearly not true.
Why is that?

same as mine, the problem happend on a 8 digs ID, i can not figure out how this ID be generted, or how to generate another ID to solve the problem
version 1.3.0 newly installed.. not fixed
self-hosted server: not works
public server: not works
tried 5 different client terminals, 4 out of 5 are ok, only one shows ID not existed
problem client setup on PVE8.0.2'/Ubuntu 22.4 VM
shows connected but other VM or Terminals or Mac can not rust desk to it .... ID not existed

update:
reinstalled then fixed with a new ID (still 8 digs)

So friend of mine installed RustDesk from the unofficial website rustdesk(dot)io. We encountered an issue where the "ID not found" error appeared. Upon investigation, we found that the unofficial version had configured a custom ID/Relay server pointing to api.rustdesk.io with an API key.

Even after uninstalling the unofficial version and reinstalling RustDesk from the official source, the custom relay server settings persisted. This caused ongoing connection issues, even though the app was now from the official source.

It would be great if RustDesk could mitigate this issue perhaps by clearing or verifying relay server configurations during installation. This would be a valuable security improvement to prevent such persistence from unofficial sources. So theres a way to mitigate this issue and prevent it from happening again.

I think I've also encountered this problem. My Windows client is fine. I'm not quite sure if my situation is the same as yours?