key mismatch error after update #3528

Closed
opened 2026-02-21 01:26:10 -05:00 by deekerman · 3 comments
Owner

Originally created by @Frankstar on GitHub (Jul 4, 2025).

Bug Description

Docker compose install.
i updated from 1.6.1 to 1.6.2 via

docker compose down
docker compose pull
docker compose up -d

after the update i cant connect to any client.
The error "key mismatch" appears.

i backuped the data folder.
The id_ed25519 and id_ed25519.pub have the same sha256sum and same content.
So the file didnt changed.

On the Client the correct pub key is entered.
(same as before - since we did only update the server version)

How to Reproduce

update from 1.6.1 to 1.6.2

Expected Behavior

no key mismatch error after an update

Operating system(s) on local (controlling) side and remote (controlled) side

linux (fedora) -> win 11

RustDesk Version(s) on local (controlling) side and remote (controlled) side

1.4.0 -> 1.4.0

Screenshots

Image

Additional Context

No response

Originally created by @Frankstar on GitHub (Jul 4, 2025). ### Bug Description Docker compose install. i updated from 1.6.1 to 1.6.2 via ``` docker compose down docker compose pull docker compose up -d ``` after the update i cant connect to any client. The error "key mismatch" appears. i backuped the data folder. The `id_ed25519` and `id_ed25519.pub` have the same sha256sum and same content. So the file didnt changed. On the Client the correct pub key is entered. (same as before - since we did only update the server version) ### How to Reproduce update from 1.6.1 to 1.6.2 ### Expected Behavior no key mismatch error after an update ### Operating system(s) on local (controlling) side and remote (controlled) side linux (fedora) -> win 11 ### RustDesk Version(s) on local (controlling) side and remote (controlled) side 1.4.0 -> 1.4.0 ### Screenshots <img width="296" height="178" alt="Image" src="https://github.com/user-attachments/assets/c7d64665-ec88-46d5-a091-6f007a0e0fc7" /> ### Additional Context _No response_
deekerman 2026-02-21 01:26:10 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Frankstar commented on GitHub (Jul 4, 2025):

i dont understand what happend or why this error occurs.
the keys are correct on the clients and on the server, backup and inside docker container.

For testing purpose i downgraded to 1.6.1 -> the error persists.
So i even deleted the data folder and restorted from backup -> the error persists.
i though "maybe its the custom client", so i tryed with the offical client and adjuste the settings (ID server, api server and key) -> the errror persists.
i builded the custom client again -> the error persists.

Is there something else that could throw the "key mismatch"-Error?

@Frankstar commented on GitHub (Jul 4, 2025): i dont understand what happend or why this error occurs. the keys are correct on the clients and on the server, backup and inside docker container. For testing purpose i downgraded to 1.6.1 -> the error persists. So i even deleted the data folder and restorted from backup -> the error persists. i though "maybe its the custom client", so i tryed with the offical client and adjuste the settings (ID server, api server and key) -> the errror persists. i builded the custom client again -> the error persists. Is there something else that could throw the "key mismatch"-Error?
Author
Owner

@Frankstar commented on GitHub (Jul 4, 2025):

Ok i found the error probably.
but i dont understand it.

i remove the -k /root/id_ed25519 from the compose.yml command line.
even tho it is correctly mapped - i doesnt work with that path.

i noticed in the logs -> with the -k /root/id_ed25519 option i got:

hbbs  | [2025-07-04 20:13:08.696404 +00:00] INFO [/home/runner/work/rustdesk-server-pro/rustdesk-server-pro/src/rendezvous_server.rs:2749] Key: /root/id_ed25519

after removing the -k /root/id_ed25519 i got:

hbbs  | [2025-07-04 20:21:27.565961 +00:00] INFO [/home/runner/work/rustdesk-server-pro/rustdesk-server-pro/src/rendezvous_server.rs:2749] Key: Uuh2PNH2g37o6jXiBsieeIZEhv7DswnZiKO6v2agkmM=


what i dont understand - why did it work before?

@Frankstar commented on GitHub (Jul 4, 2025): Ok i found the error probably. but i dont understand it. i remove the `-k /root/id_ed25519` from the compose.yml command line. even tho it is correctly mapped - i doesnt work with that path. i noticed in the logs -> with the `-k /root/id_ed25519` option i got: ``` hbbs | [2025-07-04 20:13:08.696404 +00:00] INFO [/home/runner/work/rustdesk-server-pro/rustdesk-server-pro/src/rendezvous_server.rs:2749] Key: /root/id_ed25519 ``` after removing the `-k /root/id_ed25519` i got: ``` hbbs | [2025-07-04 20:21:27.565961 +00:00] INFO [/home/runner/work/rustdesk-server-pro/rustdesk-server-pro/src/rendezvous_server.rs:2749] Key: Uuh2PNH2g37o6jXiBsieeIZEhv7DswnZiKO6v2agkmM= ``` ___ what i dont understand - why did it work before?
Author
Owner

@rustdesk commented on GitHub (Jul 4, 2025):

#763

@rustdesk commented on GitHub (Jul 4, 2025): #763
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/rustdesk-rustdesk#3528
No description provided.