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

0.51.0 Client issues #2072

New Issue
Closed
opened 2025-11-20 06:12:16 -05:00 by saavagebueno · 16 comments
saavagebueno commented 2025-11-20 06:12:16 -05:00
Owner
Copy Link

Originally created by @AuriokNomad on GitHub (Jul 15, 2025).

Full Tunnel Routes stop

When upgrading to 0.51.0 on either Windows client or linux client it breaks full tunnel routes, reverting back to 0.50.2 resolves the issue

Setup a linux client as an exit node for 0.0.0.0/0 and a windows client to connect to the client.

Are you using NetBird Cloud?
Yes

Please specify whether you use NetBird Cloud or self-host NetBird's control plane.
Cloud

NetBird version

0.51.0

Originally created by @AuriokNomad on GitHub (Jul 15, 2025). Full Tunnel Routes stop When upgrading to 0.51.0 on either Windows client or linux client it breaks full tunnel routes, reverting back to 0.50.2 resolves the issue Setup a linux client as an exit node for 0.0.0.0/0 and a windows client to connect to the client. **Are you using NetBird Cloud?** Yes Please specify whether you use NetBird Cloud or self-host NetBird's control plane. Cloud **NetBird version** 0.51.0
saavagebueno added the triage-needed label 2025-11-20 06:12:16 -05:00
saavagebueno commented 2025-11-20 06:12:17 -05:00
Author
Owner
Copy Link

@san983 commented on GitHub (Jul 15, 2025):

We've experienced the same problem on Ubuntu 24.04, had to rollback to https://github.com/netbirdio/netbird/releases/tag/v0.50.2 as well, although https://github.com/netbirdio/netbird/releases/tag/v0.50.3 looks ok as well.

Basically the Netbird client kept restarting over and over

Jul 15 13:41:39 HOSTNAME systemd[1]: netbird.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
@san983 commented on GitHub (Jul 15, 2025): We've experienced the same problem on Ubuntu 24.04, had to rollback to https://github.com/netbirdio/netbird/releases/tag/v0.50.2 as well, although https://github.com/netbirdio/netbird/releases/tag/v0.50.3 looks ok as well. Basically the Netbird client kept restarting over and over ``` Jul 15 13:41:39 HOSTNAME systemd[1]: netbird.service: Main process exited, code=exited, status=2/INVALIDARGUMENT ```
saavagebueno commented 2025-11-20 06:12:18 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Jul 15, 2025):

@san983 @AuriokNomad is it still happening for you? There was a brief moment when the clients were crashing the release's deployment has finished, but it should be working fine after that.

@nazarewk commented on GitHub (Jul 15, 2025): @san983 @AuriokNomad is it still happening for you? There was a brief moment when the clients were crashing the release's deployment has finished, but it should be working fine after that.
saavagebueno commented 2025-11-20 06:12:18 -05:00
Author
Owner
Copy Link

@cipherw0lf commented on GitHub (Jul 15, 2025):

How to update the relay server as the release post noted?
Will be holding back on this update as we also have Ubuntu nodes.

@cipherw0lf commented on GitHub (Jul 15, 2025): How to update the relay server as the release post noted? Will be holding back on this update as we also have Ubuntu nodes.
saavagebueno commented 2025-11-20 06:12:18 -05:00
Author
Owner
Copy Link

@fmedinaq commented on GitHub (Jul 15, 2025):

Same here. All tunnel routes stopped. It happened with 0.51.0 in macOS and linux.. I didn't rollback yet. Im using: self-host NetBird's control plane

@fmedinaq commented on GitHub (Jul 15, 2025): Same here. All tunnel routes stopped. It happened with 0.51.0 in macOS and linux.. I didn't rollback yet. Im using: self-host NetBird's control plane
saavagebueno commented 2025-11-20 06:12:18 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jul 15, 2025):

Hey folks, sorry about the issue. We are working on an approach that would not result in the connection restart. In the meantime, if you are self-hosting, you need to upgrade your relay servers to the 0.51.0 version.

The NetBird cloud relay servers have been updated already. If you are facing issues with our cloud, can you please share the logs from the following paths to support@netbird.io

Paths:

# Windos 
C:\ProgramData\NetBird\client.log
C:\ProgramData\NetBird\netbird.err
# Linux
/var/log/netbird/client.log
/var/log/netbird/netbird.err
# MacOS
/var/log/netbird/client.log
/var/lib/netbird.err.log
@mlsmaycon commented on GitHub (Jul 15, 2025): Hey folks, sorry about the issue. We are working on an approach that would not result in the connection restart. In the meantime, if you are self-hosting, you need to upgrade your relay servers to the 0.51.0 version. The NetBird cloud relay servers have been updated already. If you are facing issues with our cloud, can you please share the logs from the following paths to support@netbird.io Paths: ```shell # Windos C:\ProgramData\NetBird\client.log C:\ProgramData\NetBird\netbird.err # Linux /var/log/netbird/client.log /var/log/netbird/netbird.err # MacOS /var/log/netbird/client.log /var/lib/netbird.err.log ```
saavagebueno commented 2025-11-20 06:12:18 -05:00
Author
Owner
Copy Link

@fmedinaq commented on GitHub (Jul 15, 2025):

Update to the issue in macOS. I did the following steps and worked for me:

  1. Updated the coordinator server.
  2. docker compose down and up for the coordinator
  3. Install the 0.50.3 client on macOS
  4. install the 0.51.0 client on macOS

