SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-10 17:31:53 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Self-hosted Relay Server addresses not shown in netbird status -d #2006

New Issue
Closed
opened 2025-11-20 06:11:04 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 06:11:04 -05:00
Owner
Copy Link

Originally created by @dadastory on GitHub (Jun 24, 2025).

Describe the problem

After adding a custom rel:// relay address to the management.json in a self-hosted NetBird deployment, I confirmed from management logs that the relay address is being loaded correctly:

2025-06-25T01:44:07Z INFO management/cmd/management.go:563 Relay addresses: [rel://1.2.3.4:33080]

However, on the client side, running netbird status -d shows only the default Relays. Clients cannot use the new added relay even when direct P2P connections are unavailable.

To Reproduce

  1. Edit management.json and add:
"Relay": {
  "Addresses": [
    "rels://netbird.xxxxx.com:443",
     "rels://1.2.3.4:33080"
  ],
  "Secret": "my-secret",
  "CredentialsTTL": "24h0m0s"
}
  1. Restart the management container:
docker-compose restart netbird-management
  1. On another public server, run the relay container:
docker run -d \
  --name netbird-relay \
  --network host \
  --cap-add=NET_ADMIN \
  --device /dev/net/tun \
  -e NB_LISTEN_ADDRESS=":33080" \
  -e NB_EXPOSED_ADDRESS="1.2.3.4:33080" \
  -e NB_AUTH_SECRET="my-secret" \
  netbirdio/relay:latest
  1. On the client machine:
sudo systemctl restart netbird
netbird status -d

Expected behavior

Client should show the new added Relay address listed in the Relays: section of netbird status -d

Relays:
  [stun:netbird.xxxx.com:3478] is Available
  [turn:netbird.xxxxx.com:3478?transport=udp] is Available
  [rels://netbird.xxxxx.com:443] is Available
  ## but newer relays server no exist in this content:
  ##  rels://1.2.3.4:33080??? where is it?

Are you using NetBird Cloud?

❌ No, using self-hosted NetBird control plane.

NetBird version

Daemon version: 0.49.0
CLI version: 0.49.0

Is any other VPN software installed?

No.

Debug output

netbird status -d

Output omitted for brevity — no newer Relays added: section visible.

Uploaded files are automatically deleted after 30 days.

Alternatively, create the file only and attach it here manually:

netbird debug for 1m -AS

Screenshots

N/A

Additional context

Confirmed management log outputs correct relay list.
Verified relay server port is accessible via nc -vz 1.2.3.4 33080.
Tried resetting client (netbird down, delete /etc/netbird/store.json, re-register via netbird up).
Relay container is running with --network host and correct NB_AUTH_SECRET.

Have you tried these troubleshooting steps?

  • [ x] Reviewed client troubleshooting (if applicable)
  • [ x] Checked for newer NetBird versions
  • [ x] Searched for similar issues on GitHub (including closed ones)
  • [ x] Restarted the NetBird client
  • [ x] Disabled other VPN software
  • [ x] Checked firewall settings
Originally created by @dadastory on GitHub (Jun 24, 2025). **Describe the problem** After adding a custom rel:// relay address to the management.json in a self-hosted NetBird deployment, I confirmed from management logs that the relay address is being loaded correctly: ``` 2025-06-25T01:44:07Z INFO management/cmd/management.go:563 Relay addresses: [rel://1.2.3.4:33080] ``` However, on the client side, running netbird status -d shows only the default Relays. Clients cannot use the new added relay even when direct P2P connections are unavailable. **To Reproduce** 1. Edit management.json and add: ``` "Relay": { "Addresses": [ "rels://netbird.xxxxx.com:443", "rels://1.2.3.4:33080" ], "Secret": "my-secret", "CredentialsTTL": "24h0m0s" } ``` 2. Restart the management container: ``` docker-compose restart netbird-management ``` 3. On another public server, run the relay container: ``` docker run -d \ --name netbird-relay \ --network host \ --cap-add=NET_ADMIN \ --device /dev/net/tun \ -e NB_LISTEN_ADDRESS=":33080" \ -e NB_EXPOSED_ADDRESS="1.2.3.4:33080" \ -e NB_AUTH_SECRET="my-secret" \ netbirdio/relay:latest ``` 4. On the client machine: ``` sudo systemctl restart netbird netbird status -d ``` **Expected behavior** Client should show the new added Relay address listed in the Relays: section of netbird status -d ``` Relays: [stun:netbird.xxxx.com:3478] is Available [turn:netbird.xxxxx.com:3478?transport=udp] is Available [rels://netbird.xxxxx.com:443] is Available ## but newer relays server no exist in this content: ## rels://1.2.3.4:33080??? where is it? ``` **Are you using NetBird Cloud?** ❌ No, using self-hosted NetBird control plane. **NetBird version** Daemon version: 0.49.0 CLI version: 0.49.0 **Is any other VPN software installed?** No. **Debug output** ``` netbird status -d ``` Output omitted for brevity — no newer Relays added: section visible. *Uploaded files are automatically deleted after 30 days.* Alternatively, create the file only and attach it here manually: netbird debug for 1m -AS **Screenshots** N/A **Additional context** Confirmed management log outputs correct relay list. Verified relay server port is accessible via nc -vz 1.2.3.4 33080. Tried resetting client (netbird down, delete /etc/netbird/store.json, re-register via netbird up). Relay container is running with --network host and correct NB_AUTH_SECRET. **Have you tried these troubleshooting steps?** - [ x] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [ x] Checked for newer NetBird versions - [ x] Searched for similar issues on GitHub (including closed ones) - [ x] Restarted the NetBird client - [ x] Disabled other VPN software - [ x] Checked firewall settings
saavagebueno added the triage-needed label 2025-11-20 06:11:04 -05:00
saavagebueno commented 2025-11-20 06:11:06 -05:00
Author
Owner
Copy Link

@dadastory commented on GitHub (Jun 24, 2025):

  • i change the protocol from refs to ref ，because i have no cert, and Client reconnect the server, it works, it succeed show in my Relay Lists, but why it only show one Relay Serve rather than a list of server's relay server
@dadastory commented on GitHub (Jun 24, 2025): - i change the protocol from refs to ref ，because i have no cert, and Client reconnect the server, it works, it succeed show in my Relay Lists, but why it only show one Relay Serve rather than a list of server's relay server
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label triage-needed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2006
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?