SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-18 14:11:56 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Only one peer at a time reachable on VPS on service provider #878

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

Originally created by @mkauzlar on GitHub (May 13, 2024).

Describe the problem

When using Netbird on VPS at contabo only one VPS is available at a time to be reachable

To Reproduce

Setup 2 VPS at Contabo in 2 differen datacenters (Munich and Dusseldorf)
Install Netbird on both (TS1 and TS2)
Install netbird on local (nas1) (outside Contabo)

nas1 can ping TS1 but not TS2
TS1 cannot ping TS2

Restart netbird on TS2 then:
nas1 can ping TS2 but not TS!
TS2 cannot ping TS1

Basically either TS1 or TS2 is available. Restarting one disables the other.

Expected behavior

nas1 should be able to reach TS1 and TS2
And TS1 should be able to connect to TS2 and vice-versa

Are you using NetBird Cloud?

Using Netbird Cloud

NetBird version

0.27.5

NetBird status -d output:

on TS1:

Peers detail:
 nas1.netbird.cloud:
  NetBird IP: 100.97.209.153
  Public key: ***********************
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: false
  ICE candidate (Local/Remote): relay/srflx
  ICE candidate endpoints (Local/Remote): 18.157.58.205:21395/178.39.159.22:51820
  Last connection update: 27 minutes, 5 seconds ago
  Last WireGuard handshake: 3 minutes ago
  Transfer status (received/sent) 117.7 MiB/3.3 GiB
  Quantum resistance: false
  Routes: -
  Latency: 16.786306ms

 ts2.netbird.cloud:
  NetBird IP: 100.97.214.188
  Public key: *************************
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: false
  ICE candidate (Local/Remote): relay/relay
  ICE candidate endpoints (Local/Remote): 18.157.58.205:41300/18.157.58.205:12333
  Last connection update: 27 minutes, 3 seconds ago
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/37.6 KiB
  Quantum resistance: false
  Routes: -
  Latency: 14.144193ms

OS: linux/amd64
Daemon version: 0.27.5
CLI version: 0.27.5
Management: Connected to https://api.netbird.io:443
Signal: Connected to https://signal.netbird.io:443
Relays:
  [stun:stun.netbird.io:5555] is Unavailable, reason: client: write udp 91.205.175.196:39868->13.48.155.228:5555: write: operation not permitted
  [turns:turn.netbird.io:443?transport=tcp] is Available
Nameservers:
FQDN: ts1.netbird.cloud
NetBird IP: 100.97.253.199/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 3/6 Connected


on TS2:

Peers detail:
 nas1.netbird.cloud:
  NetBird IP: 100.97.209.153
  Public key: ***********************************
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: false
  ICE candidate (Local/Remote): relay/srflx
  ICE candidate endpoints (Local/Remote): 18.157.58.205:51070/178.39.159.22:51820
  Last connection update: 27 minutes, 45 seconds ago
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/38.3 KiB
  Quantum resistance: false
  Routes: -
  Latency: 13.574702ms

 ts1.netbird.cloud:
  NetBird IP: 100.97.253.199
  Public key: *************************************
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: false
  ICE candidate (Local/Remote): relay/relay
  ICE candidate endpoints (Local/Remote): 18.157.58.205:12333/18.157.58.205:41300
  Last connection update: 27 minutes, 12 seconds ago
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/37.9 KiB
  Quantum resistance: false
  Routes: -
  Latency: 16.057329ms

OS: linux/amd64
Daemon version: 0.27.5
CLI version: 0.27.5
Management: Connected to https://api.netbird.io:443
Signal: Connected to https://signal.netbird.io:443
Relays:
  [stun:stun.netbird.io:5555] is Unavailable, reason: client: write udp 156.67.31.164:34020->18.157.58.205:5555: write: operation not permitted
  [turns:turn.netbird.io:443?transport=tcp] is Available
Nameservers:
FQDN: ts2.netbird.cloud
NetBird IP: 100.97.214.188/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 3/6 Connected

I have other peers on different networks and they connect without problems

