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

Release v0.30.0 selfhosted. Can't connect to name-based routes #1327

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

Originally created by @deniritech on GitHub (Oct 11, 2024).

Describe the problem

We updated our coordinator and peers to v0.30.0 and not we can not connect on the routes have setup.
We are selfhosting netbird. The issue happens when we move to version v0.30.1 as well.

To Reproduce

Steps to reproduce the behavior:

  1. Update the coordinator.
  2. Updated the peers.
  3. Updated client locally.
  4. We're unable to connect to DNS routes after selecting them.
    The client log locally repeats the following:
2024-10-11T15:22:33+02:00 INFO client/internal/routemanager/client.go:171: New chosen route is ***REDACTED ROUTE*** with peer ***REDACTED PEER*** with score 0.000000 for network [***REDACTED NETWORK***]
2024-10-11T15:22:33+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency
2024-10-11T15:22:38+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency
2024-10-11T15:22:51+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency
2024-10-11T15:23:03+02:00 INFO [peer: ***REDACTED PEER***] client/internal/peer/worker_relay.go:187: WireGuard handshake timed out, closing relay connection: 1970-01-01 01:00:00 +0100 CET
2024-10-11T15:23:03+02:00 INFO [relay: rel://***REDACTED COORDINATOR DOMAIN***:7777] relay/client/client.go:501: free up connection to peer: ***REDACTED***
2024-10-11T15:23:03+02:00 ERRO client/internal/wgproxy/usp/proxy.go:133: failed to read from remote conn: rel://***REDACTED COORDINATOR DOMAIN***:7777, EOF
2024-10-11T15:23:03+02:00 WARN client/internal/wgproxy/usp/proxy.go:122: error in proxy to local loop: 1 error occurred:
	* remote conn: connection already closed
2024-10-11T15:23:03+02:00 WARN client/internal/routemanager/client.go:160: The network [***REDACTED NETWORK***] has not been assigned a routing peer as no peers from the list [***REDACTED PEER***] are currently connected
2024-10-11T15:23:04+02:00 INFO [relay: rel://***REDACTED COORDINATOR DOMAIN***:7777] relay/client/client.go:214: open connection to peer: ***REDACTED***
2024-10-11T15:23:04+02:00 INFO [peer: ***REDACTED PEER***] client/internal/peer/conn.go:547: created new wgProxy for relay connection: 127.0.0.1:53261
2024-10-11T15:23:04+02:00 INFO [peer: ***REDACTED PEER***] client/internal/peer/conn.go:588: start to communicate with peer via relay
2024-10-11T15:23:04+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency
2024-10-11T15:23:04+02:00 INFO client/internal/routemanager/client.go:171: New chosen route is ***REDACTED ROUTE*** with peer ***REDACTED PEER*** with score 0.000000 for network [***REDACTED NETWORK***]
2024-10-11T15:23:04+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency
2024-10-11T15:23:11+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency
2024-10-11T15:23:27+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency

Expected behavior

We expected to be able to connect the the DNS route without an issue in this new release. When we roll back to v0.29.4 everything works.

Are you using NetBird Cloud?

We are using Self Hosted Netbird.

NetBird version

➜ netbird version
0.30.0

NetBird status -dA output:

In this case we can not add the status but for the route we want to use the peer is shown as connected. After we reload the page or try to connect to the page that DNS route links to it shows disconnected momentarily.

Do you face any (non-mobile) client issues?

Please provide the file created by netbird debug for 1m -AS.
We advise reviewing the anonymized files for any remaining PII.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

What we notice is the following :
1: We get connected to the peer we want: New chosen route is XXXXXXXXX with peer XXXXXXXXX with score 0.000000 for network [XXXXXXXX]
2: Error happens: 2024-10-11T15:23:03+02:00 ERRO client/internal/wgproxy/usp/proxy.go:133: failed to read from remote conn: rel://*********:7777, EOF 2024-10-11T15:23:03+02:00 WARN client/internal/wgproxy/usp/proxy.go:122: error in proxy to local loop: 1 error occurred: * remote conn: connection already closed 2024-10-11T15:23:03+02:00 WARN client/internal/routemanager/client.go:160: The network [***********] has not been assigned a routing peer as no peers from the list [***************] are currently connected 2024-10-11T15:23:04+02:00 INFO [relay: rel://****************:7777] relay/client/client.go:214: open connection to peer: ******** 2024-10-11T15:23:04+02:00 INFO [peer: ***********] client/internal/peer/conn.go:547: created new wgProxy for relay connection: 127.0.0.1:53261
3: The peer gets assigned again. 2024-10-11T15:23:03+02:00 WARN client/internal/routemanager/client.go:160: The network [XXXXXXXX] has not been assigned a routing peer as no peers from the list [XXXXXXXXXXX] are currently connected
4: This repeats every time we want to connect to the same DNS route.
5: The same issue happens when we update to v0.30.1 as well.

Originally created by @deniritech on GitHub (Oct 11, 2024). **Describe the problem** We updated our coordinator and peers to v0.30.0 and not we can not connect on the routes have setup. We are selfhosting netbird. The issue happens when we move to version v0.30.1 as well. **To Reproduce** Steps to reproduce the behavior: 1. Update the coordinator. 2. Updated the peers. 3. Updated client locally. 4. We're unable to connect to DNS routes after selecting them. The client log locally repeats the following: ``` 2024-10-11T15:22:33+02:00 INFO client/internal/routemanager/client.go:171: New chosen route is ***REDACTED ROUTE*** with peer ***REDACTED PEER*** with score 0.000000 for network [***REDACTED NETWORK***] 2024-10-11T15:22:33+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency 2024-10-11T15:22:38+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency 2024-10-11T15:22:51+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency 2024-10-11T15:23:03+02:00 INFO [peer: ***REDACTED PEER***] client/internal/peer/worker_relay.go:187: WireGuard handshake timed out, closing relay connection: 1970-01-01 01:00:00 +0100 CET 2024-10-11T15:23:03+02:00 INFO [relay: rel://***REDACTED COORDINATOR DOMAIN***:7777] relay/client/client.go:501: free up connection to peer: ***REDACTED*** 2024-10-11T15:23:03+02:00 ERRO client/internal/wgproxy/usp/proxy.go:133: failed to read from remote conn: rel://***REDACTED COORDINATOR DOMAIN***:7777, EOF 2024-10-11T15:23:03+02:00 WARN client/internal/wgproxy/usp/proxy.go:122: error in proxy to local loop: 1 error occurred: * remote conn: connection already closed 2024-10-11T15:23:03+02:00 WARN client/internal/routemanager/client.go:160: The network [***REDACTED NETWORK***] has not been assigned a routing peer as no peers from the list [***REDACTED PEER***] are currently connected 2024-10-11T15:23:04+02:00 INFO [relay: rel://***REDACTED COORDINATOR DOMAIN***:7777] relay/client/client.go:214: open connection to peer: ***REDACTED*** 2024-10-11T15:23:04+02:00 INFO [peer: ***REDACTED PEER***] client/internal/peer/conn.go:547: created new wgProxy for relay connection: 127.0.0.1:53261 2024-10-11T15:23:04+02:00 INFO [peer: ***REDACTED PEER***] client/internal/peer/conn.go:588: start to communicate with peer via relay 2024-10-11T15:23:04+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency 2024-10-11T15:23:04+02:00 INFO client/internal/routemanager/client.go:171: New chosen route is ***REDACTED ROUTE*** with peer ***REDACTED PEER*** with score 0.000000 for network [***REDACTED NETWORK***] 2024-10-11T15:23:04+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency 2024-10-11T15:23:11+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency 2024-10-11T15:23:27+02:00 WARN client/internal/routemanager/client.go:130: peer ***REDACTED PEER*** has 0 latency ``` **Expected behavior** We expected to be able to connect the the DNS route without an issue in this new release. When we roll back to v0.29.4 everything works. **Are you using NetBird Cloud?** We are using Self Hosted Netbird. **NetBird version** ``` ➜ netbird version 0.30.0 ``` **NetBird status -dA output:** In this case we can not add the status but for the route we want to use the peer is shown as connected. After we reload the page or try to connect to the page that DNS route links to it shows disconnected momentarily. **Do you face any (non-mobile) client issues?** Please provide the file created by `netbird debug for 1m -AS`. We advise reviewing the anonymized files for any remaining PII. **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** What we notice is the following : 1: We get connected to the peer we want: ``` New chosen route is XXXXXXXXX with peer XXXXXXXXX with score 0.000000 for network [XXXXXXXX]``` 2: Error happens: ``` 2024-10-11T15:23:03+02:00 ERRO client/internal/wgproxy/usp/proxy.go:133: failed to read from remote conn: rel://*********:7777, EOF 2024-10-11T15:23:03+02:00 WARN client/internal/wgproxy/usp/proxy.go:122: error in proxy to local loop: 1 error occurred: * remote conn: connection already closed 2024-10-11T15:23:03+02:00 WARN client/internal/routemanager/client.go:160: The network [***********] has not been assigned a routing peer as no peers from the list [***************] are currently connected 2024-10-11T15:23:04+02:00 INFO [relay: rel://****************:7777] relay/client/client.go:214: open connection to peer: ******** 2024-10-11T15:23:04+02:00 INFO [peer: ***********] client/internal/peer/conn.go:547: created new wgProxy for relay connection: 127.0.0.1:53261``` 3: The peer gets assigned again. ```2024-10-11T15:23:03+02:00 WARN client/internal/routemanager/client.go:160: The network [XXXXXXXX] has not been assigned a routing peer as no peers from the list [XXXXXXXXXXX] are currently connected``` 4: This repeats every time we want to connect to the same DNS route. 5: The same issue happens when we update to v0.30.1 as well.
saavagebueno added the triage-needed label 2025-11-20 05:28:32 -05:00
saavagebueno commented 2025-11-20 05:28:33 -05:00
Author
Owner
Copy Link

@deniritech commented on GitHub (Oct 18, 2024):

Fixed on 0.30.2

@deniritech commented on GitHub (Oct 18, 2024): Fixed on 0.30.2
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#1327
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?