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

Updated FAQ (markdown)

RustDesk
2025-06-01 16:23:31 +08:00
parent 8013d0d260
commit 39ea547565
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
FAQ.md

@@ -72,16 +72,15 @@ The hardware requirements are very low, the minimum configuration of the cloud s
# Deploy RustDesk server in intranet.
First you should set relay server with public ip explicitly on "settings" -> "relay" of web console. Or you can set relay server (public ip) explcitly on controlled side (remote side, the device you want to control).
First you should set relay server with public ip explicitly on "settings" -> "relay" of web console. Or you can set relay server (public ip) explcitly on controlled side (remote side, the device you want to control).
![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.
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/