Error issuing 'netbird down' command #2046

Closed
opened 2025-11-20 06:11:51 -05:00 by saavagebueno · 1 comment
Owner

Originally created by @pri11er on GitHub (Jul 4, 2025).

Originally assigned to: @pappz on GitHub.

Describe the problem

Issuing 'netbird down' command results in error and does not take effect. This only occurs if Lazy Connections is enable.

To Reproduce

$ sudo netbird down
2025-07-04T22:21:52-04:00 ERRO client/cmd/down.go:42: call service down method: rpc error: code = Unavailable desc = error reading from server: EOF
Error: rpc error: code = Unavailable desc = error reading from server: EOF

$ netbird down
2025-07-04T22:23:43-04:00 INFO ./caller_not_available:0: 2025/07/04 22:23:43 WARNING: [core] [Channel #1 SubChannel #2]grpc: addrConn.createTransport failed to connect to {Addr: "/var/run/netbird.sock", ServerName: "localhost", Attributes: {"<%!p(networktype.keyType=grpc.internal.transport.networktype)>": "unix" }, }. Err: connection error: desc = "transport: Error while dialing: dial unix /var/run/netbird.sock: connect: connection refused"

This only occurs if Lazy Connections is enable in the Dashboard under Settings -> Clients. If it is disabled, the 'netbird down' command executes properly. If you enable it and restart the client netbird service, the down command command fails. This has been reproducible back-and-forth with the same behavior each time.

NetBird version

Observed in NetBird 0.50.0
Self-Hosted

Debian GNU/Linux 12 (bookworm)
6.1.0-37-amd64

Ubuntu 24.04.2 LTS

Originally created by @pri11er on GitHub (Jul 4, 2025). Originally assigned to: @pappz on GitHub. **Describe the problem** Issuing 'netbird down' command results in error and does not take effect. This only occurs if Lazy Connections is enable. **To Reproduce** $ sudo netbird down 2025-07-04T22:21:52-04:00 ERRO client/cmd/down.go:42: call service down method: rpc error: code = Unavailable desc = error reading from server: EOF Error: rpc error: code = Unavailable desc = error reading from server: EOF $ netbird down 2025-07-04T22:23:43-04:00 INFO ./caller_not_available:0: 2025/07/04 22:23:43 WARNING: [core] [Channel #1 SubChannel #2]grpc: addrConn.createTransport failed to connect to {Addr: "/var/run/netbird.sock", ServerName: "localhost", Attributes: {"<%!p(networktype.keyType=grpc.internal.transport.networktype)>": "unix" }, }. Err: connection error: desc = "transport: Error while dialing: dial unix /var/run/netbird.sock: connect: connection refused" This only occurs if Lazy Connections is enable in the Dashboard under Settings -> Clients. If it is disabled, the 'netbird down' command executes properly. If you enable it and restart the client netbird service, the down command command fails. This has been reproducible back-and-forth with the same behavior each time. **NetBird version** Observed in NetBird 0.50.0 Self-Hosted Debian GNU/Linux 12 (bookworm) 6.1.0-37-amd64 Ubuntu 24.04.2 LTS
saavagebueno added the triage-needed label 2025-11-20 06:11:51 -05:00
Author
Owner

@jackblk commented on GitHub (Jul 5, 2025):

Same issue. In my case, I only upgraded the client to 0.50.0, but my management is still 0.49.0. Seems to be client bug.

@jackblk commented on GitHub (Jul 5, 2025): Same issue. In my case, I only upgraded the client to 0.50.0, but my management is still 0.49.0. Seems to be client bug.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2046