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

Closed
opened 2025-11-20 07:04:14 -05:00 by saavagebueno · 3 comments
Owner

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:14 -05:00
Author
Owner

@nazarewk commented on GitHub (Jul 29, 2025):

did you check management and/or Azure logs for errors based on user's IdP IDs (those should match across Azure and NetBird user ID)?

@nazarewk commented on GitHub (Jul 29, 2025): did you check management and/or Azure logs for errors based on user's IdP IDs (those should match across Azure and NetBird user ID)?
Author
Owner

@LeoFPS72 commented on GitHub (Jul 30, 2025):

This is the error im getting when trying to log in / register with a new user:

Image

And here are my management.json and docker-compose.yml files:

docker-compose.yml.txt

management.json

@LeoFPS72 commented on GitHub (Jul 30, 2025): This is the error im getting when trying to log in / register with a new user: <img width="1683" height="49" alt="Image" src="https://github.com/user-attachments/assets/a9f2166e-81f6-4175-ac6e-338e3f11e188" /> And here are my management.json and docker-compose.yml files: [docker-compose.yml.txt](https://github.com/user-attachments/files/21502755/docker-compose.yml.txt) [management.json](https://github.com/user-attachments/files/21502756/management.json)
Author
Owner

@LeoFPS72 commented on GitHub (Jul 31, 2025):

Solution: In the store.db database, delete all additional entries under accounts (all except the “main account” with which the existing users were registered) and account_oboardings, and adjust the domain in the accounts table. The new users will then be created correctly again.
and ofc delete all enries with the wrong account_id in the other tables in store.db

Image
@LeoFPS72 commented on GitHub (Jul 31, 2025): Solution: In the store.db database, delete all additional entries under accounts (all except the “main account” with which the existing users were registered) and account_oboardings, and adjust the domain in the accounts table. The new users will then be created correctly again. and ofc delete all enries with the wrong account_id in the other tables in store.db <img width="1308" height="136" alt="Image" src="https://github.com/user-attachments/assets/fb75e1f7-0c49-4ec8-b2db-cea127dbf623" />
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2124