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

I can connect to the host, but Relays and Peers are not connected. #664

New Issue
Open
opened 2025-11-20 05:15:39 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:15:39 -05:00
Owner
Copy Link

Originally created by @komajun on GitHub (Feb 29, 2024).

When the client connects to the host, it receives a "connected" message, and the Admin console confirms the addition of a Peer, but we were unable to confirm the actual communication using ping.

Client: Ubuntu 22.04, netbird ver.0.26.0
Host: Ubuntu 22.04, netbird ver.0.24.2

Commands used to connect
$ netbird up --management-url {self_hosted_URL} -k { netbird_setup_key }

Then, checking the status on the client side, we found that the number of connections was 0, although we expected that Relays and Peers would be counted.

The results of netbird status -d are shown below.

user@computer:~$ netbird status -d
Daemon version: 0.26.0
CLI version: 0.26.0
Management: Connected to {self_hosted_URL}
Signal: Connected to {self_hosted_URL}
Relays: 
  [stun:vpn.xxx.co.jp:3478] is Unavailable, reason: stun request: context deadline exceeded
  [turn:vpn.xxx.co.jp:3478?transport=udp] is Unavailable, reason: allocate: all retransmissions failed for YV2CLvA3o2CTUwGx
FQDN: {computer}.netbird.selfhosted
NetBird IP: xxx.xxx.xxx.xxx/16
Interface type: Kernel
Peers count: 0/27 Connected

Also, tailscale was previously installed on this client, but the package was removed with the following command.

$ sudo tailscale down --accept-risk=lose-ssh
$ sudo apt remove tailscale -y

Please tell us about possible causes.

thanks.

Originally created by @komajun on GitHub (Feb 29, 2024). When the client connects to the host, it receives a "connected" message, and the Admin console confirms the addition of a Peer, but we were unable to confirm the actual communication using ping. > Client: Ubuntu 22.04, netbird ver.0.26.0 > Host: Ubuntu 22.04, netbird ver.0.24.2 Commands used to connect `$ netbird up --management-url {self_hosted_URL} -k { netbird_setup_key }` Then, checking the status on the client side, we found that the number of connections was 0, although we expected that Relays and Peers would be counted. The results of `netbird status -d` are shown below. ``` user@computer:~$ netbird status -d Daemon version: 0.26.0 CLI version: 0.26.0 Management: Connected to {self_hosted_URL} Signal: Connected to {self_hosted_URL} Relays: [stun:vpn.xxx.co.jp:3478] is Unavailable, reason: stun request: context deadline exceeded [turn:vpn.xxx.co.jp:3478?transport=udp] is Unavailable, reason: allocate: all retransmissions failed for YV2CLvA3o2CTUwGx FQDN: {computer}.netbird.selfhosted NetBird IP: xxx.xxx.xxx.xxx/16 Interface type: Kernel Peers count: 0/27 Connected ``` Also, tailscale was previously installed on this client, but the package was removed with the following command. ``` $ sudo tailscale down --accept-risk=lose-ssh $ sudo apt remove tailscale -y ``` Please tell us about possible causes. thanks.
saavagebueno added the self-hosting label 2025-11-20 05:15:39 -05:00
saavagebueno commented 2025-11-20 05:15:40 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Feb 29, 2024):

Based on the status output, there seems to be some issue with connecting to your stun/turn servers. Take a look at https://docs.netbird.io/selfhosted/troubleshooting#debugging-turn-connections

@lixmal commented on GitHub (Feb 29, 2024): Based on the `status` output, there seems to be some issue with connecting to your stun/turn servers. Take a look at https://docs.netbird.io/selfhosted/troubleshooting#debugging-turn-connections
saavagebueno commented 2025-11-20 05:15:40 -05:00
Author
Owner
Copy Link

@firekirin67 commented on GitHub (Sep 3, 2024):

When the client connects to the host, it receives a "connected" message, and the Admin console confirms the addition of a Peer, but we were unable to confirm the actual communication using ping.

Client: Ubuntu 22.04, netbird ver.0.26.0
Host: Ubuntu 22.04, netbird ver.0.24.2

Commands used to connect $ netbird up --management-url {self_hosted_URL} -k { netbird_setup_key }

Then, checking the status on the client side, we found that the number of connections was 0, although we expected that Relays and Peers would be counted.

