Key Mismatch since version 1.1.11
Describe the bug
I run multiple self-hosted RustDesk servers using docker and the sample docker-compose.yaml. On version 1.1.9 they work well. If I upgrade to more recent versions I get key mismatch error. (1.1.11 to 1.1.14, 1.1.10 being buggy and not running at all)
Describe the environment
- docker compose on
Ubuntu 24.04(both Docker as Snap or docker-ce official package)
Sample docker compose file :
networks:
rustdesk-net:
external: false
services:
hbbs:
container_name: hbbs
ports:
- 21115:21115
- 21116:21116
- 21116:21116/udp
- 21118:21118
image: rustdesk/rustdesk-server:1.1.9
command: hbbs -r [redacted domain]:21117
volumes:
- /opt/rustdesk:/root
networks:
- rustdesk-net
depends_on:
- hbbr
restart: unless-stopped
hbbr:
container_name: hbbr
ports:
- 21117:21117
- 21119:21119
image: rustdesk/rustdesk-server:1.1.9
command: hbbr
volumes:
- /opt/rustdesk:/root
networks:
- rustdesk-net
restart: unless-stopped
How to Reproduce the bug
- Install 1.1.9, setup the clients with the public key
- Test and notice it working
- Upgrade to any version higher than 1.1.9
- notice the
key mismatcherror
Expected behavior There should be no error.
Additional context I have searched any migration information in changelog, but found nothing. There is the mention of the "-k" option, but it is undocumented.
Nobody else has the issue ? I have it on three different servers ...
I tried with adding the key with -k in both hbbr and hbbs commands. The key is also reported correctly in /opt/rustdesk/id_ed25519.pub and in the output of docker containers.
As soon as I switch back to 1.1.9, everything works well.
Nobody else has the issue ? I have it on three different servers ...
I tried with adding the key with -k in both
hbbrandhbbscommands. The key is also reported correctly in/opt/rustdesk/id_ed25519.puband in the output of docker containers.As soon as I switch back to 1.1.9, everything works well.
Same here, but with .deb installation.
I guess the only solution is to revert back to older versions, which seems unsafe and overall a bad solution for this type of software.
And i assume most people never update their server instances, so there aren't many complaints about this so far.
Same here, Even if I specify the pub content with -k, Key Mismatch still occurs.
I have been banging my head against a wall trying to get this to work for the last few days using nssm on a Hyper-V VM. Connections are successful from clients to server but no matter what I had tried, I kept getting the key mismatch error. Has there been any word of a fix?
Same here, when can we expect the fix? It's a matter of security!