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

netbird doesn't seem to recover from network outage #534

New Issue
Closed
opened 2025-11-20 05:13:14 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:13:14 -05:00
Owner
Copy Link

Originally created by @TheRouce on GitHub (Dec 7, 2023).

Describe the problem
I've had two network outages recently and both times I had to manually setup each device again. An outage happened today and the same thing has happened, the network is back up but all 10 of my nodes have not reconnected.

To Reproduce
Steps to reproduce the behavior:

  1. Disconnect internet for at least a few hours, maybe up to 24 hours
  2. Reconnect internet

Expected behavior
Netbird should automatically reconnect on the last network it was authorized

NetBird status -d output:
I can comment the output when I am back at the server

Additional context
If any tests need to be performed I can simulate an outage using proxmox or similar and try to retrieve logs

Originally created by @TheRouce on GitHub (Dec 7, 2023). **Describe the problem** I've had two network outages recently and both times I had to manually setup each device again. An outage happened today and the same thing has happened, the network is back up but all 10 of my nodes have not reconnected. **To Reproduce** Steps to reproduce the behavior: 1. Disconnect internet for at least a few hours, maybe up to 24 hours 2. Reconnect internet **Expected behavior** Netbird should automatically reconnect on the last network it was authorized **NetBird status -d output:** I can comment the output when I am back at the server **Additional context** If any tests need to be performed I can simulate an outage using proxmox or similar and try to retrieve logs
saavagebueno added the clientwaiting-feedback labels 2025-11-20 05:13:14 -05:00
saavagebueno commented 2025-11-20 05:13:15 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Dec 8, 2023):

Hello @TheRouce, the peers would actively attempt to reconnect after network outages. It keeps retrying for 3 months.

What may cause an issue is a dependency on private DNS routed via the wireguard tunnel to resolve the domain name of your management services. If that is the case for you, you can add a nameserver configuration with a matching domain for your management services pointing to a public or a resolver independent from the tunnel.

If that is not the case, please follow the steps below to enable debug logs on one of the peers:

sudo netbird service stop
sudo netbird service uninstall
sudo netbird service install --log-level debug
sudo netbird service start

Then reproduce the outage on the proxmox host where this peers is running.

Once that is done, can you share the logs from the peer? they are located at /var/log/netbird

@mlsmaycon commented on GitHub (Dec 8, 2023): Hello @TheRouce, the peers would actively attempt to reconnect after network outages. It keeps retrying for 3 months. What may cause an issue is a dependency on private DNS routed via the wireguard tunnel to resolve the domain name of your management services. If that is the case for you, you can add a nameserver configuration with a matching domain for your management services pointing to a public or a resolver independent from the tunnel. If that is not the case, please follow the steps below to enable debug logs on one of the peers: ```shell sudo netbird service stop sudo netbird service uninstall sudo netbird service install --log-level debug sudo netbird service start ``` Then reproduce the outage on the proxmox host where this peers is running. Once that is done, can you share the logs from the peer? they are located at `/var/log/netbird`
saavagebueno commented 2025-11-20 05:13:15 -05:00
Author
Owner
Copy Link

@TheRouce commented on GitHub (Dec 8, 2023):

Sorry, forgot to close this. This ended up being related to an issue with our VPN accidentally being blocked. Not related to netbird.

@TheRouce commented on GitHub (Dec 8, 2023): Sorry, forgot to close this. This ended up being related to an issue with our VPN accidentally being blocked. Not related to netbird.
saavagebueno commented 2025-11-20 05:13:15 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Dec 8, 2023):

Thanks for the feedback @TheRouce

@mlsmaycon commented on GitHub (Dec 8, 2023): Thanks for the feedback @TheRouce
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 client waiting-feedback
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#534
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?