[GH-ISSUE #5128] Auto updating the client forgets enabled networks and exit nodes #10757

Open
opened 2026-08-05 01:27:11 -04:00 by saavagebueno · 6 comments
Owner

Originally created by @ddkooker2 on GitHub (Jan 19, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5128

Describe the problem

Since the auto update was introduced I have reports from multiple users (Windows and MacOS) that after the auto update is performed the client connects but enables all networks and exit nodes by default and forgets the previous state (this was not an issue when manually updating).

To Reproduce

Steps to reproduce the behavior:

  1. Configure the netbird console to auto update the agent whenever possible
  2. Connect an outdated client to the management server
  3. Wait for the update to be done and the connection to be made
  4. See error

Expected behavior

I would expect the client to remember the enabled networks/exit nodes just as it does when manually installing the update of the client.

Are you using NetBird Cloud?

Self-Hosted

NetBird version

0.63.0

Is any other VPN software installed?

Yes, OpenVPN Client on some devices (problem exists on both Windows and MacOS laptops)

Debug output

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

netbird status -dA

Netbird-StatusOutput 19-01-2026 07-48.txt

Create and upload a debug bundle, and share the returned file key:

netbird debug for 1m -AS -U

Key: 584cf321fc320142d2eb6cd97691fc70d8c7334b632a7e3ca440b54eec725e2f/3380611f-c982-4d12-9fef-faefe418c5e7

Uploaded files are automatically deleted after 30 days.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

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 @ddkooker2 on GitHub (Jan 19, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5128 **Describe the problem** Since the auto update was introduced I have reports from multiple users (Windows and MacOS) that after the auto update is performed the client connects but enables all networks and exit nodes by default and forgets the previous state (this was not an issue when manually updating). **To Reproduce** Steps to reproduce the behavior: 1. Configure the netbird console to auto update the agent whenever possible 2. Connect an outdated client to the management server 3. Wait for the update to be done and the connection to be made 4. See error **Expected behavior** I would expect the client to remember the enabled networks/exit nodes just as it does when manually installing the update of the client. **Are you using NetBird Cloud?** Self-Hosted **NetBird version** `0.63.0` **Is any other VPN software installed?** Yes, OpenVPN Client on some devices (problem exists on both Windows and MacOS laptops) **Debug output** To help us resolve the problem, please attach the following anonymized status output netbird status -dA [Netbird-StatusOutput 19-01-2026 07-48.txt](https://github.com/user-attachments/files/24707040/Netbird-StatusOutput.19-01-2026.07-48.txt) Create and upload a debug bundle, and share the returned file key: netbird debug for 1m -AS -U Key: 584cf321fc320142d2eb6cd97691fc70d8c7334b632a7e3ca440b54eec725e2f/3380611f-c982-4d12-9fef-faefe418c5e7 *Uploaded files are automatically deleted after 30 days.* **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here. **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 2026-08-05 01:27:11 -04:00
Author
Owner

@MobileManiC commented on GitHub (Jan 23, 2026):

Yes, I think I can confirm that. Just tried to switch to auto-updates and noticed this behavior. This does not happen at all when installer for new version is run manually.

<!-- gh-comment-id:3788470672 --> @MobileManiC commented on GitHub (Jan 23, 2026): Yes, I think I can confirm that. Just tried to switch to auto-updates and noticed this behavior. This does not happen at all when installer for new version is run manually.
Author
Owner

@syr333x commented on GitHub (Jan 23, 2026):

Same thing. Checked macos/win 0.64.1. After restart gui - exit nodes shows

<!-- gh-comment-id:3791787808 --> @syr333x commented on GitHub (Jan 23, 2026): Same thing. Checked macos/win 0.64.1. After restart gui - exit nodes shows
Author
Owner

@syr333x commented on GitHub (Jan 23, 2026):

Thanks a lot for the great work and community contribution, but this issue has been very annoying for the last 5-10+ releases.

<!-- gh-comment-id:3791799915 --> @syr333x commented on GitHub (Jan 23, 2026): Thanks a lot for the great work and community contribution, but this issue has been very annoying for the last 5-10+ releases.
Author
Owner

@MobileManiC commented on GitHub (Mar 11, 2026):

Just tested with 0.66.4, problem is still present. It's the only thing preventing me from finally allowing automatic updates... 😢

<!-- gh-comment-id:4042410992 --> @MobileManiC commented on GitHub (Mar 11, 2026): Just tested with 0.66.4, problem is still present. It's the only thing preventing me from finally allowing automatic updates... 😢
Author
Owner

@MobileManiC commented on GitHub (May 6, 2026):

Just tested with 0.70.5, this is not happening any more - Exit node selection now survives automatic update on Windows.

This can be closed.

<!-- gh-comment-id:4392296451 --> @MobileManiC commented on GitHub (May 6, 2026): Just tested with 0.70.5, this is not happening any more - Exit node selection now survives automatic update on Windows. This can be closed.
Author
Owner

@sjansen1 commented on GitHub (Aug 3, 2026):

Autoupdate is currently really bad, sometimes the update never completes, the connection is not in the same state after update or user has to start netbird by hand and connect again.

<!-- gh-comment-id:5167446491 --> @sjansen1 commented on GitHub (Aug 3, 2026): Autoupdate is currently really bad, sometimes the update never completes, the connection is not in the same state after update or user has to start netbird by hand and connect again.
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#10757