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

Ordinary users cannot connect to the network #2426

New Issue
Open
opened 2025-11-20 07:09:36 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 07:09:36 -05:00
Owner
Copy Link

Originally created by @YOMO-Lee on GitHub (Oct 29, 2025).

Here are the issues I encountered while using Netbird:

1、I'm using the Windows client. Every time I restart my computer, even if I don't connect to Netbird, it seems that Netbird is still working, and the access between nodes remains normal. I hope that if the computer restarts, Netbird's network will stop automatically. Moreover, it would be better to have a setting to automatically disconnect the Netbird network after a certain period of time or when there is no traffic for a specific duration. Can this be achieved?

2、I'm currently using a self-hosted service. I have registered new users. The administrator user can log in to the Netbird network normally, but when a regular user logs in, it shows "login successful" but the Netbird network shows "connection failed".

3、Can each node be set to automatically remove itself from the node list after being offline for a certain period of time?

Originally created by @YOMO-Lee on GitHub (Oct 29, 2025). Here are the issues I encountered while using Netbird: 1、I'm using the Windows client. Every time I restart my computer, even if I don't connect to Netbird, it seems that Netbird is still working, and the access between nodes remains normal. I hope that if the computer restarts, Netbird's network will stop automatically. Moreover, it would be better to have a setting to automatically disconnect the Netbird network after a certain period of time or when there is no traffic for a specific duration. Can this be achieved? 2、I'm currently using a self-hosted service. I have registered new users. The administrator user can log in to the Netbird network normally, but when a regular user logs in, it shows "login successful" but the Netbird network shows "connection failed". 3、Can each node be set to automatically remove itself from the node list after being offline for a certain period of time?
saavagebueno added the self-hosting label 2025-11-20 07:09:36 -05:00
saavagebueno commented 2025-11-20 07:09:37 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Oct 30, 2025):

1、I'm using the Windows client. Every time I restart my computer, even if I don't connect to Netbird, it seems that Netbird is still working, and the access between nodes remains normal. I hope that if the computer restarts, Netbird's network will stop automatically. Moreover, it would be better to have a setting to automatically disconnect the Netbird network after a certain period of time or when there is no traffic for a specific duration. Can this be achieved?

NetBird client runs as a background/system-wide daemon independent from the graphical application. It will be logged in as long as the login session is valid (12h by default as far as I remember or permanent when using Setup Keys). You can also disable "Connect on Startup" (GUI) or netbird up --disable-auto-connect (CLI).

3、Can each node be set to automatically remove itself from the node list after being offline for a certain period of time?

There are Ephemeral Setup keys that get cleaned up from backend 10 minutes after going offline. This is in opposition to the session expiration for Users not affecting the backend configuration of the Peer.

2、I'm currently using a self-hosted service. I have registered new users. The administrator user can log in to the Netbird network normally, but when a regular user logs in, it shows "login successful" but the Netbird network shows "connection failed".

Could you make some screenshots, maybe gather a debug bundle with netbird debug for 1m -U while trying to log in?

@nazarewk commented on GitHub (Oct 30, 2025): > 1、I'm using the Windows client. Every time I restart my computer, even if I don't connect to Netbird, it seems that Netbird is still working, and the access between nodes remains normal. I hope that if the computer restarts, Netbird's network will stop automatically. Moreover, it would be better to have a setting to automatically disconnect the Netbird network after a certain period of time or when there is no traffic for a specific duration. Can this be achieved? NetBird client runs as a background/system-wide daemon independent from the graphical application. It will be logged in as long as the login session is valid (12h by default as far as I remember or permanent when using Setup Keys). You can also disable "Connect on Startup" (GUI) or `netbird up --disable-auto-connect` (CLI). > 3、Can each node be set to automatically remove itself from the node list after being offline for a certain period of time? There are Ephemeral Setup keys that get cleaned up from backend 10 minutes after going offline. This is in opposition to the session expiration for Users not affecting the backend configuration of the Peer. > 2、I'm currently using a self-hosted service. I have registered new users. The administrator user can log in to the Netbird network normally, but when a regular user logs in, it shows "login successful" but the Netbird network shows "connection failed". Could you make some screenshots, maybe gather a debug bundle with `netbird debug for 1m -U` while trying to log in?
saavagebueno commented 2025-11-20 07:09:37 -05:00
Author
Owner
Copy Link

@YOMO-Lee commented on GitHub (Oct 31, 2025):

thx , @nazarewk

NetBird client runs as a background/system-wide daemon independent from the graphical application. It will be logged in as long as the login session is valid (12h by default as far as I remember or permanent when using Setup Keys). You can also disable "Connect on Startup" (GUI) or (CLI).netbird up --disable-auto-connect

