Client enables all the exit nodes and network routes after restart #1051

Closed
opened 2025-11-20 05:23:07 -05:00 by saavagebueno · 5 comments
Owner

Originally created by @ramphex on GitHub (Jul 9, 2024).

I'm having this issue on several devices: Windows, MacOS, Linux. After a restart, the client enables all of the available exit nodes and every single available network route. I can't imagine any case where I would want this by default. The client should remember whatever was toggled and those settings should remain the same, even after a restart, until changed.

Originally created by @ramphex on GitHub (Jul 9, 2024). I'm having this issue on several devices: Windows, MacOS, Linux. After a restart, the client enables all of the available exit nodes and every single available network route. I can't imagine any case where I would want this by default. The client should remember whatever was toggled and those settings should remain the same, even after a restart, until changed.
saavagebueno added the clientwaiting-feedbackroutes labels 2025-11-20 05:23:07 -05:00
Author
Owner

@mlsmaycon commented on GitHub (Jul 10, 2024):

This is the current behavior, we will introduce persistent selection in the coming releases.

@mlsmaycon commented on GitHub (Jul 10, 2024): This is the current behavior, we will introduce persistent selection in the coming releases.
Author
Owner

@florian-obradovic commented on GitHub (Nov 24, 2024):

@mlsmaycon do we have an ETA?
For me it's especially an issue if at home and the home route or exit node is still selected which causes network issues...

@florian-obradovic commented on GitHub (Nov 24, 2024): @mlsmaycon do we have an ETA? For me it's especially an issue if at home and the home route or exit node is still selected which causes network issues...
Author
Owner

@ramphex commented on GitHub (Nov 24, 2024):

This hasn’t been fixed yet? I had this issue in July and ended up switching to another software as this broken feature was causing too many issues.

@ramphex commented on GitHub (Nov 24, 2024): This hasn’t been fixed yet? I had this issue in July and ended up switching to another software as this broken feature was causing too many issues.
Author
Owner

@nazarewk commented on GitHub (Apr 28, 2025):

Hello @ramphex,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @ramphex, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
Author
Owner

@mlsmaycon commented on GitHub (Jun 1, 2025):

closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.

@mlsmaycon commented on GitHub (Jun 1, 2025): closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1051