mirror of
https://github.com/rustdesk/rustdesk.git
synced 2026-03-02 19:26:56 -05:00
key mismatch error after update #3528
Labels
No labels
bug
documentation
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
question
unreproducible
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/rustdesk-rustdesk#3528
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
after the update i cant connect to any client.
The error "key mismatch" appears.
i backuped the data folder.
The
id_ed25519andid_ed25519.pubhave 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
Additional Context
No response
@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):
Ok i found the error probably.
but i dont understand it.
i remove the
-k /root/id_ed25519from 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_ed25519option i got:after removing the
-k /root/id_ed25519i got:what i dont understand - why did it work before?
@rustdesk commented on GitHub (Jul 4, 2025):
#763