May I ask if Connect on Startup and netbird up --disable-auto-connect are set on the server side or the client side, and if on the server side, where are they set

Could you make some screenshots, maybe gather a debug bundle with while trying to log in?netbird debug for 1m -U

Image Image

By observing the logs, I learned that this peer has already been registered
Putting aside the question of whether the logic is reasonable, I think it would be better to return this kind of error to the user through a prompt. Currently, only a login error is displayed in the bottom right corner, which leaves us very confused

@YOMO-Lee commented on GitHub (Oct 31, 2025): thx , @nazarewk > NetBird client runs as a background/system-wide daemon independent from the graphical application. It will be logged in as long as the login session is valid (12h by default as far as I remember or permanent when using Setup Keys). You can also disable "Connect on Startup" (GUI) or (CLI).`netbird up --disable-auto-connect` May I ask if `Connect on Startup` and `netbird up --disable-auto-connect` are set on the server side or the client side, and if on the server side, where are they set > Could you make some screenshots, maybe gather a debug bundle with while trying to log in?`netbird debug for 1m -U` <img width="2560" height="1380" alt="Image" src="https://github.com/user-attachments/assets/3e157d91-514f-4a90-82ba-072c61999dce" /> <img width="2264" height="1235" alt="Image" src="https://github.com/user-attachments/assets/20cd9015-92eb-4bd9-a9d6-5bed19554049" /> By observing the logs, I learned that this peer has already been registered Putting aside the question of whether the logic is reasonable, I think it would be better to return this kind of error to the user through a prompt. Currently, only a login error is displayed in the bottom right corner, which leaves us very confused
saavagebueno commented 2025-11-20 07:09:37 -05:00
Author
Owner
Copy Link

@PowershellScripter commented on GitHub (Nov 4, 2025):

@YOMO-Lee
the disabling of auto connect is set on the client side. When you set that flag via the cli, it adds the following param in the netbird config file ["DisableAutoConnect": true,] under "C:\ProgramData\NetBird".

@PowershellScripter commented on GitHub (Nov 4, 2025): @YOMO-Lee the disabling of auto connect is set on the client side. When you set that flag via the cli, it adds the following param in the netbird config file ["DisableAutoConnect": true,] under "C:\ProgramData\NetBird".
saavagebueno commented 2025-11-20 07:09:37 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Nov 4, 2025):

@YOMO-Lee I am pretty sure the GUI losing connectivity to the background daemon is an issue we are currently addressing (or already have), can you check in with us next week/after the next release in case you still have it?

@nazarewk commented on GitHub (Nov 4, 2025): @YOMO-Lee I am pretty sure the GUI losing connectivity to the background daemon is an issue we are currently addressing (or already have), can you check in with us next week/after the next release in case you still have it?
saavagebueno commented 2025-11-20 07:09:37 -05:00
Author
Owner
Copy Link

@YOMO-Lee commented on GitHub (Nov 5, 2025):

@YOMO-Lee the disabling of auto connect is set on the client side. When you set that flag via the cli, it adds the following param in the netbird config file ["DisableAutoConnect": true,] under "C:\ProgramData\NetBird".

As an administrator, I hope to set up a feature on the server that prohibits automatic connection, requiring users to manually verify each time they restart their device. Is there any plan for this feature
If users are required to set up their own prohibitions against automatic connections, it will be difficult to manage

@YOMO-Lee commented on GitHub (Nov 5, 2025): > [@YOMO-Lee](https://github.com/YOMO-Lee) the disabling of auto connect is set on the client side. When you set that flag via the cli, it adds the following param in the netbird config file ["DisableAutoConnect": true,] under "C:\ProgramData\NetBird". As an administrator, I hope to set up a feature on the server that prohibits automatic connection, requiring users to manually verify each time they restart their device. Is there any plan for this feature If users are required to set up their own prohibitions against automatic connections, it will be difficult to manage
saavagebueno commented 2025-11-20 07:09:37 -05:00
Author
Owner
Copy Link

@YOMO-Lee commented on GitHub (Nov 5, 2025):

@YOMO-Lee I am pretty sure the GUI losing connectivity to the background daemon is an issue we are currently addressing (or already have), can you check in with us next week/after the next release in case you still have it?

OK
But my problem is actually that the node has already been registered by other accounts. The logic is correct, but the client prompt is quite vague, which initially left me confused

@YOMO-Lee commented on GitHub (Nov 5, 2025): > [@YOMO-Lee](https://github.com/YOMO-Lee) I am pretty sure the GUI losing connectivity to the background daemon is an issue we are currently addressing (or already have), can you check in with us next week/after the next release in case you still have it? OK But my problem is actually that the node has already been registered by other accounts. The logic is correct, but the client prompt is quite vague, which initially left me confused
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 self-hosting
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#2426
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?