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

Unable to register new peers/users via Azure IDP after copying Database #2121

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

Originally created by @LeoFPS72 on GitHub (Jul 29, 2025).

Describe the problem

The self-hosted Netbird system needed to be moved to a new domain, so Netbird was installed on a new server and configured with the new domain/address. To avoid having to recreate all the configurations (networks, policies, etc.), the store.db database from the old system was copied to the new one. Now, a few weeks later, it has been noticed that no new users/peers can be registered via Azure as IDP. Existing users/peers can still log in and everything works fine for them.

The authentication of new users also works correctly, but they never appear in the dashboard; it is as if a separate environment has been created for them. Although single account mode is enabled, a separate entry is created for them in the Accounts table in the database.

To Reproduce

  1. Set up a new self-hosted netbird system with Azure IDP
  2. Copy the database store.db from an existing system
  3. Try to regiester a new User with Azure as IDP

Expected behavior
expected that the new user could register and shows up in the dashboard.

Are you using NetBird Cloud?

self-hosted Netbird

NetBird version

v0.51.2

Image
Originally created by @LeoFPS72 on GitHub (Jul 29, 2025). **Describe the problem** The self-hosted Netbird system needed to be moved to a new domain, so Netbird was installed on a new server and configured with the new domain/address. To avoid having to recreate all the configurations (networks, policies, etc.), the store.db database from the old system was copied to the new one. Now, a few weeks later, it has been noticed that no new users/peers can be registered via Azure as IDP. Existing users/peers can still log in and everything works fine for them. The authentication of new users also works correctly, but they never appear in the dashboard; it is as if a separate environment has been created for them. Although single account mode is enabled, a separate entry is created for them in the Accounts table in the database. **To Reproduce** 1. Set up a new self-hosted netbird system with Azure IDP 2. Copy the database store.db from an existing system 3. Try to regiester a new User with Azure as IDP **Expected behavior** expected that the new user could register and shows up in the dashboard. **Are you using NetBird Cloud?** self-hosted Netbird **NetBird version** v0.51.2 <img width="942" height="217" alt="Image" src="https://github.com/user-attachments/assets/61374a98-b073-4cb5-a915-ea2d03a1622f" />
saavagebueno added the self-hosting label 2025-11-20 07:04:12 -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 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#2121
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?