sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-10-17 02:59:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify when the proxy falls back to relay

Browse Source
This commit is contained in:
jnfrati
2026-10-14 11:39:00 +02:00
parent daa41ba1a8
commit dc6b7ebc53
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/selfhosted/migration/enable-reverse-proxy.mdx
+1 -1
View File
@@ -299,7 +299,7 @@ Apply both with `docker compose up -d proxy traefik`. The proxy's main port stay
### Enabling peer-to-peer connectivity
The proxy runs an embedded NetBird client to reach your peers. When the proxy runs in a container or behind NAT, it only knows its internal address and a random WireGuard port, so peers usually cannot reach it directly and fall back to a relay. To let peers establish direct peer-to-peer connections to the proxy:
The proxy runs an embedded NetBird client to reach your peers. Like any NetBird client, it discovers its public address through STUN. If no STUN server is reachable, or the STUN server cannot see the proxy's public address (for example, when it runs in an adjacent container on the same host), the proxy only advertises its internal address and peers fall back to a relay. In that case, to let peers establish direct peer-to-peer connections to the proxy:
1. Set a fixed WireGuard port with `NB_PROXY_WG_PORT`.
2. Forward that UDP port on your NAT or firewall to the proxy host, and publish it on the proxy container.