SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-11 18:02:48 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

OpenWRT not able to login #1199

New Issue
Closed
opened 2025-11-20 05:25:47 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:25:47 -05:00
Owner
Copy Link

Originally created by @Gauss23 on GitHub (Sep 1, 2024).

Describe the problem

Clean installation of gl-inet AR300M with OpenWrt 22.03.4 with their firmware 4.3.17. Installed Netbird https://downloads.openwrt.org/snapshots/packages/mips_24kc/packages/netbird_0.28.9-r1_mips_24kc.ipk
Netbird up with setup key says:
Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
In the logfile I see:

2024-09-01T20:36:00Z ERRO client/server/server.go:262: failed login: context deadline exceeded
2024-09-01T20:36:00Z ERRO util/grpc/dialer.go:38: Failed to dial: dial: dial tcp ####:443: connect: invalid argument

Seems like a Go problem. Version 0.17 works for OpenWrt but is missing important features. Would be great to get the current version running. Looks like something changed between 0.17 and 0.28.9 with the go implementation to connect to the management server.

To Reproduce

  1. Fresh firmware on gl-inet AR300M
  2. Download netbird package from the snapshot tree
  3. install netbird
  4. run netbird up with setup-key
  5. wait until it times out and read the above error msg

Expected behavior

It should just connect, like it does with 0.17

Are you using NetBird Cloud?

self-hosted, but it doesn't matter, I tried it also with the the cloud version, same error

NetBird version

0.28.9

NetBird status -dA 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

Do you face any (non-mobile) client issues?

Please provide the file created by netbird debug for 1m -AS.
We advise reviewing the anonymized files for any remaining PII.
Output:
Error: failed to up: up already in progress: current status LoginFailed

Screenshots

none

Additional context

none

Originally created by @Gauss23 on GitHub (Sep 1, 2024). **Describe the problem** Clean installation of gl-inet AR300M with OpenWrt 22.03.4 with their firmware 4.3.17. Installed Netbird `https://downloads.openwrt.org/snapshots/packages/mips_24kc/packages/netbird_0.28.9-r1_mips_24kc.ipk ` Netbird up with setup key says: `Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded ` In the logfile I see: ``` 2024-09-01T20:36:00Z ERRO client/server/server.go:262: failed login: context deadline exceeded 2024-09-01T20:36:00Z ERRO util/grpc/dialer.go:38: Failed to dial: dial: dial tcp ####:443: connect: invalid argument ``` Seems like a Go problem. Version 0.17 works for OpenWrt but is missing important features. Would be great to get the current version running. Looks like something changed between 0.17 and 0.28.9 with the go implementation to connect to the management server. **To Reproduce** 1. Fresh firmware on gl-inet AR300M 2. Download netbird package from the snapshot tree 3. install netbird 4. run netbird up with setup-key 5. wait until it times out and read the above error msg **Expected behavior** It should just connect, like it does with 0.17 **Are you using NetBird Cloud?** self-hosted, but it doesn't matter, I tried it also with the the cloud version, same error **NetBird version** 0.28.9 **NetBird status -dA 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 **Do you face any (non-mobile) client issues?** Please provide the file created by `netbird debug for 1m -AS`. We advise reviewing the anonymized files for any remaining PII. Output: Error: failed to up: up already in progress: current status LoginFailed **Screenshots** none **Additional context** none
saavagebueno added the triage-needed label 2025-11-20 05:25:47 -05:00
saavagebueno commented 2025-11-20 05:25:48 -05:00
Author
Owner
Copy Link

@Gauss23 commented on GitHub (Sep 3, 2024):

Update: I exchanged the original gl-inet firmware with a vanilla OpenWRT installation. The newest Netbird package (atm 0.28.9) works perfectly.

@Gauss23 commented on GitHub (Sep 3, 2024): Update: I exchanged the original gl-inet firmware with a vanilla OpenWRT installation. The newest Netbird package (atm 0.28.9) works perfectly.
saavagebueno commented 2025-11-20 05:25:48 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Sep 3, 2024):

FYI: this might be caused by using legacy iptables instead of new nftables (or some other missing tool/kernel module) on the system running Netbird.
see https://github.com/netbirdio/netbird/issues/2116#issuecomment-2327236355

@nazarewk commented on GitHub (Sep 3, 2024): FYI: this might be caused by using legacy `iptables` instead of new `nftables` (or some other missing tool/kernel module) on the system running Netbird. see https://github.com/netbirdio/netbird/issues/2116#issuecomment-2327236355
saavagebueno commented 2025-11-20 05:25:48 -05:00
Author
Owner
Copy Link

@Gauss23 commented on GitHub (Sep 3, 2024):

Thanks for your hint. Looks like it’s the same problem indeed. I don’t want to go back to the stock firmware as the underlying OpenWrt firmware is older and the vanilla one feels better. Maybe I‘ll get another one to test it.
Interestingly enough I had a look at the function, which is creating the connection and there is a differentiation between running as root or as a different user. as root it uses the new custom connect and as normal user the legacy way.
But I was not able to trigger this if statement. Seems like netbird up was just telling the daemon to connect, which was running as root.
Maybe those exports could have helped.

@Gauss23 commented on GitHub (Sep 3, 2024): Thanks for your hint. Looks like it’s the same problem indeed. I don’t want to go back to the stock firmware as the underlying OpenWrt firmware is older and the vanilla one feels better. Maybe I‘ll get another one to test it. Interestingly enough I had a look at the function, which is creating the connection and there is a differentiation between running as root or as a different user. as root it uses the new custom connect and as normal user the legacy way. But I was not able to trigger this if statement. Seems like netbird up was just telling the daemon to connect, which was running as root. Maybe those exports could have helped.
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#1199
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?