[GH-ISSUE #1565] /etc/netbird/config.json is being modified by client process #2692

Open
opened 2026-08-05 00:48:26 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @PavelNiedoba on GitHub (Feb 12, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1565

Describe the problem

I had working server with connected clients. I changed management port from default 443 to 9443.

To Reproduce
Have client installed and connected. then stop client netbird down Modify /etc/netbird/config.json

   ...
    "ManagementURL": {
        "Scheme": "https",
        "Opaque": "",
        "User": null,
        "Host": "vpn.xxx.eu:443",

change port 443 to 9443 and then start the client netbird up
you will see error message

2024-02-12T16:46:05+01:00 WARN client/cmd/root.go:195: retrying Login to the Management service in 1.135610787s due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded

then open /etc/netbird/config.json and you will see it was modified and port 443 is set again.

Expected behavior
/etc/netbird/config.json should never change unless being created for first time

A clear and concise description of what you expected to happen.
client should connect to new url

Are you using NetBird Cloud?
no

Please specify whether you use NetBird Cloud or self-host NetBird's control plane.
self hosted

NetBird version
025.5

NetBird status -d output:

Daemon status: LoginFailed

Run UP command to log in with SSO (interactive login):

 netbird up 

If you are running a self-hosted version and no SSO provider has been configured in your Management Server,
you can use a setup-key:

 netbird up --management-url <YOUR_MANAGEMENT_URL> --setup-key <YOUR_SETUP_KEY>

More info: https://docs.netbird.io/how-to/register-machines-using-setup-keys
Originally created by @PavelNiedoba on GitHub (Feb 12, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1565 **Describe the problem** I had working server with connected clients. I changed management port from default 443 to 9443. **To Reproduce** Have client installed and connected. then stop client `netbird down` Modify `/etc/netbird/config.json` ``` ... "ManagementURL": { "Scheme": "https", "Opaque": "", "User": null, "Host": "vpn.xxx.eu:443", ``` change port 443 to 9443 and then start the client `netbird up` you will see error message ``` 2024-02-12T16:46:05+01:00 WARN client/cmd/root.go:195: retrying Login to the Management service in 1.135610787s due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded ``` then open `/etc/netbird/config.json` and you will see it was modified and port 443 is set again. **Expected behavior** `/etc/netbird/config.json` should never change unless being created for first time A clear and concise description of what you expected to happen. client should connect to new url **Are you using NetBird Cloud?** no Please specify whether you use NetBird Cloud or self-host NetBird's control plane. self hosted **NetBird version** `025.5` **NetBird status -d output:** ``` Daemon status: LoginFailed Run UP command to log in with SSO (interactive login): netbird up If you are running a self-hosted version and no SSO provider has been configured in your Management Server, you can use a setup-key: netbird up --management-url <YOUR_MANAGEMENT_URL> --setup-key <YOUR_SETUP_KEY> More info: https://docs.netbird.io/how-to/register-machines-using-setup-keys ```
saavagebueno added the waiting-feedbackself-hosting labels 2026-08-05 00:48:26 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2692