Key Mismatch after update latest docker image

[teledong]

trafficstars

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...

[randall11GB]

yes I upgraded too. and I have same key mismatch. cannot connect. please advise

[GuillaumeHullin]

are you sure your server keys did not change during the upgrade? Compare your installed pub key with your RustDesk client.

[randall11GB]

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: @.***>

[GuillaumeHullin]

if you run docker logs rustdesk-server to pull the logs. At the startup sequence, search for Key: and compare with what you have.

[rustdesk]

This version changes default -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 "".

[GuillaumeHullin]

@rustdesk Oh I see....could it be that I did not run into an error because I have ENCRYPTED_ONLY as true?

[zhangbo8418]

hbbs -k ""

It's no use

[rustdesk]

@rustdesk Oh I see....could it be that I did not run into an error because I have ENCRYPTED_ONLY as true?

yes

[xldistance]

This version changes default -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 "".

I set the key on the client and running hbbs still prompts key mismatch

[GuillaumeHullin]

Are you sure you set the the Public key on the client? Not the private!

[randall11GB]

I have same issue. Tried many times making sure I am using server's public key. But I was not successful so i switched to version 10.3 from latest, as this last version which key is not required. Hoping this will resolve. 10.3 i am saying from memory, maybe different version as it is not in front of me exact version. Best regards,

Most importantly i want to thank team for providing such an amazing product for us.

Sent from Proton Mail Android

-------- Original Message -------- On 7/10/24 1:08 PM, Guillaume Hullin wrote:

Are you sure you set the the Public key on the client? Not the private!

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

[Thormus]

Adding public key to client fixed it. If running AIO ruskdesk server container just open logs, it will show you the public key.

[randall11GB]

I will give that a try. Thank you.

Sent from Proton Mail Android

-------- Original Message -------- On 7/11/24 8:11 AM, Bronzewing wrote:

Adding public key to client fixed it. If running AIO ruskdesk server container just open logs, it will show you the public key.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

[randall11GB]

So i tried it now working. Thank you very much. :)

Sent from Proton Mail Android

-------- Original Message -------- On 7/11/24 8:23 AM, randall11 wrote:

I will give that a try. Thank you.

Sent from Proton Mail Android

-------- Original Message -------- On 7/11/24 8:11 AM, Bronzewing wrote:

Adding public key to client fixed it. If running AIO ruskdesk server container just open logs, it will show you the public key.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

[randornot]

Maybe I find a way. There is a an extra "#" in pub key. run docker logs hbbs can check the key you need. I have observed that the key within the logs differs from the key in the pub key. like this: key in the log: key in the pub key: There is a an extra "#", before I observed that, I entered the pub key by copying the out of cat id_ed25519.pub, then when I tried to connect my PC, it prompted Key Mismatch. Now I use the key without "#" at the end, and enter both ID server and Relay server with ip:21116、ip:21117，it works. And whether latest image 1.1.11 or 1.1.10-3, it works all.

[randall11GB]

I had same error, because i used id_ed25519.pub The team told me to use key from log and now working. Now thanks to your details i know exactly why id_ed25519.pub did not work. Appreciate the detail. R Sent from Proton Mail Android

-------- Original Message -------- On 7/19/24 7:37 AM, xor wrote:

Maybe I find a way. There is a an extra "#" in pub key. run docker logs hbbs can check the key you need. I have observed that the key within the logs differs from the key in the pub key. like this: key in the log: image.png (view on web) key in the pub key: image.png (view on web) There is a an extra "#", before I observed that, I entered the pub key by copying the out of cat id_ed25519.pub, then when I tried to connect my PC, it prompted Key Mismatch. Now I use the key without "#" at the end, and enter both ID server and Relay server with ip:21116、ip:21117，it works. And whether latest image 1.1.11 or 1.1.10-3, it works all.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

@github.com>

[BakkerHenk]

It was only after changing the language setting that I figured out the Key was wrong. In my language the error was "Wrong code" which lead me down the wrong path. Adding the key from hbbs logs into the client fixed it for me. So thank you all.

[lw94]

注意他会在服务器生成两个 id_ed25519.pub 文件 Note that it will generate two id_ed25519.pub files on the server.

find / -name id_ed25519.pub

安装目录的 id_ed25519.pub 是错的 ,另一个一个才是对的 The id_ed25519.pub in the installation directory is incorrect; the other one is the correct one.

[RyanLoil]

This is not a bug i think.

I found that I run 2 rustdesk happenedly on my server (As rustdesk will automatically run after you install it though deb). This will lead to the second rustdesk create a new key will the first one still running in the old key. The phenomenen is that when you try to connect to another computer, you will receive "Key mismatch" the first time and then receive "Remote is offline" the second time and the laters. Shutdown the service first then kill all the process of rustdesk finally restart it works for me. And no need to change key.

我觉得这不是bug

我发现我的服务器上同时运行了两个 rustdesk（因为 rustdesk 通过 deb 安装后会自动运行）。这会导致第二个 rustdesk 创建新的密钥，而第一个仍在使用旧密钥运行。 这会导致一种很奇葩的现象：当你尝试连接到另一台电脑时，第一次会收到“Key不匹配”的提示，第二次和之后的尝试则会收到“远程电脑已离线”的提示。 我先关闭服务，然后终止所有 rustdesk 进程，最后重启一下，这样就解决了， key也无需更换。