Updated FAQ (markdown)

RustDesk
2025-06-01 16:23:31 +08:00
parent 8013d0d260
commit 39ea547565

3
FAQ.md

@@ -76,12 +76,11 @@ First you should set relay server with public ip explicitly on "settings" -> "re
![image](https://github.com/user-attachments/assets/1831bd14-f7db-4065-ac9f-9ba5f18ab8ef) ![image](https://github.com/user-attachments/assets/1831bd14-f7db-4065-ac9f-9ba5f18ab8ef)
Go to [access logs](https://github.com/rustdesk/rustdesk/wiki/FAQ#access-logs) on controlled side, you can see more details about failures, also check connection logs `%AppData%\RustDesk\log\RustDesk_rCURRENT.log` on controlling side. Go to [access logs](https://github.com/rustdesk/rustdesk/wiki/FAQ#access-logs) on controlled side, you can see more details about failures, also check connection logs `%AppData%\RustDesk\log\RustDesk_rCURRENT.log` on controlling side.
If you host the server in your intranet with some type of routers, you may have network problem because of NAT hairping. If you host the server in your intranet with some type of routers, you may have network problem because of NAT hairping.
One simple solution for NAT hairping (loopback) is that both internal and external use domain. Internally, use an internal DNS Server to point the domain to an intranet IP. One simple solution for NAT hairping (loopback) is that both internal and external use domain. Internally, use an internal DNS Server (or modify your hosts file) to point the domain to an intranet IP.
https://rustdesk.com/docs/en/self-host/nat-loopback-issues/ https://rustdesk.com/docs/en/self-host/nat-loopback-issues/