Replies: 10 comments 1 reply
-
Same problem in all the machines. All showing the same message Connection error "ID does not exist". |
Beta Was this translation helpful? Give feedback.
-
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). |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Same issue here, two Win 11 boxes, using saved creds/id so I know it's not a mistype. |
Beta Was this translation helpful? Give feedback.
-
Same problem |
Beta Was this translation helpful? Give feedback.
-
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... |
Beta Was this translation helpful? Give feedback.
-
Sometimes if there is "ID does not exist" its because You or the other Side is on a different Server. |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
Hola, la solución a este problema es ir a la sección ajustes del rustdesk, luego ir a la sección red y eliminar lo que sale escrito en el servidor y en la key luego dar en aplicar y listo , esta solución me funciono a mi, espero sea de su ayuda.... |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Just installed rustdesk on another PC today. An ID was automatically generated as usual, but when I try to connect to it via the public servers the following error is returned:
ID does not exist
Other existing installations have been accessible today without any issue, btw.
Do the public servers need to be rebooted?
Beta Was this translation helpful? Give feedback.
All reactions