TheLanc3/rustdesk
1
0
Fork 0
mirror of https://github.com/rustdesk/rustdesk.git synced 2026-04-20 00:43:20 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ (markdown)

RustDesk
2025-06-06 14:33:43 +08:00
parent 3d0ea5c663
commit 0b93470daf
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
FAQ.md

@@ -368,6 +368,10 @@ https://github.com/rustdesk/rustdesk/discussions/6398#discussioncomment-9065991
- Check your relay server (hbbr/21117) is using the same key as hbbs (using the same `id_ed25519` file or having the same content). You can see some errors related to connection to relay server in https://github.com/rustdesk/rustdesk/wiki/FAQ#access-logs on controlled side.
You can find the key from logs of `hbbs` and `hbbr`. If you install with `install.sh`, the logs file are `hbbr.log` and `hbbs.log` under `/var/log/rustdesk-server/`. If you install with Docker compose, please use command `docker logs hbbs` and `docker logs hbbr`. You can find the key (something like `key: afdsfsdfsffsfsd=`) in the header of the logs file.
The id_ed25519 file is under `/var/lib/rustdesk-server/` if you install with `install.sh`, and under `./data` if you install with Docker compose.
It may be caused by using wrong volumns mapping in docker compose file, please strictly follow https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/installscript/docker/#docker-compose, or you changed hbbs key but forgot to sync to hbbr (and restart), or some other reasons.
> We have seen two cases having this hbbr key issue while upgading RustDesk server.