Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

netbird-ui rolls back the daemon to default interface and port #1581

Closed
nazarewk opened this issue Feb 13, 2024 · 5 comments
Closed

netbird-ui rolls back the daemon to default interface and port #1581

nazarewk opened this issue Feb 13, 2024 · 5 comments
Labels

Comments

@nazarewk
Copy link
Contributor

Describe the problem

A complete opposite of #1562 : netbird-ui rolls back the daemon to default configuration wt0:51820 no matter what I set up on the actual systemd service.

NixOS/nixpkgs#287236 (comment)

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Are you using NetBird Cloud?

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

NetBird version

netbird version

NetBird status -d output:

If applicable, add the `netbird status -d' command output.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

@nazarewk
Copy link
Contributor Author

I tried locating the issue in the code, but cannot pinpoint anything.

@surik
Copy link
Contributor

surik commented Feb 14, 2024

Hi @nazarewk I was trying to reproduce the issue but not luck. Can you give more information about the version you use and maybe do an additional checks of the /etc/netbird/config.json. Where do you notice that values are reverted to the defaults?

@nazarewk
Copy link
Contributor Author

It happens when I Connect/login through the UI

@surik
Copy link
Contributor

surik commented Feb 14, 2024

Can you make an additional test to prove an assumption.

  1. Run netbird down
  2. Try to connect via CLI: netbird up --interface-name wt1 --wireguard-port 51840 or any other name/port
  3. Check /etc/netbird/config.json
  4. Disconnect via UI
  5. Connect via UI
  6. Check /etc/netbird/config.json

@nazarewk
Copy link
Contributor Author

During Slack conversation it was pointed out I was starting without any config whatsoever and neither netbird service up nor netbird-ui support passing the interface/port configuration.

So this is issue caused by #1562

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants