From 072a9bbb7df55cb0e3943290f5565058dfe9a67f Mon Sep 17 00:00:00 2001 From: RustDesk <71636191+rustdesk@users.noreply.github.com> Date: Thu, 6 Feb 2025 14:22:16 +0800 Subject: [PATCH] Update _index.en.md --- content/self-host/nat-loopback-issues/_index.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/self-host/nat-loopback-issues/_index.en.md b/content/self-host/nat-loopback-issues/_index.en.md index 9bed697..e84a4b6 100644 --- a/content/self-host/nat-loopback-issues/_index.en.md +++ b/content/self-host/nat-loopback-issues/_index.en.md @@ -12,7 +12,7 @@ This explanation involves complex networking knowledge, we need your assistance For more details about NAT Loopback, please check the [Wikipedia](https://en.m.wikipedia.org/wiki/Network_address_translation#NAT_hairpinning) page. When you're deploying RustDesk server on your home network or any other network environment that is behind a NAT firewall, the RustDesk server and your clients **MUST** either: -A: Use the local ip addresss to access eachother OR: +A: Use the local ip addresss to access each other OR: B: Have a firewall that supports and has enabled the NAT Loopback. You may notice you are unable to connect to your server through your **Public IP** or **Domain** (Which in theory points to your public IP).