From 0b93470dafd7949d6af00300c468153cdb480170 Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Fri, 6 Jun 2025 14:33:43 +0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/FAQ.md b/FAQ.md
index 3ca96b2..eb95141 100644
--- a/FAQ.md
+++ b/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.