Originally created by @mkauzlar on GitHub (May 13, 2024). **Describe the problem** When using Netbird on VPS at contabo only one VPS is available at a time to be reachable **To Reproduce** Setup 2 VPS at Contabo in 2 differen datacenters (Munich and Dusseldorf) Install Netbird on both (TS1 and TS2) Install netbird on local (nas1) (outside Contabo) nas1 can ping TS1 but not TS2 TS1 cannot ping TS2 Restart netbird on TS2 then: nas1 can ping TS2 but not TS! TS2 cannot ping TS1 Basically either TS1 or TS2 is available. Restarting one disables the other. **Expected behavior** nas1 should be able to reach TS1 and TS2 And TS1 should be able to connect to TS2 and vice-versa **Are you using NetBird Cloud?** Using Netbird Cloud **NetBird version** 0.27.5 **NetBird status -d output:** ``` on TS1: Peers detail: nas1.netbird.cloud: NetBird IP: 100.97.209.153 Public key: *********************** Status: Connected -- detail -- Connection type: Relayed Direct: false ICE candidate (Local/Remote): relay/srflx ICE candidate endpoints (Local/Remote): 18.157.58.205:21395/178.39.159.22:51820 Last connection update: 27 minutes, 5 seconds ago Last WireGuard handshake: 3 minutes ago Transfer status (received/sent) 117.7 MiB/3.3 GiB Quantum resistance: false Routes: - Latency: 16.786306ms ts2.netbird.cloud: NetBird IP: 100.97.214.188 Public key: ************************* Status: Connected -- detail -- Connection type: Relayed Direct: false ICE candidate (Local/Remote): relay/relay ICE candidate endpoints (Local/Remote): 18.157.58.205:41300/18.157.58.205:12333 Last connection update: 27 minutes, 3 seconds ago Last WireGuard handshake: - Transfer status (received/sent) 0 B/37.6 KiB Quantum resistance: false Routes: - Latency: 14.144193ms OS: linux/amd64 Daemon version: 0.27.5 CLI version: 0.27.5 Management: Connected to https://api.netbird.io:443 Signal: Connected to https://signal.netbird.io:443 Relays: [stun:stun.netbird.io:5555] is Unavailable, reason: client: write udp 91.205.175.196:39868->13.48.155.228:5555: write: operation not permitted [turns:turn.netbird.io:443?transport=tcp] is Available Nameservers: FQDN: ts1.netbird.cloud NetBird IP: 100.97.253.199/16 Interface type: Kernel Quantum resistance: false Routes: - Peers count: 3/6 Connected on TS2: Peers detail: nas1.netbird.cloud: NetBird IP: 100.97.209.153 Public key: *********************************** Status: Connected -- detail -- Connection type: Relayed Direct: false ICE candidate (Local/Remote): relay/srflx ICE candidate endpoints (Local/Remote): 18.157.58.205:51070/178.39.159.22:51820 Last connection update: 27 minutes, 45 seconds ago Last WireGuard handshake: - Transfer status (received/sent) 0 B/38.3 KiB Quantum resistance: false Routes: - Latency: 13.574702ms ts1.netbird.cloud: NetBird IP: 100.97.253.199 Public key: ************************************* Status: Connected -- detail -- Connection type: Relayed Direct: false ICE candidate (Local/Remote): relay/relay ICE candidate endpoints (Local/Remote): 18.157.58.205:12333/18.157.58.205:41300 Last connection update: 27 minutes, 12 seconds ago Last WireGuard handshake: - Transfer status (received/sent) 0 B/37.9 KiB Quantum resistance: false Routes: - Latency: 16.057329ms OS: linux/amd64 Daemon version: 0.27.5 CLI version: 0.27.5 Management: Connected to https://api.netbird.io:443 Signal: Connected to https://signal.netbird.io:443 Relays: [stun:stun.netbird.io:5555] is Unavailable, reason: client: write udp 156.67.31.164:34020->18.157.58.205:5555: write: operation not permitted [turns:turn.netbird.io:443?transport=tcp] is Available Nameservers: FQDN: ts2.netbird.cloud NetBird IP: 100.97.214.188/16 Interface type: Kernel Quantum resistance: false Routes: - Peers count: 3/6 Connected ``` I have other peers on different networks and they connect without problems
saavagebueno added the triage-needed label 2025-11-20 05:19:09 -05:00
saavagebueno commented 2025-11-20 05:19:09 -05:00
Author
Owner
Copy Link

@mkauzlar commented on GitHub (May 21, 2024):

Upgraded to Netbird 0.27.7 and it's working now

@mkauzlar commented on GitHub (May 21, 2024): Upgraded to Netbird 0.27.7 and it's working now
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#878
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?