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

same management-url, different peers #2199

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

Originally created by @HMK2501 on GitHub (Aug 18, 2025).

I have the strangest situation. My selfhosted-AzureID netbird was on a machine. I "moved" it to another machine and switched domains : the new machine now have the dns of the previous machine so that users do not change their config. I shutted down the old machine.

With my account (as owner in Azure), i was able to connect and manage my account in the new management. Some servers that use setup keys also can connect to the new management.
All my users now say they can't access the servers : their clients say "connected" but i don't see them in management AND when they "status -d", they only see themselves, not the servers or me. We all connect to the same url (https://vpn.mydomain.fr:33073, "resolve-dnsname" on their machine points to the same address as mine)

On a blank client machine that never had netbird installed, i created 2 profiles : mine and a user that have the problem. The situation is as i described on the same machine : when i connect with my profile we see the servers, when he connects we see only the machines of other users.
When i give a new setup key to a user, he can connect but i still don't see him and he sees other users that have the problem.

Users heavily relies on the GUI while i only used the cli. On the machine with the 2 profiles we used the cli.

To Reproduce

Change the host machine of a Netbird ?

Expected behavior

I wanted user to connect like the moving never was a problem for them.

NetBird version

management and clients : 0.54.2
most of my users have older versions. i updated one and saw the same behaviour

Is any other VPN software installed?

No

Debug output

"netbird status -d" have the same management-url but the peers are different between me and users

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

"netbird debug for 1m -AS -U" for a problematic user :
7b780f38f46effc7c832201d92f2fd19f2e9647f97c541d384ecba94a9fa8d45/12e9f409-49a2-4dce-af14-0fbcf4c188ab

"netbird debug for 1m -AS -U" from my machine :
7b780f38f46effc7c832201d92f2fd19f2e9647f97c541d384ecba94a9fa8d45/fdb17267-3970-4715-adbd-23e76b0734be

i have a bunch of these in "docker compose logs management" :

`management-1 | 2025-08-18T15:51:06Z WARN [context: HTTP, requestID: e65e1c37-b7f0-4958-9a71-88e611e5514a] management/server/store/sql_store.go:2830: grpc context ended early, error: context canceled

...

management-1 | 2025-08-18T16:02:49Z WARN [context: HTTP, requestID: f379fa7f-9149-4364-a00a-ed53c7ed7600, accountID: cvpvpnk84iqs73f4g5f0, userID: 515f779f-1efd-477d-9513-16ac738b226c] management/server/store/sql_store.go:2830: grpc context ended early, error: context canceled`

Additional context

I moved from a baremetal's VM behind NAT with rootless docker to a simple VPS (with rootful docker) on the same provider. We all use windows clients. When we connect, we are asked to identify with Microsoft and it works.

I have no idea where this behaviour could come from. Any help would be appreciated.

Originally created by @HMK2501 on GitHub (Aug 18, 2025). I have the strangest situation. My selfhosted-AzureID netbird was on a machine. I "moved" it to another machine and switched domains : the new machine now have the dns of the previous machine so that users do not change their config. I shutted down the old machine. With my account (as owner in Azure), i was able to connect and manage my account in the new management. Some servers that use setup keys also can connect to the new management. All my users now say they can't access the servers : their clients say "connected" but i don't see them in management AND when they "status -d", they only see themselves, not the servers or me. We all connect to the same url (https://vpn.mydomain.fr:33073, "resolve-dnsname" on their machine points to the same address as mine) On a blank client machine that never had netbird installed, i created 2 profiles : mine and a user that have the problem. The situation is as i described on the same machine : when i connect with my profile we see the servers, when he connects we see only the machines of other users. When i give a new setup key to a user, he can connect but i still don't see him and he sees other users that have the problem. Users heavily relies on the GUI while i only used the cli. On the machine with the 2 profiles we used the cli. **To Reproduce** Change the host machine of a Netbird ? **Expected behavior** I wanted user to connect like the moving never was a problem for them. **NetBird version** management and clients : 0.54.2 most of my users have older versions. i updated one and saw the same behaviour **Is any other VPN software installed?** No **Debug output** "netbird status -d" have the same management-url but the peers are different between me and users Create and upload a debug bundle, and share the returned file key: "netbird debug for 1m -AS -U" for a problematic user : 7b780f38f46effc7c832201d92f2fd19f2e9647f97c541d384ecba94a9fa8d45/12e9f409-49a2-4dce-af14-0fbcf4c188ab "netbird debug for 1m -AS -U" from my machine : 7b780f38f46effc7c832201d92f2fd19f2e9647f97c541d384ecba94a9fa8d45/fdb17267-3970-4715-adbd-23e76b0734be i have a bunch of these in "docker compose logs management" : `management-1 | 2025-08-18T15:51:06Z WARN [context: HTTP, requestID: e65e1c37-b7f0-4958-9a71-88e611e5514a] management/server/store/sql_store.go:2830: grpc context ended early, error: context canceled ... management-1 | 2025-08-18T16:02:49Z WARN [context: HTTP, requestID: f379fa7f-9149-4364-a00a-ed53c7ed7600, accountID: cvpvpnk84iqs73f4g5f0, userID: 515f779f-1efd-477d-9513-16ac738b226c] management/server/store/sql_store.go:2830: grpc context ended early, error: context canceled` **Additional context** I moved from a baremetal's VM behind NAT with rootless docker to a simple VPS (with rootful docker) on the same provider. We all use windows clients. When we connect, we are asked to identify with Microsoft and it works. I have no idea where this behaviour could come from. Any help would be appreciated.
saavagebueno added the triage-needed label 2025-11-20 07:05:43 -05:00
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#2199
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?