rustdesk / rustdesk/rustdesk-server
Key Mismatch since version 1.1.11
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked docker-compose.yml and reproduce the upgrade from server version 1.1.9 using the persisted /opt/rustdesk volume. Compare the later versions' key handling and the undocumented -k option, then verify an upgrade preserves client connectivity without the key mismatch error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, rust
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100