RustDesk Self-Hosted (Docker) – Persistent KEY mismatch in Mixed Network (LAN / Wi-Fi) #620
Unanswered
MixGitstore
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
While deploying a RustDesk self-hosted server using Docker (hbbs + hbbr) in a mixed enterprise network environment, I consistently encountered a KEY mismatch error during peer connection attempts. This occurred despite the server being correctly configured, reachable on all required ports, and clients successfully registering with the server. clients connected via Ethernet would appear as Ready, while Wi-Fi clients often remained in a Connecting state. In some cases, even two wired clients using the same server, public key, and RustDesk version were unable to establish a session and would fail with a KEY mismatch error.
Server-side logs confirmed successful client registration (update_pk, pk updated instead of insert.i Already tried regenerating keys, clearing client cache, reinstalling clients, resetting Docker volumes, and verifying firewall rules but nothing worked.
Beta Was this translation helpful? Give feedback.
All reactions