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

Connected peer unreachable #1799

New Issue
Open
opened 2025-11-20 06:07:00 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 06:07:00 -05:00
Owner
Copy Link

Originally created by @kosinus2pi on GitHub (Apr 8, 2025).

Describe the problem

After any change related to NetBird - such as restarting the service or modifying the network interface - most peers become unreachable, even though they still appear as "connected". This issue began about a week ago, despite no changes being made to the network infrastructure.

Out of approximately 100 peers, sudo wg show and netbird status -d display only a small subset of matching peers, suggesting that the majority are not establishing proper WireGuard sessions despite being listed as connected.

This is happening on both, Windows and Linux (Ubuntu) OS

To Reproduce

Steps to reproduce the behavior:

  1. Restart netbird service, reconnect netbird, change network interface

Expected behavior

All peers visible in netbird details -d output with connected status are reachable

Are you using NetBird Cloud?

No, self hosted instance.

NetBird version

0.39.2

Is any other VPN software installed?

No

Add any other context about the problem here.

Have you tried these troubleshooting steps?

  • Checked for newer NetBird versions - Yes
  • Searched for similar issues on GitHub (including closed ones) - Yes
  • Restarted the NetBird client - Yes
  • Disabled other VPN software - n/a
  • Checked firewall settings - Yes
Originally created by @kosinus2pi on GitHub (Apr 8, 2025). **Describe the problem** After any change related to NetBird - such as restarting the service or modifying the network interface - most peers become unreachable, even though they still appear as "connected". This issue began about a week ago, despite no changes being made to the network infrastructure. Out of approximately 100 peers, `sudo wg show` and `netbird status -d` display only a small subset of matching peers, suggesting that the majority are not establishing proper WireGuard sessions despite being listed as connected. This is happening on both, Windows and Linux (Ubuntu) OS **To Reproduce** Steps to reproduce the behavior: 1. Restart netbird service, reconnect netbird, change network interface **Expected behavior** All peers visible in `netbird details -d` output with connected status are reachable **Are you using NetBird Cloud?** No, self hosted instance. **NetBird version** 0.39.2 **Is any other VPN software installed?** No Add any other context about the problem here. **Have you tried these troubleshooting steps?** - [ ] Checked for newer NetBird versions - Yes - [ ] Searched for similar issues on GitHub (including closed ones) - Yes - [ ] Restarted the NetBird client - Yes - [ ] Disabled other VPN software - n/a - [ ] Checked firewall settings - Yes
saavagebueno added the triage-needed label 2025-11-20 06:07:00 -05:00
saavagebueno commented 2025-11-20 06:07:01 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 8, 2025):

could you turn on trace logs, reproduce and send us debug bundle?
You can mail it to support at netbird.io or send to me directly on Slack (kdn).

@nazarewk commented on GitHub (Apr 8, 2025): could you turn on trace logs, reproduce and send us debug bundle? You can mail it to support at netbird.io or send to me directly on Slack (kdn).
saavagebueno commented 2025-11-20 06:07:01 -05:00
Author
Owner
Copy Link

@netandreus commented on GitHub (Apr 21, 2025):

I have the same issue. It repeats almost every day now. I caught 2 different cases now:

  1. There is no Netbird IP and FQDN, and onlu 2/60 nodes "connected". There is no ping to current node.
OS: linux/amd64
Daemon version: 0.39.1
CLI version: 0.39.1
Management: Connected to https://gateway.wealthcoders.com:443
Signal: Connected to https://gateway.wealthcoders.com:443
Relays:
  [stun:gateway.wealthcoders.com:3478] is Available
  [turn:gateway.wealthcoders.com:3478?transport=udp] is Available
  [rels://gateway.wealthcoders.com:443] is Available
Nameservers:
> FQDN:
> NetBird IP: N/A
Interface type: N/A
Quantum resistance: false
Networks: -
Forwarding rules: 0
> Peers count: 2/69 Connected
  1. There are both FQDN and NetBird IP, but zero nodes connected. There is no ping to current node.
OS: linux/amd64
Daemon version: 0.39.1
CLI version: 0.39.1
Management: Connected
Signal: Connected
Relays: 3/3 Available
Nameservers: 0/0 Available
> FQDN: xxx.netbird.selfhosted
> NetBird IP: 100.81.94.114/16
Interface type: Kernel
Quantum resistance: false
Networks: 10.10.100.0/24 ...
Forwarding rules: 0
> Peers count: 0/69 Connected

@nazarewk can you please fix it? I already sent debug bundles to @pappz via Slack.

@netandreus commented on GitHub (Apr 21, 2025): I have the same issue. It repeats almost every day now. I caught 2 different cases now: 1. There is no Netbird IP and FQDN, and onlu 2/60 nodes "connected". There is no ping to current node. ``` OS: linux/amd64 Daemon version: 0.39.1 CLI version: 0.39.1 Management: Connected to https://gateway.wealthcoders.com:443 Signal: Connected to https://gateway.wealthcoders.com:443 Relays: [stun:gateway.wealthcoders.com:3478] is Available [turn:gateway.wealthcoders.com:3478?transport=udp] is Available [rels://gateway.wealthcoders.com:443] is Available Nameservers: > FQDN: > NetBird IP: N/A Interface type: N/A Quantum resistance: false Networks: - Forwarding rules: 0 > Peers count: 2/69 Connected ``` 2. There are both FQDN and NetBird IP, but zero nodes connected. There is no ping to current node. ``` OS: linux/amd64 Daemon version: 0.39.1 CLI version: 0.39.1 Management: Connected Signal: Connected Relays: 3/3 Available Nameservers: 0/0 Available > FQDN: xxx.netbird.selfhosted > NetBird IP: 100.81.94.114/16 Interface type: Kernel Quantum resistance: false Networks: 10.10.100.0/24 ... Forwarding rules: 0 > Peers count: 0/69 Connected ``` @nazarewk can you please fix it? I already sent debug bundles to @pappz via Slack.
saavagebueno commented 2025-11-20 06:07:01 -05:00
Author
Owner
Copy Link

@Pamalosebi commented on GitHub (Oct 22, 2025):

I do experience something similar. It did work before ~0.58 I think.

I can connect to lets say peer A from peer B.
But when restarting the netbird service on peer B, peer B cannot connect to A anymore. Even when shown as online with netbird status.
When rebooting peer A (just restarting the service is not enough) then peer B can connect again without further changes.
Really strange and I cannot see how to debug further.

edit:
de-registering peer B and re-registering peer B immediately fixes it without reboot of peer A.
But then the IP of peer B changes which causes other issues.

@Pamalosebi commented on GitHub (Oct 22, 2025): I do experience something similar. It did work before ~0.58 I think. I can connect to lets say peer A from peer B. But when restarting the netbird service on peer B, peer B cannot connect to A anymore. Even when shown as online with `netbird status`. When rebooting peer A (just restarting the service is not enough) then peer B can connect again without further changes. Really strange and I cannot see how to debug further. edit: de-registering peer B and re-registering peer B immediately fixes it without reboot of peer A. But then the IP of peer B changes which causes other issues.
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#1799
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?