The results of netbird status -d are shown below.

user@computer:~$ netbird status -d
Daemon version: 0.26.0
CLI version: 0.26.0
Management: Connected to {self_hosted_URL}
Signal: Connected to {self_hosted_URL}
Relays: 
  [stun:vpn.xxx.co.jp:3478] is Unavailable, reason: stun request: context deadline exceeded
  [turn:vpn.xxx.co.jp:3478?transport=udp] is Unavailable, reason: allocate: all retransmissions failed for YV2CLvA3o2CTUwGx
FQDN: {computer}.netbird.selfhosted
NetBird IP: xxx.xxx.xxx.xxx/16
Interface type: Kernel
Peers count: 0/27 Connected

Also, tailscale was previously installed on this client, but the package was removed with the following command.

$ sudo tailscale down --accept-risk=lose-ssh
$ sudo apt remove tailscale -y

Please tell us about possible causes.

thanks.

I encountered the same issue as you. Is it resolved? Can you provide some help?

@firekirin67 commented on GitHub (Sep 3, 2024): > When the client connects to the host, it receives a "connected" message, and the Admin console confirms the addition of a Peer, but we were unable to confirm the actual communication using ping. > > > Client: Ubuntu 22.04, netbird ver.0.26.0 > > Host: Ubuntu 22.04, netbird ver.0.24.2 > > Commands used to connect `$ netbird up --management-url {self_hosted_URL} -k { netbird_setup_key }` > > Then, checking the status on the client side, we found that the number of connections was 0, although we expected that Relays and Peers would be counted. > > The results of `netbird status -d` are shown below. > > ``` > user@computer:~$ netbird status -d > Daemon version: 0.26.0 > CLI version: 0.26.0 > Management: Connected to {self_hosted_URL} > Signal: Connected to {self_hosted_URL} > Relays: > [stun:vpn.xxx.co.jp:3478] is Unavailable, reason: stun request: context deadline exceeded > [turn:vpn.xxx.co.jp:3478?transport=udp] is Unavailable, reason: allocate: all retransmissions failed for YV2CLvA3o2CTUwGx > FQDN: {computer}.netbird.selfhosted > NetBird IP: xxx.xxx.xxx.xxx/16 > Interface type: Kernel > Peers count: 0/27 Connected > ``` > > Also, tailscale was previously installed on this client, but the package was removed with the following command. > > ``` > $ sudo tailscale down --accept-risk=lose-ssh > $ sudo apt remove tailscale -y > ``` > > Please tell us about possible causes. > > thanks. I encountered the same issue as you. Is it resolved? Can you provide some help?
saavagebueno commented 2025-11-20 05:15:40 -05:00
Author
Owner
Copy Link

@mbaybarsk commented on GitHub (Feb 20, 2025):

I have the same problem, it's intermittent, I wonder I need to increase a timeout value somewhere.

@mbaybarsk commented on GitHub (Feb 20, 2025): I have the same problem, it's intermittent, I wonder I need to increase a timeout value somewhere.
saavagebueno commented 2025-11-20 05:15:40 -05:00
Author
Owner
Copy Link

@alepaes1975 commented on GitHub (Apr 26, 2025):

Hi, same problem here, but only in one machine im my network. Others are ok.

OS: linux/amd64 Daemon version: 0.42.0 CLI version: 0.42.0 Management: Connected to https://xxx:443 Signal: Connected to https://xxx:443 Relays: [stun:xxx:3478] is Unavailable, reason: stun request: context deadline exceeded [turn:xxx:3478?transport=udp] is Unavailable, reason: allocate: all retransmissions failed for RBEVaj6QKnI+hNRJ

@alepaes1975 commented on GitHub (Apr 26, 2025): Hi, same problem here, but only in one machine im my network. Others are ok. `OS: linux/amd64 Daemon version: 0.42.0 CLI version: 0.42.0 Management: Connected to https://xxx:443 Signal: Connected to https://xxx:443 Relays: [stun:xxx:3478] is Unavailable, reason: stun request: context deadline exceeded [turn:xxx:3478?transport=udp] is Unavailable, reason: allocate: all retransmissions failed for RBEVaj6QKnI+hNRJ `
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 self-hosting
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#664
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?