All seems works ok.

@fmedinaq commented on GitHub (Jul 15, 2025): Update to the issue in macOS. I did the following steps and worked for me: 1. Updated the coordinator server. 2. docker compose down and up for the coordinator 3. Install the 0.50.3 client on macOS 4. install the 0.51.0 client on macOS All seems works ok.
saavagebueno commented 2025-11-20 06:12:18 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jul 15, 2025):

for relay only using our scripts:

docker compose pull relay
docker compose up -d --force-recreate relay
@mlsmaycon commented on GitHub (Jul 15, 2025): for relay only using our scripts: ```shell docker compose pull relay docker compose up -d --force-recreate relay ```
saavagebueno commented 2025-11-20 06:12:18 -05:00
Author
Owner
Copy Link

@misterlegend commented on GitHub (Jul 15, 2025):

Updating the relay server worked for my self-hosted instance, thanks!

@misterlegend commented on GitHub (Jul 15, 2025): Updating the relay server worked for my self-hosted instance, thanks!
saavagebueno commented 2025-11-20 06:12:19 -05:00
Author
Owner
Copy Link

@kartikg-salaryse commented on GitHub (Jul 15, 2025):

@misterlegend just the relay server worked ? Can you please tell the steps to troubleshoot ?

@kartikg-salaryse commented on GitHub (Jul 15, 2025): @misterlegend just the relay server worked ? Can you please tell the steps to troubleshoot ?
saavagebueno commented 2025-11-20 06:12:19 -05:00
Author
Owner
Copy Link

@misterlegend commented on GitHub (Jul 15, 2025):

@kartikg-salaryse Correct, I just ssh'd into my NB server and pulled the relay image and recreated as outlined in https://github.com/netbirdio/netbird/issues/4152#issuecomment-3074728311

@misterlegend commented on GitHub (Jul 15, 2025): @kartikg-salaryse Correct, I just ssh'd into my NB server and pulled the relay image and recreated as outlined in https://github.com/netbirdio/netbird/issues/4152#issuecomment-3074728311
saavagebueno commented 2025-11-20 06:12:19 -05:00
Author
Owner
Copy Link

@leungincd commented on GitHub (Jul 15, 2025):

me too
update my windows client to 0.51
then link loss
i have many diffent tape clients
when i rollback to 0.50.3 ,question repaired
windows now OK
but i have some other like liunx & debian ,now still can't work.
:(

@leungincd commented on GitHub (Jul 15, 2025): me too update my windows client to 0.51 then link loss i have many diffent tape clients when i rollback to 0.50.3 ,question repaired windows now OK but i have some other like liunx & debian ,now still can't work. :(
saavagebueno commented 2025-11-20 06:12:19 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jul 15, 2025):

@leungincd @kartikg-salaryse Updating the relay service is the best approach and should resolve for all clients

@mlsmaycon commented on GitHub (Jul 15, 2025): @leungincd @kartikg-salaryse Updating the relay service is the best approach and should resolve for all clients
saavagebueno commented 2025-11-20 06:12:19 -05:00
Author
Owner
Copy Link

@kartikg-salaryse commented on GitHub (Jul 15, 2025):

@leungincd @kartikg-salaryse Updating the relay service is the best approach and should resolve for all clients

Updating the relay service didn't work . For now rolled back all the clients to 0.50.3 to ensure stability.

@kartikg-salaryse commented on GitHub (Jul 15, 2025): > @leungincd @kartikg-salaryse Updating the relay service is the best approach and should resolve for all clients Updating the relay service didn't work . For now rolled back all the clients to `0.50.3` to ensure stability.
saavagebueno commented 2025-11-20 06:12:19 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jul 15, 2025):

Can you run:

docker inspect <relay_container_id> | grep -i version`

If that don't return 0.51.0 then the upgrade failed, if it does return 0.51.0, the issue might be something unrelated to relay

@mlsmaycon commented on GitHub (Jul 15, 2025): Can you run: ``` docker inspect <relay_container_id> | grep -i version` ``` If that don't return 0.51.0 then the upgrade failed, if it does return 0.51.0, the issue might be something unrelated to relay
saavagebueno commented 2025-11-20 06:12:20 -05:00
Author
Owner
Copy Link

@san983 commented on GitHub (Jul 15, 2025):

@san983 @AuriokNomad is it still happening for you? There was a brief moment when the clients were crashing the release's deployment has finished, but it should be working fine after that.

The only canary I left with v0.51.0 hasn't had any problem since ~1pm UTC, so it looks good.

@san983 commented on GitHub (Jul 15, 2025): > [@san983](https://github.com/san983) [@AuriokNomad](https://github.com/AuriokNomad) is it still happening for you? There was a brief moment when the clients were crashing the release's deployment has finished, but it should be working fine after that. The only canary I left with v0.51.0 hasn't had any problem since ~1pm UTC, so it looks good.
saavagebueno commented 2025-11-20 06:12:20 -05:00
Author
Owner
Copy Link

@AuriokNomad commented on GitHub (Jul 16, 2025):

Connections are functioning properly on the newest version 0.51.1

Thanks!

@AuriokNomad commented on GitHub (Jul 16, 2025): Connections are functioning properly on the newest version 0.51.1 Thanks!
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#2072
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?