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

netbird 0.56.1 and up don't wait long enough for DNS resolve during netbird up #2289

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

Originally created by @Spiritreader on GitHub (Sep 15, 2025).

Describe the problem

I have a peer that seems to be rather slow when dialing the management, signal and relay servers.
Since 0.56.1, when starting up the docker container, the first connect always fails.
I need to wait a bit and manually call netbird up via the attached docker shell. That will then connect the container.

It only happens on this machine, and all of the netbird related services are definitely up and available as my other home lab machines connect with no issue.

To Reproduce

Steps to reproduce the behavior:

  1. Start netbird docker container on a machine with slow dns resolution.
  2. Wait and observe logs

Expected behavior

Netbird connects

Are you using NetBird Cloud?

Selfhosted.

NetBird version

0.56.1, 0.57.0 and 0.57.1

Is any other VPN software installed?

Yes, Wireguard

Debug output

To help us resolve the problem, please attach the following anonymized status output

Peers detail:
Events: No events recorded
OS: linux/amd64
Daemon version: 0.57.1
CLI version: 0.57.1
Profile: default
Management: Disconnected, reason: rpc error: code = Canceled desc = context canceled
Signal: Disconnected, reason: rpc error: code = Canceled desc = context canceled
Relays: 
  [rels://relay-bar.anon-5EHXn.domain] is Unavailable, reason: relay client not connected
Nameservers: 
FQDN: quasar.wan.anon-5EHXn.domain
NetBird IP: 100.64.225.216/16
Interface type: Kernel
Quantum resistance: false
Lazy connection: false
Networks: -
Forwarding rules: 0
Peers count: 0/0 Connected

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

Attached logs show attempting to start the docker container three times.

netbird-client_logs.txt

Add any other context about the problem here.

There is a similar issue here #4358, but I don't think it's related to my issue as it has started precisely with 0.56.1 and never happened before.

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings
Originally created by @Spiritreader on GitHub (Sep 15, 2025). **Describe the problem** I have a peer that seems to be rather slow when dialing the management, signal and relay servers. Since 0.56.1, when starting up the docker container, the first connect always fails. I need to wait a bit and manually call `netbird up` via the attached docker shell. That will then connect the container. It only happens on this machine, and all of the netbird related services are definitely up and available as my other home lab machines connect with no issue. **To Reproduce** Steps to reproduce the behavior: 1. Start netbird docker container on a machine with slow dns resolution. 2. Wait and observe logs **Expected behavior** Netbird connects **Are you using NetBird Cloud?** Selfhosted. **NetBird version** 0.56.1, 0.57.0 and 0.57.1 **Is any other VPN software installed?** Yes, Wireguard **Debug output** To help us resolve the problem, please attach the following anonymized status output ``` Peers detail: Events: No events recorded OS: linux/amd64 Daemon version: 0.57.1 CLI version: 0.57.1 Profile: default Management: Disconnected, reason: rpc error: code = Canceled desc = context canceled Signal: Disconnected, reason: rpc error: code = Canceled desc = context canceled Relays: [rels://relay-bar.anon-5EHXn.domain] is Unavailable, reason: relay client not connected Nameservers: FQDN: quasar.wan.anon-5EHXn.domain NetBird IP: 100.64.225.216/16 Interface type: Kernel Quantum resistance: false Lazy connection: false Networks: - Forwarding rules: 0 Peers count: 0/0 Connected ``` Alternatively, create the file only and attach it here manually: Attached logs show attempting to start the docker container three times. [netbird-client_logs.txt](https://github.com/user-attachments/files/22352336/netbird-client_logs.txt) **Add any other context about the problem here.** There is a similar issue here #4358, but I don't think it's related to my issue as it has started precisely with 0.56.1 and never happened before. **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 07:07:09 -05:00
saavagebueno commented 2025-11-20 07:07:10 -05:00
Author
Owner
Copy Link

@Spiritreader commented on GitHub (Sep 23, 2025):

fully resolved since 0.58.1, probably related to either #4523, #4509 or both of them

@Spiritreader commented on GitHub (Sep 23, 2025): fully resolved since 0.58.1, probably related to either #4523, #4509 or both of them
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#2289
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?