Open teledong opened 1 month ago
yes I upgraded too. and I have same key mismatch. cannot connect. please advise
are you sure your server keys did not change during the upgrade? Compare your installed pub key with your RustDesk client.
Hello thank you for the reply. I am running rustdesk-server-s6:latest using docker. I upgraded from working version 1.1.10-3. I checked id_ed25519 and id_ed25519.pub on server latest. It is identical to version 1.1.10-3 but when i run latest get key mismatch when i run 1.1.10-3 works on all clients fine. I hope you can advise me how to fix. Again i really appreciate your time and help.
Sent from Proton Mail mobile
-------- Original Message -------- On May 26, 2024, 11:27 AM, Guillaume Hullin wrote:
are you sure your server keys did not change during the upgrade? Compare your installed pub key with your RustDesk client.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
if you run docker logs rustdesk-server
to pull the logs.
At the startup sequence, search for Key:
and compare with what you have.
-k
of hbbs to -
, which means setting key on client side is mandatory. If you want to run empty -k
as before, please run hbbs -k ""
.@rustdesk Oh I see....could it be that I did not run into an error because I have ENCRYPTED_ONLY
as true?
hbbs -k ""
It's no use
@rustdesk Oh I see....could it be that I did not run into an error because I have
ENCRYPTED_ONLY
as true?
yes
Bug Description
all client Key Mismatch after update latest docker image. can't connect
How to Reproduce
Update Latest version. // 1.1.10-3 is fine
Expected Behavior
can connect and remote any device.
Operating system(s) on local side and remote side
Android -> Android,Windows,Linux,etc...
RustDesk Version(s) on local side and remote side
latest
Screenshots
Additional Context
Also, latest (nightly build) arm7 signed apk can't install because package broken...