Skip to content

Update ports-and-firewalls.mdx #790

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
emrcbrn merged 1 commit into from
Jun 11, 2026
+1 −1
Merged

Update ports-and-firewalls.mdx #790

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/pages/about-netbird/ports-and-firewalls.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ NetBird usually won't need open ports, but sometimes you or your IT team needs t
* In more restricted environments, `netbird status` will show `keepalive ping failed` errors without a firewall rule for TURN
* Example `nftables` outbound firewall rule: `ip daddr turn.netbird.io tcp dport 443-65535 accept`
* Relay service:
* **Endpoint**: *.relay.netbird.io
* **Endpoints**: *.relay.netbird.io and relay.netbird.io
* **Port**: TCP/443
* **IPv4**: The list is dynamic and geo-distributed; When looking at the `netbird status -d` output, you can see which relay you are connecting to.
* It is advised to wildcard `*.relay.netbird.io` when possible, to avoid interrupts.
Expand Down
Loading