Management Service login issue #404

Open
opened 2025-11-20 05:10:50 -05:00 by saavagebueno · 50 comments
Owner

Originally created by @Sxndxr on GitHub (Aug 3, 2023).

Hello,
I started using Netbird yesterday on my linux machine. It was working fine, but once i restarted my machine it displays the message "2023-08-03T10:19:37+01:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.098619925s due to error rpc error: code = Unknown desc = getting pkce authorization flow info failed with error: context deadline exceeded" when i run "sudo netbird up" even with my setup-key. I tried uninstall/reinstall but nothing worked. Can you help please ?

Steps to reproduce the behavior:

  1. Install Netbird
  2. sudo netbird up
  3. restart machine
  4. sudo netbird up
  5. 2023-08-03T10:19:37+01:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.098619925s due to error rpc error: code = Unknown desc = getting pkce authorization flow info failed with error: context deadline exceeded

The expected behavior is to have the same as yesterday when i installed it. I expected it to display "connected" after i run the command "sudo netbird up".

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://www.netbird.io/docs/overview/setup-keys

Screenshots
image
image

Thanks for help

Originally created by @Sxndxr on GitHub (Aug 3, 2023). Hello, I started using Netbird yesterday on my linux machine. It was working fine, but once i restarted my machine it displays the message "2023-08-03T10:19:37+01:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.098619925s due to error rpc error: code = Unknown desc = getting pkce authorization flow info failed with error: context deadline exceeded" when i run "sudo netbird up" even with my setup-key. I tried uninstall/reinstall but nothing worked. Can you help please ? Steps to reproduce the behavior: 1. Install Netbird 2. sudo netbird up 3. restart machine 4. sudo netbird up 5. 2023-08-03T10:19:37+01:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.098619925s due to error rpc error: code = Unknown desc = getting pkce authorization flow info failed with error: context deadline exceeded The expected behavior is to have the same as yesterday when i installed it. I expected it to display "connected" after i run the command "sudo netbird up". **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://www.netbird.io/docs/overview/setup-keys **Screenshots** ![image](https://github.com/netbirdio/netbird/assets/86080510/9e4eed4b-46e1-4925-af80-49e63361f5c8) ![image](https://github.com/netbirdio/netbird/assets/86080510/2f994e60-a727-4a79-b1b9-3ee5e2618be5) Thanks for help
saavagebueno added the clientUX labels 2025-11-20 05:10:50 -05:00
Author
Owner

@gmatasba commented on GitHub (Aug 3, 2023):

Hi.
Almost identical similar issue here. Just to add some additional context of my case that may be helpful:

  1. For me, errors with the connection to Management Server start as soon as seconds after the registration as a peer. (see image attached)
  2. The only instance in which I am seeing this issue myself is in a docker Ubuntu container, Netbird client is working as expected in all other machines in which I have installed it. The container I am mentioning is inside the same server as the management service and it is running a client because I wanted to use as a routing peer in order to not have to create a separate machine.

I have been trying to debug the error but I have had no luck so far, any help or discoveries on the matter would be greatly appreciated if shared.

Thanks!

netbird_error

@gmatasba commented on GitHub (Aug 3, 2023): Hi. Almost identical similar issue here. Just to add some additional context of my case that may be helpful: 1. For me, errors with the connection to Management Server start as soon as seconds after the registration as a peer. (see image attached) 2. The only instance in which I am seeing this issue myself is in a docker Ubuntu container, Netbird client is working as expected in all other machines in which I have installed it. The container I am mentioning is inside the same server as the management service and it is running a client because I wanted to use as a routing peer in order to not have to create a separate machine. I have been trying to debug the error but I have had no luck so far, any help or discoveries on the matter would be greatly appreciated if shared. Thanks! ![netbird_error](https://github.com/netbirdio/netbird/assets/31928542/3fe8fff8-a6a3-47b6-a78c-87659626b1e7)
Author
Owner

@bcmmbaga commented on GitHub (Aug 3, 2023):

Could you please check if there are any error logs available at /var/log/netbird/client.log and /var/log/netbird/netbird.err?

@bcmmbaga commented on GitHub (Aug 3, 2023): Could you please check if there are any error logs available at `/var/log/netbird/client.log` and `/var/log/netbird/netbird.err`?
Author
Owner

@gmatasba commented on GitHub (Aug 3, 2023):

Here you go, these are the logs from the client that is having the issues mentioned. As far as I have seen, the other machines (clients that work properly and the management server, don't have these logs).

Checking timestamps, the line that aligns perfectly with the moment in which the issues have started is this one:
2023-08-03T10:50:03Z ERRO client/internal/wgproxy/factory_linux.go:15: failed to initialize ebpf proxy: failed to set memlock rlimit: operation not permitted

netbird_error_logs

@gmatasba commented on GitHub (Aug 3, 2023): Here you go, these are the logs from the client that is having the issues mentioned. As far as I have seen, the other machines (clients that work properly and the management server, don't have these logs). Checking timestamps, the line that aligns perfectly with the moment in which the issues have started is this one: `2023-08-03T10:50:03Z ERRO client/internal/wgproxy/factory_linux.go:15: failed to initialize ebpf proxy: failed to set memlock rlimit: operation not permitted` ![netbird_error_logs](https://github.com/netbirdio/netbird/assets/31928542/c0885930-ecef-40e4-8c1f-4c6eef3d2d4c)
Author
Owner

@mlsmaycon commented on GitHub (Aug 4, 2023):

@gmatasba @Sxndxr the issue was fixed in v0.22.2, can you test on your end?

@mlsmaycon commented on GitHub (Aug 4, 2023): @gmatasba @Sxndxr the issue was fixed in v0.22.2, can you test on your end?
Author
Owner

@reimarstier commented on GitHub (Aug 14, 2023):

I had a similar issue with netbird client v0.21.8:

netbird up --management-url <YOUR_MANAGEMENT_URL> --setup-key <YOUR_SETUP_KEY>
logs
2023-08-14T16:01:13+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 936.119771ms due to error rpc error: code = DeadlineExceeded desc = context deadline exceeded 2023-08-14T16:01:24+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 2.102444321s due to error rpc error: code = DeadlineExceeded desc = context deadline exceeded Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded

Updating the client to v0.22.4 fixed it for me. Yay.

@reimarstier commented on GitHub (Aug 14, 2023): I had a similar issue with netbird client v0.21.8: `netbird up --management-url <YOUR_MANAGEMENT_URL> --setup-key <YOUR_SETUP_KEY>` logs `2023-08-14T16:01:13+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 936.119771ms due to error rpc error: code = DeadlineExceeded desc = context deadline exceeded 2023-08-14T16:01:24+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 2.102444321s due to error rpc error: code = DeadlineExceeded desc = context deadline exceeded Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded ` Updating the client to v0.22.4 fixed it for me. Yay.
Author
Owner

@kdre commented on GitHub (Aug 18, 2023):

I have exactly the same Problem on one (I have several) Manjaro Linux computer with the latest netbird Client from AUR (not docker).

Tried to remove the package and reinstalled it, but had no luck so far.

Any idea what causes this problem?

@kdre commented on GitHub (Aug 18, 2023): I have exactly the same Problem on one (I have several) Manjaro Linux computer with the latest netbird Client from AUR (not docker). Tried to remove the package and reinstalled it, but had no luck so far. Any idea what causes this problem?
Author
Owner

@gmatasba commented on GitHub (Aug 21, 2023):

@mlsmaycon I personally solved the issue by creating a very small separate machine in order to use it as a routing peer and no longer have the set-up I described earlier. I will try to replicate it, test with the new version and then share the results here.

@gmatasba commented on GitHub (Aug 21, 2023): @mlsmaycon I personally solved the issue by creating a very small separate machine in order to use it as a routing peer and no longer have the set-up I described earlier. I will try to replicate it, test with the new version and then share the results here.
Author
Owner

@kdre commented on GitHub (Aug 22, 2023):

Since today a second machine fails to connect. When I execute "netbird up", I get:

2023-08-22T14:52:40+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 502.410121ms due to error rpc error: code = Unknown desc = getting pkce authorization flow info failed with error: context deadline exceeded
Error: login backoff cycle failed: rpc error: code = Unknown desc = getting pkce authorization flow info failed with error: context deadline exceeded

Daemon version: 0.22.6
CLI version: 0.22.6

What is going on?

@kdre commented on GitHub (Aug 22, 2023): Since today a second machine fails to connect. When I execute "netbird up", I get: 2023-08-22T14:52:40+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 502.410121ms due to error rpc error: code = Unknown desc = getting pkce authorization flow info failed with error: context deadline exceeded Error: login backoff cycle failed: rpc error: code = Unknown desc = getting pkce authorization flow info failed with error: context deadline exceeded Daemon version: 0.22.6 CLI version: 0.22.6 What is going on?
Author
Owner

@Trevinlc1997 commented on GitHub (Aug 29, 2023):

Getting the same error on v0.22.7 with Debian 12 LXC. Interesting enough I was able to get it connected but after restarting the container that's when the errors started popping up and even started locking up the LXC container every 20 secs and dropping my SSH connection.

@Trevinlc1997 commented on GitHub (Aug 29, 2023): Getting the same error on v0.22.7 with Debian 12 LXC. Interesting enough I was able to get it connected but after restarting the container that's when the errors started popping up and even started locking up the LXC container every 20 secs and dropping my SSH connection.
Author
Owner

@Sxndxr commented on GitHub (Aug 29, 2023):

I think you have to update Netbird. I guess that the bug has been fixed in
the new version.

Le mer. 30 août 2023 à 05:03, Trevin Corkery @.***> a
écrit :

Getting the same error on v0.22.7 with Debian 12 LXC. Interesting enough I
was able to get it connected but after restarting the container that's when
the errors started popping up and even started locking up the LXC container
every 20 secs and dropping my SSH connection.


Reply to this email directly, view it on GitHub
https://github.com/netbirdio/netbird/issues/1048#issuecomment-1698418127,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUQXX7WG3S23PMVNL6LVCNTXX2URVANCNFSM6AAAAAA3CPJA34
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Sxndxr commented on GitHub (Aug 29, 2023): I think you have to update Netbird. I guess that the bug has been fixed in the new version. Le mer. 30 août 2023 à 05:03, Trevin Corkery ***@***.***> a écrit : > Getting the same error on v0.22.7 with Debian 12 LXC. Interesting enough I > was able to get it connected but after restarting the container that's when > the errors started popping up and even started locking up the LXC container > every 20 secs and dropping my SSH connection. > > — > Reply to this email directly, view it on GitHub > <https://github.com/netbirdio/netbird/issues/1048#issuecomment-1698418127>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AUQXX7WG3S23PMVNL6LVCNTXX2URVANCNFSM6AAAAAA3CPJA34> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@holotrack commented on GitHub (Aug 31, 2023):

Same here with newest version:

image

Exactly same when --management-url provided

@holotrack commented on GitHub (Aug 31, 2023): Same here with newest version: ![image](https://github.com/netbirdio/netbird/assets/100580892/c88c42b4-2de9-452c-8f60-dc45fa6992f7) Exactly same when --management-url provided
Author
Owner

@kdre commented on GitHub (Sep 1, 2023):

I still have the problem on two machines and the latest versions (0.22.7).

@kdre commented on GitHub (Sep 1, 2023): I still have the problem on two machines and the latest versions (0.22.7).
Author
Owner

@mlsmaycon commented on GitHub (Sep 5, 2023):

The issue might be a problem with gRPC connectivity. Could you run the agent in the foreground with the following steps and share the output?

First, you need to stop the current agent:

sudo netbird service stop

Then run:

sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F -l debug'
@mlsmaycon commented on GitHub (Sep 5, 2023): The issue might be a problem with gRPC connectivity. Could you run the agent in the foreground with the following steps and share the output? First, you need to stop the current agent: ``` sudo netbird service stop ``` Then run: ``` sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F -l debug' ```
Author
Owner

@equalis3r commented on GitHub (Sep 7, 2023):

@mlsmaycon Here is the log that I get. I just try to install and run netbird on my 2 machines. The desktop runs normally while the laptop encounters this issue. Both have the same network configurations.

// Edit: My bad. Turn out on my laptop, I didn't link stub-resolv.conf to /etc/resolv.conf. It's now working normally.

log.txt

@equalis3r commented on GitHub (Sep 7, 2023): @mlsmaycon Here is the log that I get. I just try to install and run netbird on my 2 machines. The desktop runs normally while the laptop encounters this issue. Both have the same network configurations. // Edit: My bad. Turn out on my laptop, I didn't link stub-resolv.conf to /etc/resolv.conf. It's now working normally. [log.txt](https://github.com/netbirdio/netbird/files/12552457/log.txt)
Author
Owner

@kdre commented on GitHub (Sep 19, 2023):

I still have this issue with the latest releases.

sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F -l debug'

2023-09-19T09:17:12+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://api.wiretrustee.com:443
2023/09/19 09:17:12 INFO: [core] [Channel #1] Channel created
2023/09/19 09:17:12 INFO: [core] [Channel #1] original dial target is: "api.wiretrustee.com:443"
2023/09/19 09:17:12 INFO: [core] [Channel #1] parsed dial target is: {Scheme:api.wiretrustee.com Authority: URL:{Scheme:api.wiretrustee.com Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/19 09:17:12 INFO: [core] [Channel #1] fallback to scheme "passthrough"
2023/09/19 09:17:12 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.wiretrustee.com:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/19 09:17:12 INFO: [core] [Channel #1] Channel authority set to "api.wiretrustee.com:443"
2023/09/19 09:17:12 INFO: [core] [Channel #1] Resolver state updated: {
"Addresses": [
{
"Addr": "api.wiretrustee.com:443",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
2023/09/19 09:17:12 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first"
2023/09/19 09:17:12 INFO: [core] [Channel #1 SubChannel #2] Subchannel created
2023/09/19 09:17:12 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING
2023/09/19 09:17:12 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING
2023/09/19 09:17:12 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.wiretrustee.com:443" to connect
2023/09/19 09:17:12 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0006da0a8, {CONNECTING }
2023/09/19 09:17:17 INFO: [core] [Channel #1] Channel Connectivity change to SHUTDOWN
2023/09/19 09:17:17 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to SHUTDOWN
2023/09/19 09:17:17 INFO: [core] [Channel #1 SubChannel #2] Subchannel deleted
2023/09/19 09:17:17 INFO: [core] [Channel #1] Channel deleted
2023-09-19T09:17:17+02:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-09-19T09:17:17+02:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://api.wiretrustee.com:443 context deadline exceeded
2023/09/19 09:17:17 INFO: [core] Creating new client transport to "{\n "Addr": "api.wiretrustee.com:443",\n "ServerName": "api.wiretrustee.com:443",\n "Attributes": null,\n "BalancerAttributes": null,\n "Type": 0,\n "Metadata": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com: operation was canceled"
2023-09-19T09:17:17+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.43203904s due to error context deadline exceeded
2023/09/19 09:17:17 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {
"Addr": "api.wiretrustee.com:443",
"ServerName": "api.wiretrustee.com:443",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com: operation was canceled"
2023-09-19T09:17:18+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://api.wiretrustee.com:443
2023/09/19 09:17:18 INFO: [core] [Channel #3] Channel created
2023/09/19 09:17:18 INFO: [core] [Channel #3] original dial target is: "api.wiretrustee.com:443"
2023/09/19 09:17:18 INFO: [core] [Channel #3] parsed dial target is: {Scheme:api.wiretrustee.com Authority: URL:{Scheme:api.wiretrustee.com Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/19 09:17:18 INFO: [core] [Channel #3] fallback to scheme "passthrough"
2023/09/19 09:17:18 INFO: [core] [Channel #3] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.wiretrustee.com:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/19 09:17:18 INFO: [core] [Channel #3] Channel authority set to "api.wiretrustee.com:443"
2023/09/19 09:17:18 INFO: [core] [Channel #3] Resolver state updated: {
"Addresses": [
{
"Addr": "api.wiretrustee.com:443",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
2023/09/19 09:17:18 INFO: [core] [Channel #3] Channel switches to new LB policy "pick_first"
2023/09/19 09:17:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel created
2023/09/19 09:17:18 INFO: [core] [Channel #3] Channel Connectivity change to CONNECTING
2023/09/19 09:17:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING
2023/09/19 09:17:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.wiretrustee.com:443" to connect
2023/09/19 09:17:18 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0006da030, {CONNECTING }
2023/09/19 09:17:23 INFO: [core] [Channel #3] Channel Connectivity change to SHUTDOWN
2023/09/19 09:17:23 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to SHUTDOWN
2023/09/19 09:17:23 INFO: [core] [Channel #3 SubChannel #4] Subchannel deleted
2023/09/19 09:17:23 INFO: [core] [Channel #3] Channel deleted
2023-09-19T09:17:23+02:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-09-19T09:17:23+02:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://api.wiretrustee.com:443 context deadline exceeded
2023-09-19T09:17:23+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.54748959s due to error context deadline exceeded
2023/09/19 09:17:23 INFO: [core] Creating new client transport to "{\n "Addr": "api.wiretrustee.com:443",\n "ServerName": "api.wiretrustee.com:443",\n "Attributes": null,\n "BalancerAttributes": null,\n "Type": 0,\n "Metadata": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com: operation was canceled"
2023/09/19 09:17:23 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {
"Addr": "api.wiretrustee.com:443",
"ServerName": "api.wiretrustee.com:443",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com: operation was canceled"
2023-09-19T09:17:25+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://api.wiretrustee.com:443
2023/09/19 09:17:25 INFO: [core] [Channel #5] Channel created
2023/09/19 09:17:25 INFO: [core] [Channel #5] original dial target is: "api.wiretrustee.com:443"
2023/09/19 09:17:25 INFO: [core] [Channel #5] parsed dial target is: {Scheme:api.wiretrustee.com Authority: URL:{Scheme:api.wiretrustee.com Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/19 09:17:25 INFO: [core] [Channel #5] fallback to scheme "passthrough"
2023/09/19 09:17:25 INFO: [core] [Channel #5] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.wiretrustee.com:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/19 09:17:25 INFO: [core] [Channel #5] Channel authority set to "api.wiretrustee.com:443"
2023/09/19 09:17:25 INFO: [core] [Channel #5] Resolver state updated: {
"Addresses": [
{
"Addr": "api.wiretrustee.com:443",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
...

Any ideas?

@kdre commented on GitHub (Sep 19, 2023): I still have this issue with the latest releases. sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F -l debug' 2023-09-19T09:17:12+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://api.wiretrustee.com:443 2023/09/19 09:17:12 INFO: [core] [Channel #1] Channel created 2023/09/19 09:17:12 INFO: [core] [Channel #1] original dial target is: "api.wiretrustee.com:443" 2023/09/19 09:17:12 INFO: [core] [Channel #1] parsed dial target is: {Scheme:api.wiretrustee.com Authority: URL:{Scheme:api.wiretrustee.com Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/19 09:17:12 INFO: [core] [Channel #1] fallback to scheme "passthrough" 2023/09/19 09:17:12 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.wiretrustee.com:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/19 09:17:12 INFO: [core] [Channel #1] Channel authority set to "api.wiretrustee.com:443" 2023/09/19 09:17:12 INFO: [core] [Channel #1] Resolver state updated: { "Addresses": [ { "Addr": "api.wiretrustee.com:443", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2023/09/19 09:17:12 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first" 2023/09/19 09:17:12 INFO: [core] [Channel #1 SubChannel #2] Subchannel created 2023/09/19 09:17:12 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING 2023/09/19 09:17:12 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2023/09/19 09:17:12 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.wiretrustee.com:443" to connect 2023/09/19 09:17:12 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0006da0a8, {CONNECTING <nil>} 2023/09/19 09:17:17 INFO: [core] [Channel #1] Channel Connectivity change to SHUTDOWN 2023/09/19 09:17:17 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to SHUTDOWN 2023/09/19 09:17:17 INFO: [core] [Channel #1 SubChannel #2] Subchannel deleted 2023/09/19 09:17:17 INFO: [core] [Channel #1] Channel deleted 2023-09-19T09:17:17+02:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-09-19T09:17:17+02:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://api.wiretrustee.com:443 context deadline exceeded 2023/09/19 09:17:17 INFO: [core] Creating new client transport to "{\n \"Addr\": \"api.wiretrustee.com:443\",\n \"ServerName\": \"api.wiretrustee.com:443\",\n \"Attributes\": null,\n \"BalancerAttributes\": null,\n \"Type\": 0,\n \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com: operation was canceled" 2023-09-19T09:17:17+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.43203904s due to error context deadline exceeded 2023/09/19 09:17:17 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to { "Addr": "api.wiretrustee.com:443", "ServerName": "api.wiretrustee.com:443", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com: operation was canceled" 2023-09-19T09:17:18+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://api.wiretrustee.com:443 2023/09/19 09:17:18 INFO: [core] [Channel #3] Channel created 2023/09/19 09:17:18 INFO: [core] [Channel #3] original dial target is: "api.wiretrustee.com:443" 2023/09/19 09:17:18 INFO: [core] [Channel #3] parsed dial target is: {Scheme:api.wiretrustee.com Authority: URL:{Scheme:api.wiretrustee.com Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/19 09:17:18 INFO: [core] [Channel #3] fallback to scheme "passthrough" 2023/09/19 09:17:18 INFO: [core] [Channel #3] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.wiretrustee.com:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/19 09:17:18 INFO: [core] [Channel #3] Channel authority set to "api.wiretrustee.com:443" 2023/09/19 09:17:18 INFO: [core] [Channel #3] Resolver state updated: { "Addresses": [ { "Addr": "api.wiretrustee.com:443", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2023/09/19 09:17:18 INFO: [core] [Channel #3] Channel switches to new LB policy "pick_first" 2023/09/19 09:17:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel created 2023/09/19 09:17:18 INFO: [core] [Channel #3] Channel Connectivity change to CONNECTING 2023/09/19 09:17:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2023/09/19 09:17:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.wiretrustee.com:443" to connect 2023/09/19 09:17:18 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0006da030, {CONNECTING <nil>} 2023/09/19 09:17:23 INFO: [core] [Channel #3] Channel Connectivity change to SHUTDOWN 2023/09/19 09:17:23 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to SHUTDOWN 2023/09/19 09:17:23 INFO: [core] [Channel #3 SubChannel #4] Subchannel deleted 2023/09/19 09:17:23 INFO: [core] [Channel #3] Channel deleted 2023-09-19T09:17:23+02:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-09-19T09:17:23+02:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://api.wiretrustee.com:443 context deadline exceeded 2023-09-19T09:17:23+02:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.54748959s due to error context deadline exceeded 2023/09/19 09:17:23 INFO: [core] Creating new client transport to "{\n \"Addr\": \"api.wiretrustee.com:443\",\n \"ServerName\": \"api.wiretrustee.com:443\",\n \"Attributes\": null,\n \"BalancerAttributes\": null,\n \"Type\": 0,\n \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com: operation was canceled" 2023/09/19 09:17:23 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to { "Addr": "api.wiretrustee.com:443", "ServerName": "api.wiretrustee.com:443", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com: operation was canceled" 2023-09-19T09:17:25+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://api.wiretrustee.com:443 2023/09/19 09:17:25 INFO: [core] [Channel #5] Channel created 2023/09/19 09:17:25 INFO: [core] [Channel #5] original dial target is: "api.wiretrustee.com:443" 2023/09/19 09:17:25 INFO: [core] [Channel #5] parsed dial target is: {Scheme:api.wiretrustee.com Authority: URL:{Scheme:api.wiretrustee.com Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/19 09:17:25 INFO: [core] [Channel #5] fallback to scheme "passthrough" 2023/09/19 09:17:25 INFO: [core] [Channel #5] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.wiretrustee.com:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/19 09:17:25 INFO: [core] [Channel #5] Channel authority set to "api.wiretrustee.com:443" 2023/09/19 09:17:25 INFO: [core] [Channel #5] Resolver state updated: { "Addresses": [ { "Addr": "api.wiretrustee.com:443", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) ... Any ideas?
Author
Owner

@devopskupryk commented on GitHub (Sep 22, 2023):

I updated netbird client from 0.22.7 to 0.23.2 on my CentOS 7.9 host and have got the same issue:

2023-09-22T18:43:01+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-09-22T18:43:02+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded
2023-09-22T18:43:02+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded

At the same time there isn't this issue on fedora 37 with 0.23.2

UPDATE: reinstall netbird client 0.22.7 which worked well before and have got the same issue
DEBUG:

sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F -l debug'
2023-09-25T10:46:57+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073
2023/09/25 10:46:57 INFO: [core] [Channel #1] Channel created
2023/09/25 10:46:57 INFO: [core] [Channel #1] original dial target is: "netbird.hidden.tech:33073"
2023/09/25 10:46:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:46:57 INFO: [core] [Channel #1] fallback to scheme "passthrough"
2023/09/25 10:46:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:46:57 INFO: [core] [Channel #1] Channel authority set to "netbird.hidden.tech:33073"
2023/09/25 10:46:57 INFO: [core] [Channel #1] Resolver state updated: {
  "Addresses": [
    {
      "Addr": "netbird.hidden.tech:33073",
      "ServerName": "",
      "Attributes": null,
      "BalancerAttributes": null,
      "Type": 0,
      "Metadata": null
    }
  ],
  "ServiceConfig": null,
  "Attributes": null
} (resolver returned new addresses)
2023/09/25 10:46:57 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first"
2023/09/25 10:46:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel created
2023/09/25 10:46:57 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING
2023/09/25 10:46:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING
2023/09/25 10:46:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "netbird.hidden.tech:33073" to connect
2023/09/25 10:46:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000010ba0, {CONNECTING <nil>}
2023/09/25 10:47:02 INFO: [core] [Channel #1] Channel Connectivity change to SHUTDOWN
2023/09/25 10:47:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to SHUTDOWN
2023/09/25 10:47:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel deleted
2023/09/25 10:47:02 INFO: [core] [Channel #1] Channel deleted
2023-09-25T10:47:02+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-09-25T10:47:02+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded
2023/09/25 10:47:02 INFO: [core] Creating new client transport to "{\n  \"Addr\": \"netbird.hidden.tech:33073\",\n  \"ServerName\": \"netbird.hidden.tech:33073\",\n  \"Attributes\": null,\n  \"BalancerAttributes\": null,\n  \"Type\": 0,\n  \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled"
2023/09/25 10:47:02 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {
  "Addr": "netbird.hidden.tech:33073",
  "ServerName": "netbird.hidden.tech:33073",
  "Attributes": null,
  "BalancerAttributes": null,
  "Type": 0,
  "Metadata": null
}. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled"
2023-09-25T10:47:02+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 781.98239ms due to error context deadline exceeded
2023-09-25T10:47:03+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073
2023/09/25 10:47:03 INFO: [core] [Channel #3] Channel created
2023/09/25 10:47:03 INFO: [core] [Channel #3] original dial target is: "netbird.hidden.tech:33073"
2023/09/25 10:47:03 INFO: [core] [Channel #3] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:47:03 INFO: [core] [Channel #3] fallback to scheme "passthrough"
2023/09/25 10:47:03 INFO: [core] [Channel #3] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:47:03 INFO: [core] [Channel #3] Channel authority set to "netbird.hidden.tech:33073"
2023/09/25 10:47:03 INFO: [core] [Channel #3] Resolver state updated: {
  "Addresses": [
    {
      "Addr": "netbird.hidden.tech:33073",
      "ServerName": "",
      "Attributes": null,
      "BalancerAttributes": null,
      "Type": 0,
      "Metadata": null
    }
  ],
  "ServiceConfig": null,
  "Attributes": null
} (resolver returned new addresses)
2023/09/25 10:47:03 INFO: [core] [Channel #3] Channel switches to new LB policy "pick_first"
2023/09/25 10:47:03 INFO: [core] [Channel #3 SubChannel #4] Subchannel created
2023/09/25 10:47:03 INFO: [core] [Channel #3] Channel Connectivity change to CONNECTING
2023/09/25 10:47:03 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING
2023/09/25 10:47:03 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "netbird.hidden.tech:33073" to connect
2023/09/25 10:47:03 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0001aa078, {CONNECTING <nil>}
2023/09/25 10:47:08 INFO: [core] [Channel #3] Channel Connectivity change to SHUTDOWN
2023/09/25 10:47:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to SHUTDOWN
2023/09/25 10:47:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel deleted
2023/09/25 10:47:08 INFO: [core] [Channel #3] Channel deleted
2023-09-25T10:47:08+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-09-25T10:47:08+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded
2023/09/25 10:47:08 INFO: [core] Creating new client transport to "{\n  \"Addr\": \"netbird.hidden.tech:33073\",\n  \"ServerName\": \"netbird.hidden.tech:33073\",\n  \"Attributes\": null,\n  \"BalancerAttributes\": null,\n  \"Type\": 0,\n  \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled"
2023-09-25T10:47:08+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.993228132s due to error context deadline exceeded
2023/09/25 10:47:08 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {
  "Addr": "netbird.hidden.tech:33073",
  "ServerName": "netbird.hidden.tech:33073",
  "Attributes": null,
  "BalancerAttributes": null,
  "Type": 0,
  "Metadata": null
}. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled"
2023-09-25T10:47:10+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073
2023/09/25 10:47:10 INFO: [core] [Channel #5] Channel created
2023/09/25 10:47:10 INFO: [core] [Channel #5] original dial target is: "netbird.hidden.tech:33073"
2023/09/25 10:47:10 INFO: [core] [Channel #5] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:47:10 INFO: [core] [Channel #5] fallback to scheme "passthrough"
2023/09/25 10:47:10 INFO: [core] [Channel #5] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:47:10 INFO: [core] [Channel #5] Channel authority set to "netbird.hidden.tech:33073"
2023/09/25 10:47:10 INFO: [core] [Channel #5] Resolver state updated: {
  "Addresses": [
    {
      "Addr": "netbird.hidden.tech:33073",
      "ServerName": "",
      "Attributes": null,
      "BalancerAttributes": null,
      "Type": 0,
      "Metadata": null
    }
  ],
  "ServiceConfig": null,
  "Attributes": null
} (resolver returned new addresses)
2023/09/25 10:47:10 INFO: [core] [Channel #5] Channel switches to new LB policy "pick_first"
2023/09/25 10:47:10 INFO: [core] [Channel #5 SubChannel #6] Subchannel created
2023/09/25 10:47:10 INFO: [core] [Channel #5] Channel Connectivity change to CONNECTING
2023/09/25 10:47:10 INFO: [core] [Channel #5 SubChannel #6] Subchannel Connectivity change to CONNECTING
2023/09/25 10:47:10 INFO: [core] [Channel #5 SubChannel #6] Subchannel picks a new address "netbird.hidden.tech:33073" to connect
2023/09/25 10:47:10 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0001aa408, {CONNECTING <nil>}
2023/09/25 10:47:15 INFO: [core] [Channel #5] Channel Connectivity change to SHUTDOWN
2023/09/25 10:47:15 INFO: [core] [Channel #5 SubChannel #6] Subchannel Connectivity change to SHUTDOWN
2023/09/25 10:47:15 INFO: [core] [Channel #5 SubChannel #6] Subchannel deleted
2023/09/25 10:47:15 INFO: [core] [Channel #5] Channel deleted
2023-09-25T10:47:15+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-09-25T10:47:15+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded
2023/09/25 10:47:15 INFO: [core] Creating new client transport to "{\n  \"Addr\": \"netbird.hidden.tech:33073\",\n  \"ServerName\": \"netbird.hidden.tech:33073\",\n  \"Attributes\": null,\n  \"BalancerAttributes\": null,\n  \"Type\": 0,\n  \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled"
2023/09/25 10:47:15 WARNING: [core] [Channel #5 SubChannel #6] grpc: addrConn.createTransport failed to connect to {
  "Addr": "netbird.hidden.tech:33073",
  "ServerName": "netbird.hidden.tech:33073",
  "Attributes": null,
  "BalancerAttributes": null,
  "Type": 0,
  "Metadata": null
}. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled"
2023-09-25T10:47:15+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 2.225361164s due to error context deadline exceeded
2023-09-25T10:47:17+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073
2023/09/25 10:47:17 INFO: [core] [Channel #7] Channel created
2023/09/25 10:47:17 INFO: [core] [Channel #7] original dial target is: "netbird.hidden.tech:33073"
2023/09/25 10:47:17 INFO: [core] [Channel #7] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:47:17 INFO: [core] [Channel #7] fallback to scheme "passthrough"
2023/09/25 10:47:17 INFO: [core] [Channel #7] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:47:17 INFO: [core] [Channel #7] Channel authority set to "netbird.hidden.tech:33073"
2023/09/25 10:47:17 INFO: [core] [Channel #7] Resolver state updated: {
  "Addresses": [
    {
      "Addr": "netbird.hidden.tech:33073",
      "ServerName": "",
      "Attributes": null,
      "BalancerAttributes": null,
      "Type": 0,
      "Metadata": null
    }
  ],
  "ServiceConfig": null,
  "Attributes": null
} (resolver returned new addresses)
2023/09/25 10:47:17 INFO: [core] [Channel #7] Channel switches to new LB policy "pick_first"
2023/09/25 10:47:17 INFO: [core] [Channel #7 SubChannel #8] Subchannel created
2023/09/25 10:47:17 INFO: [core] [Channel #7] Channel Connectivity change to CONNECTING
2023/09/25 10:47:17 INFO: [core] [Channel #7 SubChannel #8] Subchannel Connectivity change to CONNECTING
2023/09/25 10:47:17 INFO: [core] [Channel #7 SubChannel #8] Subchannel picks a new address "netbird.hidden.tech:33073" to connect
2023/09/25 10:47:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0006660a8, {CONNECTING <nil>}
2023/09/25 10:47:22 INFO: [core] [Channel #7] Channel Connectivity change to SHUTDOWN
2023/09/25 10:47:22 INFO: [core] [Channel #7 SubChannel #8] Subchannel Connectivity change to SHUTDOWN
2023/09/25 10:47:22 INFO: [core] [Channel #7 SubChannel #8] Subchannel deleted
2023/09/25 10:47:22 INFO: [core] [Channel #7] Channel deleted
2023-09-25T10:47:22+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-09-25T10:47:22+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded
2023-09-25T10:47:22+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.731637762s due to error context deadline exceeded
2023/09/25 10:47:22 INFO: [core] Creating new client transport to "{\n  \"Addr\": \"netbird.hidden.tech:33073\",\n  \"ServerName\": \"netbird.hidden.tech:33073\",\n  \"Attributes\": null,\n  \"BalancerAttributes\": null,\n  \"Type\": 0,\n  \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled"
2023/09/25 10:47:22 WARNING: [core] [Channel #7 SubChannel #8] grpc: addrConn.createTransport failed to connect to {
  "Addr": "netbird.hidden.tech:33073",
  "ServerName": "netbird.hidden.tech:33073",
  "Attributes": null,
  "BalancerAttributes": null,
  "Type": 0,
  "Metadata": null
}. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled"
2023-09-25T10:47:24+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073
2023/09/25 10:47:24 INFO: [core] [Channel #9] Channel created
2023/09/25 10:47:24 INFO: [core] [Channel #9] original dial target is: "netbird.hidden.tech:33073"
2023/09/25 10:47:24 INFO: [core] [Channel #9] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:47:24 INFO: [core] [Channel #9] fallback to scheme "passthrough"
2023/09/25 10:47:24 INFO: [core] [Channel #9] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/09/25 10:47:24 INFO: [core] [Channel #9] Channel authority set to "netbird.hidden.tech:33073"
2023/09/25 10:47:24 INFO: [core] [Channel #9] Resolver state updated: {
  "Addresses": [
    {
      "Addr": "netbird.hidden.tech:33073",
      "ServerName": "",
      "Attributes": null,
      "BalancerAttributes": null,
      "Type": 0,
      "Metadata": null
    }
  ],
  "ServiceConfig": null,
  "Attributes": null
} (resolver returned new addresses)
2023/09/25 10:47:24 INFO: [core] [Channel #9] Channel switches to new LB policy "pick_first"
2023/09/25 10:47:24 INFO: [core] [Channel #9 SubChannel #10] Subchannel created
2023/09/25 10:47:24 INFO: [core] [Channel #9] Channel Connectivity change to CONNECTING
2023/09/25 10:47:24 INFO: [core] [Channel #9 SubChannel #10] Subchannel Connectivity change to CONNECTING
2023/09/25 10:47:24 INFO: [core] [Channel #9 SubChannel #10] Subchannel picks a new address "netbird.hidden.tech:33073" to connect
2023/09/25 10:47:24 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0006f8090, {CONNECTING <nil>}
2023/09/25 10:47:29 INFO: [core] [Channel #9] Channel Connectivity change to SHUTDOWN
2023/09/25 10:47:29 INFO: [core] [Channel #9 SubChannel #10] Subchannel Connectivity change to SHUTDOWN
2023/09/25 10:47:29 INFO: [core] [Channel #9 SubChannel #10] Subchannel deleted
2023/09/25 10:47:29 INFO: [core] [Channel #9] Channel deleted
2023-09-25T10:47:29+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-09-25T10:47:29+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded
Error: foreground login failed: backoff cycle failed: context deadline exceeded

@devopskupryk commented on GitHub (Sep 22, 2023): I updated netbird client from 0.22.7 to 0.23.2 on my CentOS 7.9 host and have got the same issue: ``` 2023-09-22T18:43:01+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-09-22T18:43:02+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded 2023-09-22T18:43:02+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded ``` At the same time there isn't this issue on fedora 37 with 0.23.2 UPDATE: reinstall netbird client 0.22.7 which worked well before and have got the same issue DEBUG: ``` sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F -l debug' 2023-09-25T10:46:57+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073 2023/09/25 10:46:57 INFO: [core] [Channel #1] Channel created 2023/09/25 10:46:57 INFO: [core] [Channel #1] original dial target is: "netbird.hidden.tech:33073" 2023/09/25 10:46:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:46:57 INFO: [core] [Channel #1] fallback to scheme "passthrough" 2023/09/25 10:46:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:46:57 INFO: [core] [Channel #1] Channel authority set to "netbird.hidden.tech:33073" 2023/09/25 10:46:57 INFO: [core] [Channel #1] Resolver state updated: { "Addresses": [ { "Addr": "netbird.hidden.tech:33073", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2023/09/25 10:46:57 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first" 2023/09/25 10:46:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel created 2023/09/25 10:46:57 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING 2023/09/25 10:46:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2023/09/25 10:46:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "netbird.hidden.tech:33073" to connect 2023/09/25 10:46:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000010ba0, {CONNECTING <nil>} 2023/09/25 10:47:02 INFO: [core] [Channel #1] Channel Connectivity change to SHUTDOWN 2023/09/25 10:47:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to SHUTDOWN 2023/09/25 10:47:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel deleted 2023/09/25 10:47:02 INFO: [core] [Channel #1] Channel deleted 2023-09-25T10:47:02+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-09-25T10:47:02+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded 2023/09/25 10:47:02 INFO: [core] Creating new client transport to "{\n \"Addr\": \"netbird.hidden.tech:33073\",\n \"ServerName\": \"netbird.hidden.tech:33073\",\n \"Attributes\": null,\n \"BalancerAttributes\": null,\n \"Type\": 0,\n \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled" 2023/09/25 10:47:02 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to { "Addr": "netbird.hidden.tech:33073", "ServerName": "netbird.hidden.tech:33073", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled" 2023-09-25T10:47:02+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 781.98239ms due to error context deadline exceeded 2023-09-25T10:47:03+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073 2023/09/25 10:47:03 INFO: [core] [Channel #3] Channel created 2023/09/25 10:47:03 INFO: [core] [Channel #3] original dial target is: "netbird.hidden.tech:33073" 2023/09/25 10:47:03 INFO: [core] [Channel #3] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:47:03 INFO: [core] [Channel #3] fallback to scheme "passthrough" 2023/09/25 10:47:03 INFO: [core] [Channel #3] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:47:03 INFO: [core] [Channel #3] Channel authority set to "netbird.hidden.tech:33073" 2023/09/25 10:47:03 INFO: [core] [Channel #3] Resolver state updated: { "Addresses": [ { "Addr": "netbird.hidden.tech:33073", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2023/09/25 10:47:03 INFO: [core] [Channel #3] Channel switches to new LB policy "pick_first" 2023/09/25 10:47:03 INFO: [core] [Channel #3 SubChannel #4] Subchannel created 2023/09/25 10:47:03 INFO: [core] [Channel #3] Channel Connectivity change to CONNECTING 2023/09/25 10:47:03 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2023/09/25 10:47:03 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "netbird.hidden.tech:33073" to connect 2023/09/25 10:47:03 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0001aa078, {CONNECTING <nil>} 2023/09/25 10:47:08 INFO: [core] [Channel #3] Channel Connectivity change to SHUTDOWN 2023/09/25 10:47:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to SHUTDOWN 2023/09/25 10:47:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel deleted 2023/09/25 10:47:08 INFO: [core] [Channel #3] Channel deleted 2023-09-25T10:47:08+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-09-25T10:47:08+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded 2023/09/25 10:47:08 INFO: [core] Creating new client transport to "{\n \"Addr\": \"netbird.hidden.tech:33073\",\n \"ServerName\": \"netbird.hidden.tech:33073\",\n \"Attributes\": null,\n \"BalancerAttributes\": null,\n \"Type\": 0,\n \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled" 2023-09-25T10:47:08+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.993228132s due to error context deadline exceeded 2023/09/25 10:47:08 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to { "Addr": "netbird.hidden.tech:33073", "ServerName": "netbird.hidden.tech:33073", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled" 2023-09-25T10:47:10+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073 2023/09/25 10:47:10 INFO: [core] [Channel #5] Channel created 2023/09/25 10:47:10 INFO: [core] [Channel #5] original dial target is: "netbird.hidden.tech:33073" 2023/09/25 10:47:10 INFO: [core] [Channel #5] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:47:10 INFO: [core] [Channel #5] fallback to scheme "passthrough" 2023/09/25 10:47:10 INFO: [core] [Channel #5] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:47:10 INFO: [core] [Channel #5] Channel authority set to "netbird.hidden.tech:33073" 2023/09/25 10:47:10 INFO: [core] [Channel #5] Resolver state updated: { "Addresses": [ { "Addr": "netbird.hidden.tech:33073", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2023/09/25 10:47:10 INFO: [core] [Channel #5] Channel switches to new LB policy "pick_first" 2023/09/25 10:47:10 INFO: [core] [Channel #5 SubChannel #6] Subchannel created 2023/09/25 10:47:10 INFO: [core] [Channel #5] Channel Connectivity change to CONNECTING 2023/09/25 10:47:10 INFO: [core] [Channel #5 SubChannel #6] Subchannel Connectivity change to CONNECTING 2023/09/25 10:47:10 INFO: [core] [Channel #5 SubChannel #6] Subchannel picks a new address "netbird.hidden.tech:33073" to connect 2023/09/25 10:47:10 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0001aa408, {CONNECTING <nil>} 2023/09/25 10:47:15 INFO: [core] [Channel #5] Channel Connectivity change to SHUTDOWN 2023/09/25 10:47:15 INFO: [core] [Channel #5 SubChannel #6] Subchannel Connectivity change to SHUTDOWN 2023/09/25 10:47:15 INFO: [core] [Channel #5 SubChannel #6] Subchannel deleted 2023/09/25 10:47:15 INFO: [core] [Channel #5] Channel deleted 2023-09-25T10:47:15+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-09-25T10:47:15+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded 2023/09/25 10:47:15 INFO: [core] Creating new client transport to "{\n \"Addr\": \"netbird.hidden.tech:33073\",\n \"ServerName\": \"netbird.hidden.tech:33073\",\n \"Attributes\": null,\n \"BalancerAttributes\": null,\n \"Type\": 0,\n \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled" 2023/09/25 10:47:15 WARNING: [core] [Channel #5 SubChannel #6] grpc: addrConn.createTransport failed to connect to { "Addr": "netbird.hidden.tech:33073", "ServerName": "netbird.hidden.tech:33073", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled" 2023-09-25T10:47:15+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 2.225361164s due to error context deadline exceeded 2023-09-25T10:47:17+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073 2023/09/25 10:47:17 INFO: [core] [Channel #7] Channel created 2023/09/25 10:47:17 INFO: [core] [Channel #7] original dial target is: "netbird.hidden.tech:33073" 2023/09/25 10:47:17 INFO: [core] [Channel #7] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:47:17 INFO: [core] [Channel #7] fallback to scheme "passthrough" 2023/09/25 10:47:17 INFO: [core] [Channel #7] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:47:17 INFO: [core] [Channel #7] Channel authority set to "netbird.hidden.tech:33073" 2023/09/25 10:47:17 INFO: [core] [Channel #7] Resolver state updated: { "Addresses": [ { "Addr": "netbird.hidden.tech:33073", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2023/09/25 10:47:17 INFO: [core] [Channel #7] Channel switches to new LB policy "pick_first" 2023/09/25 10:47:17 INFO: [core] [Channel #7 SubChannel #8] Subchannel created 2023/09/25 10:47:17 INFO: [core] [Channel #7] Channel Connectivity change to CONNECTING 2023/09/25 10:47:17 INFO: [core] [Channel #7 SubChannel #8] Subchannel Connectivity change to CONNECTING 2023/09/25 10:47:17 INFO: [core] [Channel #7 SubChannel #8] Subchannel picks a new address "netbird.hidden.tech:33073" to connect 2023/09/25 10:47:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0006660a8, {CONNECTING <nil>} 2023/09/25 10:47:22 INFO: [core] [Channel #7] Channel Connectivity change to SHUTDOWN 2023/09/25 10:47:22 INFO: [core] [Channel #7 SubChannel #8] Subchannel Connectivity change to SHUTDOWN 2023/09/25 10:47:22 INFO: [core] [Channel #7 SubChannel #8] Subchannel deleted 2023/09/25 10:47:22 INFO: [core] [Channel #7] Channel deleted 2023-09-25T10:47:22+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-09-25T10:47:22+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded 2023-09-25T10:47:22+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.731637762s due to error context deadline exceeded 2023/09/25 10:47:22 INFO: [core] Creating new client transport to "{\n \"Addr\": \"netbird.hidden.tech:33073\",\n \"ServerName\": \"netbird.hidden.tech:33073\",\n \"Attributes\": null,\n \"BalancerAttributes\": null,\n \"Type\": 0,\n \"Metadata\": null\n}": connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled" 2023/09/25 10:47:22 WARNING: [core] [Channel #7 SubChannel #8] grpc: addrConn.createTransport failed to connect to { "Addr": "netbird.hidden.tech:33073", "ServerName": "netbird.hidden.tech:33073", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null }. Err: connection error: desc = "transport: Error while dialing: dial tcp: lookup netbird.hidden.tech: operation was canceled" 2023-09-25T10:47:24+03:00 DEBG client/internal/login.go:93: connecting to the Management service https://netbird.hidden.tech:33073 2023/09/25 10:47:24 INFO: [core] [Channel #9] Channel created 2023/09/25 10:47:24 INFO: [core] [Channel #9] original dial target is: "netbird.hidden.tech:33073" 2023/09/25 10:47:24 INFO: [core] [Channel #9] parsed dial target is: {Scheme:netbird.hidden.tech Authority: URL:{Scheme:netbird.hidden.tech Opaque:33073 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:47:24 INFO: [core] [Channel #9] fallback to scheme "passthrough" 2023/09/25 10:47:24 INFO: [core] [Channel #9] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/netbird.hidden.tech:33073 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2023/09/25 10:47:24 INFO: [core] [Channel #9] Channel authority set to "netbird.hidden.tech:33073" 2023/09/25 10:47:24 INFO: [core] [Channel #9] Resolver state updated: { "Addresses": [ { "Addr": "netbird.hidden.tech:33073", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2023/09/25 10:47:24 INFO: [core] [Channel #9] Channel switches to new LB policy "pick_first" 2023/09/25 10:47:24 INFO: [core] [Channel #9 SubChannel #10] Subchannel created 2023/09/25 10:47:24 INFO: [core] [Channel #9] Channel Connectivity change to CONNECTING 2023/09/25 10:47:24 INFO: [core] [Channel #9 SubChannel #10] Subchannel Connectivity change to CONNECTING 2023/09/25 10:47:24 INFO: [core] [Channel #9 SubChannel #10] Subchannel picks a new address "netbird.hidden.tech:33073" to connect 2023/09/25 10:47:24 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0006f8090, {CONNECTING <nil>} 2023/09/25 10:47:29 INFO: [core] [Channel #9] Channel Connectivity change to SHUTDOWN 2023/09/25 10:47:29 INFO: [core] [Channel #9 SubChannel #10] Subchannel Connectivity change to SHUTDOWN 2023/09/25 10:47:29 INFO: [core] [Channel #9 SubChannel #10] Subchannel deleted 2023/09/25 10:47:29 INFO: [core] [Channel #9] Channel deleted 2023-09-25T10:47:29+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-09-25T10:47:29+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded Error: foreground login failed: backoff cycle failed: context deadline exceeded ```
Author
Owner

@kdre commented on GitHub (Oct 3, 2023):

Any news? This issue is very annoying and a deal breaker for me, if no solution is around the corner...

@kdre commented on GitHub (Oct 3, 2023): Any news? This issue is very annoying and a deal breaker for me, if no solution is around the corner...
Author
Owner

@bcmmbaga commented on GitHub (Oct 3, 2023):

Could you please upgrade to the most recent version, v0.23.6? After the update, follow these steps:

  • Execute sudo netbird service stop
  • Run sudo netbird service uninstall
  • Then, proceed with sudo netbird service install
  • Finally, initiate sudo netbird service start and test the client's connection with netbird up
@bcmmbaga commented on GitHub (Oct 3, 2023): Could you please upgrade to the most recent version, v0.23.6? After the update, follow these steps: - Execute `sudo netbird service stop` - Run `sudo netbird service uninstall` - Then, proceed with `sudo netbird service install` - Finally, initiate `sudo netbird service start ` and test the client's connection with `netbird up`
Author
Owner

@devopskupryk commented on GitHub (Oct 4, 2023):

There is no v0.23.6 available for my centos - v0.23.4 is the latest available.

I've tried your solution but result the same:

Downloading packages:
netbird_0.23.4_linux_amd64.rpm                                                                                                                         | 8.4 MB  00:00:05     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : netbird-0.23.4-1.x86_64                                                                                                                                    1/1 Post Install of an clean install
Netbird service has been installed
Netbird service has been started
  Verifying  : netbird-0.23.4-1.x86_64                                                                                                                                    1/1 

Installed:
  netbird.x86_64 0:0.23.4-1                                                                                                                                                   

Complete!
:~$ sudo netbird service stop
Netbird service has been stopped
:~$ sudo netbird service uninstall
Netbird has been uninstalled
:~$ sudo netbird service install
Netbird service has been installed
:~$ sudo netbird service start
Netbird service has been started
:~$ sudo netbird up --management-url https://netbird.hidden.tech:33073 --setup-key 'hidden'
Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded
:~$ sudo netbird down
sudo netbird up --management-url https://netbird.hidden.tech:33073 --setup-key 'hidden'
2023-10-04T10:39:55+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 890.429447ms due to error rpc error: code = DeadlineExceeded desc = context deadline exceeded
2023-10-04T10:40:06+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.12732371s due to error rpc error: code = DeadlineExceeded desc = context deadline exceeded
Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
:~$ tail /var/log/netbird/client.log
2023-10-04T10:40:01+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded
2023-10-04T10:40:06+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-10-04T10:40:06+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded
2023-10-04T10:40:06+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded
2023-10-04T10:40:12+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-10-04T10:40:12+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded
2023-10-04T10:40:12+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded
2023-10-04T10:40:17+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded
2023-10-04T10:40:17+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded
2023-10-04T10:40:17+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded
:~$ cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Any other suggestion?

@devopskupryk commented on GitHub (Oct 4, 2023): There is no v0.23.6 available for my centos - v0.23.4 is the latest available. I've tried your solution but result the same: ``` Downloading packages: netbird_0.23.4_linux_amd64.rpm | 8.4 MB 00:00:05 Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : netbird-0.23.4-1.x86_64 1/1 Post Install of an clean install Netbird service has been installed Netbird service has been started Verifying : netbird-0.23.4-1.x86_64 1/1 Installed: netbird.x86_64 0:0.23.4-1 Complete! :~$ sudo netbird service stop Netbird service has been stopped :~$ sudo netbird service uninstall Netbird has been uninstalled :~$ sudo netbird service install Netbird service has been installed :~$ sudo netbird service start Netbird service has been started :~$ sudo netbird up --management-url https://netbird.hidden.tech:33073 --setup-key 'hidden' Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded :~$ sudo netbird down sudo netbird up --management-url https://netbird.hidden.tech:33073 --setup-key 'hidden' 2023-10-04T10:39:55+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 890.429447ms due to error rpc error: code = DeadlineExceeded desc = context deadline exceeded 2023-10-04T10:40:06+03:00 WARN client/cmd/root.go:187: retrying Login to the Management service in 1.12732371s due to error rpc error: code = DeadlineExceeded desc = context deadline exceeded Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded :~$ tail /var/log/netbird/client.log 2023-10-04T10:40:01+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded 2023-10-04T10:40:06+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-10-04T10:40:06+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded 2023-10-04T10:40:06+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded 2023-10-04T10:40:12+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-10-04T10:40:12+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded 2023-10-04T10:40:12+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded 2023-10-04T10:40:17+03:00 ERRO management/client/grpc.go:64: failed creating connection to Management Service context deadline exceeded 2023-10-04T10:40:17+03:00 ERRO client/internal/login.go:96: failed connecting to the Management service https://netbird.hidden.tech:33073 context deadline exceeded 2023-10-04T10:40:17+03:00 ERRO client/server/server.go:124: failed login: context deadline exceeded :~$ cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" ``` Any other suggestion?
Author
Owner

@kdre commented on GitHub (Oct 4, 2023):

~ > sudo netbird service stop
Netbird service has been stopped
~ > sudo netbird service uninstall
Netbird has been uninstalled
~ > sudo netbird service install
Netbird service has been installed
~ > sudo netbird service start
Netbird service has been started
~ > netbird up
Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded
~ > netbird version
0.23.6

@kdre commented on GitHub (Oct 4, 2023): ~ > sudo netbird service stop Netbird service has been stopped ~ > sudo netbird service uninstall Netbird has been uninstalled ~ > sudo netbird service install Netbird service has been installed ~ > sudo netbird service start Netbird service has been started ~ > netbird up Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded ~ > netbird version 0.23.6
Author
Owner

@bcmmbaga commented on GitHub (Oct 4, 2023):

@kdre , @devopskupryk. To streamline the troubleshooting process and address your issue more effectively, we kindly request that you join our Slack or Matrix.

@bcmmbaga commented on GitHub (Oct 4, 2023): @kdre , @devopskupryk. To streamline the troubleshooting process and address your issue more effectively, we kindly request that you join our [Slack](https://join.slack.com/t/netbirdio/shared_invite/zt-vrahf41g-ik1v7fV8du6t0RwxSrJ96A) or [Matrix](https://matrix.to/#/#netbird:matrix.org).
Author
Owner

@tribor commented on GitHub (Oct 26, 2023):

I also stumbled across this kind of error today. For me the solution was to adjust my /etc/resolv.conf.
there were two entries for nameserver + search domain. after removing the second (original host) entry and keeping the one created by netbird, a "netbird up" worked again.

it seems that "netbird up" failed to resolve its required login servers.

@tribor commented on GitHub (Oct 26, 2023): I also stumbled across this kind of error today. For me the solution was to adjust my **/etc/resolv.conf**. there were **two entries for nameserver + search domain**. after removing the second (original host) entry and keeping the one created by netbird, a "netbird up" worked again. it seems that "netbird up" failed to resolve its required login servers.
Author
Owner

@mrmoose0 commented on GitHub (Nov 23, 2023):

I have this problem:
Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed while getting Management Service public key: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); malformed header: missing HTTP content-type

@mrmoose0 commented on GitHub (Nov 23, 2023): I have this problem: `Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed while getting Management Service public key: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); malformed header: missing HTTP content-type`
Author
Owner

@azey7f commented on GitHub (Dec 11, 2023):

I also stumbled across this kind of error today. For me the solution was to adjust my /etc/resolv.conf. there were two entries for nameserver + search domain. after removing the second (original host) entry and keeping the one created by netbird, a "netbird up" worked again.

it seems that "netbird up" failed to resolve its required login servers.

This also fixed it for me, apparently adding a custom DNS nameserver in netbird that's only accessible via the VPN causes this.

@azey7f commented on GitHub (Dec 11, 2023): > I also stumbled across this kind of error today. For me the solution was to adjust my **/etc/resolv.conf**. there were **two entries for nameserver + search domain**. after removing the second (original host) entry and keeping the one created by netbird, a "netbird up" worked again. > > it seems that "netbird up" failed to resolve its required login servers. This also fixed it for me, apparently adding a custom DNS nameserver in netbird that's only accessible via the VPN causes this.
Author
Owner

@bryanjuho commented on GitHub (Dec 19, 2023):

In my case, it was because I changed my Netbird host url (like... old.example.com → new.example.io).
Fix was to delete (or move to /tmp) the config.json in /etc/netbird/config.json,
and ran sudo netbird service uninstall. Not sure if which handled the issue though

@bryanjuho commented on GitHub (Dec 19, 2023): In my case, it was because I changed my Netbird host url (like... old.example.com → new.example.io). Fix was to delete (or move to /tmp) the config.json in /etc/netbird/config.json, and ran ```sudo netbird service uninstall```. Not sure if which handled the issue though
Author
Owner

@JonnyBDev commented on GitHub (Dec 31, 2023):

Just want to bring attention to this issue again. We had the same problem today with one of our servers. Server rebooted due to a failure (non Netbird related) and did not show up in Netbird as online. After running the command netbird up manually, we got the same error message as some of you above:

Error: status failed: failed connecting to Management Service : context deadline exceeded

We figured out that Netbird replaces or adds its own Nameserver (if configured) and search into the /etc/resolv.conf. The order was Netbird-configured-search, Netbird-configured-nameserver and then our two nameservers. We also noticed problems with the general DNS resolution to e.g. google.de. Our Netbird instance address resolves via a public DNS and therefore this setup won't work.

After removing all entries except our two public nameservers and waiting a few seconds, we could successfully connect to our Netbird instance with netbird up. This, obviously, overwrote the /etc/resolv.conf again. This will likely result in the same scenario if the machine goes down again the next time.

Is there any way to avoid this problem here?

@JonnyBDev commented on GitHub (Dec 31, 2023): Just want to bring attention to this issue again. We had the same problem today with one of our servers. Server rebooted due to a failure (non Netbird related) and did not show up in Netbird as online. After running the command `netbird up` manually, we got the same error message as some of you above: ``` Error: status failed: failed connecting to Management Service : context deadline exceeded ``` We figured out that Netbird replaces or adds its own Nameserver (if configured) and search into the `/etc/resolv.conf`. The order was Netbird-configured-search, Netbird-configured-nameserver and then our two nameservers. We also noticed problems with the general DNS resolution to e.g. google.de. Our Netbird instance address resolves via a public DNS and therefore this setup won't work. After removing all entries except our two public nameservers and waiting a few seconds, we could successfully connect to our Netbird instance with `netbird up`. This, obviously, overwrote the `/etc/resolv.conf` again. This will likely result in the same scenario if the machine goes down again the next time. Is there any way to avoid this problem here?
Author
Owner

@aatumaykin commented on GitHub (Jan 4, 2024):

Just want to bring attention to this issue again. We had the same problem today with one of our servers. Server rebooted due to a failure (non Netbird related) and did not show up in Netbird as online. After running the command netbird up manually, we got the same error message as some of you above:

Error: status failed: failed connecting to Management Service : context deadline exceeded

We figured out that Netbird replaces or adds its own Nameserver (if configured) and search into the /etc/resolv.conf. The order was Netbird-configured-search, Netbird-configured-nameserver and then our two nameservers. We also noticed problems with the general DNS resolution to e.g. google.de. Our Netbird instance address resolves via a public DNS and therefore this setup won't work.

After removing all entries except our two public nameservers and waiting a few seconds, we could successfully connect to our Netbird instance with netbird up. This, obviously, overwrote the /etc/resolv.conf again. This will likely result in the same scenario if the machine goes down again the next time.

Is there any way to avoid this problem here?

I found the same behavior. After removing the servers from resolv.conf, netbird connected.

@aatumaykin commented on GitHub (Jan 4, 2024): > Just want to bring attention to this issue again. We had the same problem today with one of our servers. Server rebooted due to a failure (non Netbird related) and did not show up in Netbird as online. After running the command `netbird up` manually, we got the same error message as some of you above: > > ``` > Error: status failed: failed connecting to Management Service : context deadline exceeded > ``` > > We figured out that Netbird replaces or adds its own Nameserver (if configured) and search into the `/etc/resolv.conf`. The order was Netbird-configured-search, Netbird-configured-nameserver and then our two nameservers. We also noticed problems with the general DNS resolution to e.g. google.de. Our Netbird instance address resolves via a public DNS and therefore this setup won't work. > > After removing all entries except our two public nameservers and waiting a few seconds, we could successfully connect to our Netbird instance with `netbird up`. This, obviously, overwrote the `/etc/resolv.conf` again. This will likely result in the same scenario if the machine goes down again the next time. > > Is there any way to avoid this problem here? I found the same behavior. After removing the servers from resolv.conf, netbird connected.
Author
Owner

@magixus commented on GitHub (Jan 9, 2024):

link to slack thread https://netbirdio.slack.com/archives/C05T5K65X7U/p1704806688445639

@magixus commented on GitHub (Jan 9, 2024): link to slack thread [https://netbirdio.slack.com/archives/C05T5K65X7U/p1704806688445639](https://netbirdio.slack.com/archives/C05T5K65X7U/p1704806688445639)
Author
Owner

@inboardnor commented on GitHub (Feb 5, 2024):

I have this problem: Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed while getting Management Service public key: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); malformed header: missing HTTP content-type

this is the error I also have. Where you able to resolve your issue?

@inboardnor commented on GitHub (Feb 5, 2024): > I have this problem: `Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed while getting Management Service public key: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); malformed header: missing HTTP content-type` this is the error I also have. Where you able to resolve your issue?
Author
Owner

@robertompf commented on GitHub (Feb 11, 2024):

for nam

@robertompf commented on GitHub (Feb 11, 2024): > for nam
Author
Owner

@peterdieleman commented on GitHub (Apr 18, 2024):

This issue (the DeadlineExceeded ..) re-appears for us when running the latest available current version (0.27.3) on alma linux. We are unable to get netbird running.

Our fix was downgrading to 0.26.3. We have checked the /etc/resolv.conf file for additional entries as well as using the command by @mlsmaycon to increase grpc logging level, but neither of those made us any wiser.

@peterdieleman commented on GitHub (Apr 18, 2024): This issue (the DeadlineExceeded ..) re-appears for us when running the latest available current version (`0.27.3`) on alma linux. We are unable to get netbird running. Our fix was downgrading to 0.26.3. We have checked the `/etc/resolv.conf` file for additional entries as well as using the command by @mlsmaycon to increase grpc logging level, but neither of those made us any wiser.
Author
Owner

@mrbluecoat commented on GitHub (May 4, 2024):

Same for me on desktop with Ubuntu 22.04.4 LTS and the latest version 0.27.4 via the recommended installation method: curl -fsSL https://pkgs.netbird.io/install.sh | sh

I tried a variety of permutations:

netbird up
sudo netbird up
netbird up --setup-key 12345...

They all give me the same error: Error: login failed: rpc error: code = PermissionDenied desc = peer login has expired, please log in once more

I edited my /etc/resolv.conf and just put a single entry nameserver 1.1.1.1 but still no luck

Reboot made no difference

Update: upgrading to Ubuntu 24.04 fixed it for me.

@mrbluecoat commented on GitHub (May 4, 2024): Same for me on desktop with Ubuntu 22.04.4 LTS and the latest version 0.27.4 via the recommended installation method: ` curl -fsSL https://pkgs.netbird.io/install.sh | sh` I tried a variety of permutations: ``` netbird up sudo netbird up netbird up --setup-key 12345... ``` They all give me the same error: `Error: login failed: rpc error: code = PermissionDenied desc = peer login has expired, please log in once more` I edited my `/etc/resolv.conf` and just put a single entry `nameserver 1.1.1.1` but still no luck Reboot made no difference **Update**: upgrading to Ubuntu 24.04 fixed it for me.
Author
Owner

@beastma commented on GitHub (May 13, 2024):

Same here, on openwrt netbird version 0.27.3

`Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded

netbird status -d

Error: status failed: failed connecting to Management Service : context deadline exceeded

netbird status -d output:

Peers detail:
Daemon version: 0.27.3
CLI version: 0.27.3
Management: Disconnected, reason: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded
Signal: Disconnected
Relays:
Nameservers:
FQDN:
NetBird IP: N/A
Interface type: N/A
Quantum resistance: false
Routes: -
Peers count: 0/0 Connected

sudo netbird service stop

Netbird service has been stopped

sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F

-l debug'
2024-05-13T04:13:57Z DEBG client/internal/login.go:93: connecting to the Management service https://api.netbird.io:443
2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel created
2024/05/13 04:13:57 INFO: [core] [Channel #1] original dial target is: "api.netbird.io:443"
2024/05/13 04:13:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:api.netbird.io Authority: URL:{Scheme:api.netbird.io Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2024/05/13 04:13:57 INFO: [core] [Channel #1] fallback to scheme "passthrough"
2024/05/13 04:13:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.netbird.io:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel authority set to "api.netbird.io:443"
2024/05/13 04:13:57 INFO: [core] [Channel #1] Resolver state updated: {
"Addresses": [
{
"Addr": "api.netbird.io:443",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first"
2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel created
2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING
2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING
2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:13:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING }
2024-05-13T04:13:57Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:13:57 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:13:57 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:13:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel Connectivity change to TRANSIENT_FAILURE
2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING
2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING }
2024-05-13T04:13:58Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:13:58 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:13:58 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING
2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING }
2024-05-13T04:14:00Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:14:00 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:00 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING
2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING }
2024-05-13T04:14:02Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:14:02 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:02 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING
2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING }
2024-05-13T04:14:06Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:14:06 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:06 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:07 INFO: [core] [Channel #1] Channel Connectivity change to SHUTDOWN
2024/05/13 04:14:07 INFO: [core] [Channel #1] ccBalancerWrapper: closing
2024/05/13 04:14:07 INFO: [core] [Channel #1] Closing the name resolver
2024/05/13 04:14:07 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to SHUTDOWN
2024/05/13 04:14:07 INFO: [core] [Channel #1 SubChannel #2] Subchannel deleted
2024/05/13 04:14:07 INFO: [core] [Channel #1] Channel deleted
2024-05-13T04:14:07Z ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded
2024-05-13T04:14:07Z ERRO client/internal/login.go:96: failed connecting to the Management service https://api.netbird.io:443 context deadline exceeded
2024-05-13T04:14:07Z WARN client/cmd/root.go:214: retrying Login to the Management service in 734.073652ms due to error context deadline exceeded
2024-05-13T04:14:08Z DEBG client/internal/login.go:93: connecting to the Management service https://api.netbird.io:443
2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel created
2024/05/13 04:14:08 INFO: [core] [Channel #3] original dial target is: "api.netbird.io:443"
2024/05/13 04:14:08 INFO: [core] [Channel #3] parsed dial target is: {Scheme:api.netbird.io Authority: URL:{Scheme:api.netbird.io Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2024/05/13 04:14:08 INFO: [core] [Channel #3] fallback to scheme "passthrough"
2024/05/13 04:14:08 INFO: [core] [Channel #3] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.netbird.io:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel authority set to "api.netbird.io:443"
2024/05/13 04:14:08 INFO: [core] [Channel #3] Resolver state updated: {
"Addresses": [
{
"Addr": "api.netbird.io:443",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel switches to new LB policy "pick_first"
2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel created
2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel Connectivity change to CONNECTING
2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING
2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:14:08 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING }
2024-05-13T04:14:08Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:14:08 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:08 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:08 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel Connectivity change to TRANSIENT_FAILURE
2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING
2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING }
2024-05-13T04:14:09Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:14:09 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:09 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING
2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING }
2024-05-13T04:14:11Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:14:11 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:11 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING
2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING }
2024-05-13T04:14:13Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:14:13 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:13 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING
2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect
2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING }
2024-05-13T04:14:17Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument
2024/05/13 04:14:17 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:17 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"
2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"}
2024/05/13 04:14:18 INFO: [core] [Channel #3] Channel Connectivity change to SHUTDOWN
2024/05/13 04:14:18 INFO: [core] [Channel #3] ccBalancerWrapper: closing
2024/05/13 04:14:18 INFO: [core] [Channel #3] Closing the name resolver
2024/05/13 04:14:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to SHUTDOWN
2024/05/13 04:14:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel deleted
2024/05/13 04:14:18 INFO: [core] [Channel #3] Channel deleted
2024-05-13T04:14:18Z ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded
2024-05-13T04:14:18Z ERRO client/internal/login.go:96: failed connecting to the Management service https://api.netbird.io:443 context deadline exceeded
2024-05-13T04:14:18Z WARN client/cmd/root.go:214: retrying Login to the Management service in 2.018719926s due to error context deadline exceeded`

ping api.netbird.io PING api.netbird.io (35.186.199.111): 56 data bytes 64 bytes from 35.186.199.111: seq=0 ttl=114 time=11.965 ms 64 bytes from 35.186.199.111: seq=1 ttl=114 time=12.270 ms 64 bytes from 35.186.199.111: seq=2 ttl=114 time=12.027 ms

cat /etc/resolv.conf search lan nameserver 127.0.0.1 nameserver ::1

I was thinking it could be caused by DNS , but It is able to resolve the api link just fine.
I tried to get help in the slack but not results.
Any suggestions?

@beastma commented on GitHub (May 13, 2024): Same here, on openwrt netbird version 0.27.3 `Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded # netbird status -d Error: status failed: failed connecting to Management Service : context deadline exceeded # netbird status -d output: Peers detail: Daemon version: 0.27.3 CLI version: 0.27.3 Management: Disconnected, reason: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded Signal: Disconnected Relays: Nameservers: FQDN: NetBird IP: N/A Interface type: N/A Quantum resistance: false Routes: - Peers count: 0/0 Connected # sudo netbird service stop Netbird service has been stopped # sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F -l debug' 2024-05-13T04:13:57Z DEBG client/internal/login.go:93: connecting to the Management service https://api.netbird.io:443 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel created 2024/05/13 04:13:57 INFO: [core] [Channel #1] original dial target is: "api.netbird.io:443" 2024/05/13 04:13:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:api.netbird.io Authority: URL:{Scheme:api.netbird.io Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:13:57 INFO: [core] [Channel #1] fallback to scheme "passthrough" 2024/05/13 04:13:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.netbird.io:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel authority set to "api.netbird.io:443" 2024/05/13 04:13:57 INFO: [core] [Channel #1] Resolver state updated: { "Addresses": [ { "Addr": "api.netbird.io:443", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first" 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel created 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:13:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING <nil>} 2024-05-13T04:13:57Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:13:57 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:57 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel Connectivity change to TRANSIENT_FAILURE 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING <nil>} 2024-05-13T04:13:58Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:13:58 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING <nil>} 2024-05-13T04:14:00Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:00 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING <nil>} 2024-05-13T04:14:02Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:02 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING <nil>} 2024-05-13T04:14:06Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:06 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:07 INFO: [core] [Channel #1] Channel Connectivity change to SHUTDOWN 2024/05/13 04:14:07 INFO: [core] [Channel #1] ccBalancerWrapper: closing 2024/05/13 04:14:07 INFO: [core] [Channel #1] Closing the name resolver 2024/05/13 04:14:07 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to SHUTDOWN 2024/05/13 04:14:07 INFO: [core] [Channel #1 SubChannel #2] Subchannel deleted 2024/05/13 04:14:07 INFO: [core] [Channel #1] Channel deleted 2024-05-13T04:14:07Z ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded 2024-05-13T04:14:07Z ERRO client/internal/login.go:96: failed connecting to the Management service https://api.netbird.io:443 context deadline exceeded 2024-05-13T04:14:07Z WARN client/cmd/root.go:214: retrying Login to the Management service in 734.073652ms due to error context deadline exceeded 2024-05-13T04:14:08Z DEBG client/internal/login.go:93: connecting to the Management service https://api.netbird.io:443 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel created 2024/05/13 04:14:08 INFO: [core] [Channel #3] original dial target is: "api.netbird.io:443" 2024/05/13 04:14:08 INFO: [core] [Channel #3] parsed dial target is: {Scheme:api.netbird.io Authority: URL:{Scheme:api.netbird.io Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:14:08 INFO: [core] [Channel #3] fallback to scheme "passthrough" 2024/05/13 04:14:08 INFO: [core] [Channel #3] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.netbird.io:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel authority set to "api.netbird.io:443" 2024/05/13 04:14:08 INFO: [core] [Channel #3] Resolver state updated: { "Addresses": [ { "Addr": "api.netbird.io:443", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel switches to new LB policy "pick_first" 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel created 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel Connectivity change to CONNECTING 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:08 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING <nil>} 2024-05-13T04:14:08Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:08 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:08 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:08 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel Connectivity change to TRANSIENT_FAILURE 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING <nil>} 2024-05-13T04:14:09Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:09 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING <nil>} 2024-05-13T04:14:11Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:11 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING <nil>} 2024-05-13T04:14:13Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:13 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING <nil>} 2024-05-13T04:14:17Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:17 INFO: [core] Creating new client transport to "{Addr: \"api.netbird.io:443\", ServerName: \"api.netbird.io:443\", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:18 INFO: [core] [Channel #3] Channel Connectivity change to SHUTDOWN 2024/05/13 04:14:18 INFO: [core] [Channel #3] ccBalancerWrapper: closing 2024/05/13 04:14:18 INFO: [core] [Channel #3] Closing the name resolver 2024/05/13 04:14:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to SHUTDOWN 2024/05/13 04:14:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel deleted 2024/05/13 04:14:18 INFO: [core] [Channel #3] Channel deleted 2024-05-13T04:14:18Z ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded 2024-05-13T04:14:18Z ERRO client/internal/login.go:96: failed connecting to the Management service https://api.netbird.io:443 context deadline exceeded 2024-05-13T04:14:18Z WARN client/cmd/root.go:214: retrying Login to the Management service in 2.018719926s due to error context deadline exceeded` `ping api.netbird.io PING api.netbird.io (35.186.199.111): 56 data bytes 64 bytes from 35.186.199.111: seq=0 ttl=114 time=11.965 ms 64 bytes from 35.186.199.111: seq=1 ttl=114 time=12.270 ms 64 bytes from 35.186.199.111: seq=2 ttl=114 time=12.027 ms` `cat /etc/resolv.conf search lan nameserver 127.0.0.1 nameserver ::1` I was thinking it could be caused by DNS , but It is able to resolve the api link just fine. I tried to get help in the slack but not results. Any suggestions?
Author
Owner

@beastma commented on GitHub (May 13, 2024):

Same here, on openwrt netbird version 0.27.3

`Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded

netbird status -d

Error: status failed: failed connecting to Management Service : context deadline exceeded

netbird status -d output:

Peers detail: Daemon version: 0.27.3 CLI version: 0.27.3 Management: Disconnected, reason: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded Signal: Disconnected Relays: Nameservers: FQDN: NetBird IP: N/A Interface type: N/A Quantum resistance: false Routes: - Peers count: 0/0 Connected

sudo netbird service stop

Netbird service has been stopped

sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F

-l debug' 2024-05-13T04:13:57Z DEBG client/internal/login.go:93: connecting to the Management service https://api.netbird.io:443 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel created 2024/05/13 04:13:57 INFO: [core] [Channel #1] original dial target is: "api.netbird.io:443" 2024/05/13 04:13:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:api.netbird.io Authority: URL:{Scheme:api.netbird.io Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:13:57 INFO: [core] [Channel #1] fallback to scheme "passthrough" 2024/05/13 04:13:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.netbird.io:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel authority set to "api.netbird.io:443" 2024/05/13 04:13:57 INFO: [core] [Channel #1] Resolver state updated: { "Addresses": [ { "Addr": "api.netbird.io:443", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first" 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel created 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:13:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:13:57Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:13:57 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:57 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel Connectivity change to TRANSIENT_FAILURE 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:13:58Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:13:58 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:14:00Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:00 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:14:02Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:02 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:14:06Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:06 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:07 INFO: [core] [Channel #1] Channel Connectivity change to SHUTDOWN 2024/05/13 04:14:07 INFO: [core] [Channel #1] ccBalancerWrapper: closing 2024/05/13 04:14:07 INFO: [core] [Channel #1] Closing the name resolver 2024/05/13 04:14:07 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to SHUTDOWN 2024/05/13 04:14:07 INFO: [core] [Channel #1 SubChannel #2] Subchannel deleted 2024/05/13 04:14:07 INFO: [core] [Channel #1] Channel deleted 2024-05-13T04:14:07Z ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded 2024-05-13T04:14:07Z ERRO client/internal/login.go:96: failed connecting to the Management service https://api.netbird.io:443 context deadline exceeded 2024-05-13T04:14:07Z WARN client/cmd/root.go:214: retrying Login to the Management service in 734.073652ms due to error context deadline exceeded 2024-05-13T04:14:08Z DEBG client/internal/login.go:93: connecting to the Management service https://api.netbird.io:443 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel created 2024/05/13 04:14:08 INFO: [core] [Channel #3] original dial target is: "api.netbird.io:443" 2024/05/13 04:14:08 INFO: [core] [Channel #3] parsed dial target is: {Scheme:api.netbird.io Authority: URL:{Scheme:api.netbird.io Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:14:08 INFO: [core] [Channel #3] fallback to scheme "passthrough" 2024/05/13 04:14:08 INFO: [core] [Channel #3] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.netbird.io:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel authority set to "api.netbird.io:443" 2024/05/13 04:14:08 INFO: [core] [Channel #3] Resolver state updated: { "Addresses": [ { "Addr": "api.netbird.io:443", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel switches to new LB policy "pick_first" 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel created 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel Connectivity change to CONNECTING 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:08 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:08Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:08 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:08 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:08 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel Connectivity change to TRANSIENT_FAILURE 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:09Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:09 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:11Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:11 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:13Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:13 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:17Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:17 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:18 INFO: [core] [Channel #3] Channel Connectivity change to SHUTDOWN 2024/05/13 04:14:18 INFO: [core] [Channel #3] ccBalancerWrapper: closing 2024/05/13 04:14:18 INFO: [core] [Channel #3] Closing the name resolver 2024/05/13 04:14:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to SHUTDOWN 2024/05/13 04:14:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel deleted 2024/05/13 04:14:18 INFO: [core] [Channel #3] Channel deleted 2024-05-13T04:14:18Z ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded 2024-05-13T04:14:18Z ERRO client/internal/login.go:96: failed connecting to the Management service https://api.netbird.io:443 context deadline exceeded 2024-05-13T04:14:18Z WARN client/cmd/root.go:214: retrying Login to the Management service in 2.018719926s due to error context deadline exceeded`

ping api.netbird.io PING api.netbird.io (35.186.199.111): 56 data bytes 64 bytes from 35.186.199.111: seq=0 ttl=114 time=11.965 ms 64 bytes from 35.186.199.111: seq=1 ttl=114 time=12.270 ms 64 bytes from 35.186.199.111: seq=2 ttl=114 time=12.027 ms

cat /etc/resolv.conf search lan nameserver 127.0.0.1 nameserver ::1

I was thinking it could be caused by DNS , but It is able to resolve the api link just fine. I tried to get help in the slack but not results. Any suggestions?

update:
Installed netbird verions 0.17.0 and worked right away, so apparently was a issue with previous mentioned version.

@beastma commented on GitHub (May 13, 2024): > Same here, on openwrt netbird version 0.27.3 > > `Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded > > # netbird status -d > Error: status failed: failed connecting to Management Service : context deadline exceeded > > # netbird status -d output: > Peers detail: Daemon version: 0.27.3 CLI version: 0.27.3 Management: Disconnected, reason: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded Signal: Disconnected Relays: Nameservers: FQDN: NetBird IP: N/A Interface type: N/A Quantum resistance: false Routes: - Peers count: 0/0 Connected > > # sudo netbird service stop > Netbird service has been stopped > > # sudo bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F > -l debug' 2024-05-13T04:13:57Z DEBG client/internal/login.go:93: connecting to the Management service https://api.netbird.io:443 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel created 2024/05/13 04:13:57 INFO: [core] [Channel #1] original dial target is: "api.netbird.io:443" 2024/05/13 04:13:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:api.netbird.io Authority: URL:{Scheme:api.netbird.io Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:13:57 INFO: [core] [Channel #1] fallback to scheme "passthrough" 2024/05/13 04:13:57 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.netbird.io:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel authority set to "api.netbird.io:443" 2024/05/13 04:13:57 INFO: [core] [Channel #1] Resolver state updated: { "Addresses": [ { "Addr": "api.netbird.io:443", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first" 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel created 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:13:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:13:57Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:13:57 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:57 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:57 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:57 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:13:57 INFO: [core] [Channel #1] Channel Connectivity change to TRANSIENT_FAILURE 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:13:58Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:13:58 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:13:58 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:14:00Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:00 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:00 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:14:02Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:02 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:02 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {CONNECTING } 2024-05-13T04:14:06Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:06 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 WARNING: [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:06 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x3476b10, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:07 INFO: [core] [Channel #1] Channel Connectivity change to SHUTDOWN 2024/05/13 04:14:07 INFO: [core] [Channel #1] ccBalancerWrapper: closing 2024/05/13 04:14:07 INFO: [core] [Channel #1] Closing the name resolver 2024/05/13 04:14:07 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to SHUTDOWN 2024/05/13 04:14:07 INFO: [core] [Channel #1 SubChannel #2] Subchannel deleted 2024/05/13 04:14:07 INFO: [core] [Channel #1] Channel deleted 2024-05-13T04:14:07Z ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded 2024-05-13T04:14:07Z ERRO client/internal/login.go:96: failed connecting to the Management service https://api.netbird.io:443 context deadline exceeded 2024-05-13T04:14:07Z WARN client/cmd/root.go:214: retrying Login to the Management service in 734.073652ms due to error context deadline exceeded 2024-05-13T04:14:08Z DEBG client/internal/login.go:93: connecting to the Management service https://api.netbird.io:443 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel created 2024/05/13 04:14:08 INFO: [core] [Channel #3] original dial target is: "api.netbird.io:443" 2024/05/13 04:14:08 INFO: [core] [Channel #3] parsed dial target is: {Scheme:api.netbird.io Authority: URL:{Scheme:api.netbird.io Opaque:443 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:14:08 INFO: [core] [Channel #3] fallback to scheme "passthrough" 2024/05/13 04:14:08 INFO: [core] [Channel #3] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/api.netbird.io:443 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel authority set to "api.netbird.io:443" 2024/05/13 04:14:08 INFO: [core] [Channel #3] Resolver state updated: { "Addresses": [ { "Addr": "api.netbird.io:443", "ServerName": "", "Attributes": null, "BalancerAttributes": null, "Type": 0, "Metadata": null } ], "ServiceConfig": null, "Attributes": null } (resolver returned new addresses) 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel switches to new LB policy "pick_first" 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel created 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel Connectivity change to CONNECTING 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:08 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:08Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:08 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:08 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:08 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:08 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:08 INFO: [core] [Channel #3] Channel Connectivity change to TRANSIENT_FAILURE 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:09Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:09 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:11Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:11 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:11 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:13Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:13 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:13 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {IDLE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel picks a new address "api.netbird.io:443" to connect 2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {CONNECTING } 2024-05-13T04:14:17Z ERRO util/grpc/dialer.go:33: Failed to dial: dial: dial tcp 35.186.199.111:443: connect: invalid argument 2024/05/13 04:14:17 INFO: [core] Creating new client transport to "{Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }": connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 WARNING: [core] [Channel #3 SubChannel #4] grpc: addrConn.createTransport failed to connect to {Addr: "api.netbird.io:443", ServerName: "api.netbird.io:443", }. Err: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument" 2024/05/13 04:14:17 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0x34777d0, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial: dial tcp 35.186.199.111:443: connect: invalid argument"} 2024/05/13 04:14:18 INFO: [core] [Channel #3] Channel Connectivity change to SHUTDOWN 2024/05/13 04:14:18 INFO: [core] [Channel #3] ccBalancerWrapper: closing 2024/05/13 04:14:18 INFO: [core] [Channel #3] Closing the name resolver 2024/05/13 04:14:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to SHUTDOWN 2024/05/13 04:14:18 INFO: [core] [Channel #3 SubChannel #4] Subchannel deleted 2024/05/13 04:14:18 INFO: [core] [Channel #3] Channel deleted 2024-05-13T04:14:18Z ERRO management/client/grpc.go:68: failed creating connection to Management Service context deadline exceeded 2024-05-13T04:14:18Z ERRO client/internal/login.go:96: failed connecting to the Management service https://api.netbird.io:443 context deadline exceeded 2024-05-13T04:14:18Z WARN client/cmd/root.go:214: retrying Login to the Management service in 2.018719926s due to error context deadline exceeded` > > `ping api.netbird.io PING api.netbird.io (35.186.199.111): 56 data bytes 64 bytes from 35.186.199.111: seq=0 ttl=114 time=11.965 ms 64 bytes from 35.186.199.111: seq=1 ttl=114 time=12.270 ms 64 bytes from 35.186.199.111: seq=2 ttl=114 time=12.027 ms` > > `cat /etc/resolv.conf search lan nameserver 127.0.0.1 nameserver ::1` > > I was thinking it could be caused by DNS , but It is able to resolve the api link just fine. I tried to get help in the slack but not results. Any suggestions? update: Installed netbird verions 0.17.0 and worked right away, so apparently was a issue with previous mentioned version.
Author
Owner

@ecker00 commented on GitHub (May 23, 2024):

Might be affected by this as well, or it might be slightly different issue. All Proxmox PVE and PBS instances will eventually disconnect from peers, or end up with Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded after being connected for a while. Bringing it down and up solves it for an undefined amount of time before the issue returns (sometimes takes a day, or about an hour).

So far I've just setup a cronjob */20 * * * * /usr/bin/netbird down && /usr/bin/netbird up which seems to keep things connected.

Tested on 4 different PVE hosts (v7.x and v8.x) and 3 different PVB instances (v2.x and v3.x) and they all suffer from this. Does not seem to affect other servers we got.

@ecker00 commented on GitHub (May 23, 2024): Might be affected by this as well, or it might be slightly different issue. All Proxmox PVE and PBS instances will eventually disconnect from peers, or end up with `Error: unable to get daemon status: rpc error: code = FailedPrecondition desc = failed connecting to Management Service : context deadline exceeded` after being connected for a while. Bringing it down and up solves it for an undefined amount of time before the issue returns (sometimes takes a day, or about an hour). So far I've just setup a cronjob `*/20 * * * * /usr/bin/netbird down && /usr/bin/netbird up` which seems to keep things connected. Tested on 4 different PVE hosts (v7.x and v8.x) and 3 different PVB instances (v2.x and v3.x) and they all suffer from this. Does not seem to affect other servers we got.
Author
Owner

@ZabotoBlack commented on GitHub (Jun 21, 2024):

Hi, I also had an issue with registration I used a Proxmox Ubuntu LXC and installed the latest netbird client version.
There was only this one line in the client.log: " ERRO management/client/grpc.go:287: failed while getting Management Service public key: rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type "text/html" "
The other log files were all empty.
I deleted the LXC and created a new one and everything worked fine with the registration.

PS: This comment is just to let you know about the error. Reach out to me if you need further information.

@ZabotoBlack commented on GitHub (Jun 21, 2024): Hi, I also had an issue with registration I used a Proxmox Ubuntu LXC and installed the latest netbird client version. There was only this one line in the client.log: " ERRO management/client/grpc.go:287: failed while getting Management Service public key: rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type "text/html" " The other log files were all empty. I deleted the LXC and created a new one and everything worked fine with the registration. PS: This comment is just to let you know about the error. Reach out to me if you need further information.
Author
Owner

@khanfarhan10 commented on GitHub (Jul 8, 2024):

@gmatasba @Sxndxr the issue was fixed in v0.22.2, can you test on your end?

I'm facing the same on version 0.27.10

@khanfarhan10 commented on GitHub (Jul 8, 2024): > @gmatasba @Sxndxr the issue was fixed in v0.22.2, can you test on your end? I'm facing the same on version `0.27.10`
Author
Owner

@Stunt0265 commented on GitHub (Jul 18, 2024):

Having the same issue on Zorin OS 17.1

@Stunt0265 commented on GitHub (Jul 18, 2024): Having the same issue on Zorin OS 17.1
Author
Owner

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

possibly related to #2116 as https://github.com/netbirdio/netbird/issues/1048#issuecomment-2106635400 mentions the invalid argument error during connecting to API server

@nazarewk commented on GitHub (Sep 3, 2024): possibly related to #2116 as https://github.com/netbirdio/netbird/issues/1048#issuecomment-2106635400 mentions the `invalid argument` error during connecting to API server
Author
Owner

@dillfrescott commented on GitHub (Oct 18, 2024):

Same issues on archlinux on a laptop:

Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded

Using official api

EDIT: Was not fixed with a reboot, only temporarily.

@dillfrescott commented on GitHub (Oct 18, 2024): Same issues on archlinux on a laptop: ``` Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded ``` Using official api EDIT: Was not fixed with a reboot, only temporarily.
Author
Owner

@abewartech commented on GitHub (Oct 27, 2024):

  1. Stop the Netbird Service
    You've already stopped the service, but you can confirm it’s inactive with:
sudo systemctl stop netbird
sudo systemctl disable netbird
  1. Remove Netbird Files
    Use these commands to remove Netbird’s files and directories:
sudo rm -rf /usr/local/bin/netbird
sudo rm -rf /etc/netbird
sudo rm -rf /var/lib/netbird
  1. Uninstall Netbird if Installed via apt
    If you used apt to install Netbird, you can also remove it with:

sudo apt remove netbird -y
4. Reinstall Netbird
Now, reinstall Netbird:

curl -fsSL https://pkgs.netbird.io/install.sh | sudo bash
sudo apt update
sudo apt install netbird -y

Finally, start Netbird again:

sudo netbird up

Worked for me

@abewartech commented on GitHub (Oct 27, 2024): 1. Stop the Netbird Service You've already stopped the service, but you can confirm it’s inactive with: ``` sudo systemctl stop netbird sudo systemctl disable netbird ``` 2. Remove Netbird Files Use these commands to remove Netbird’s files and directories: ``` sudo rm -rf /usr/local/bin/netbird sudo rm -rf /etc/netbird sudo rm -rf /var/lib/netbird ``` 3. Uninstall Netbird if Installed via apt If you used apt to install Netbird, you can also remove it with: `sudo apt remove netbird -y` 4. Reinstall Netbird Now, reinstall Netbird: ``` curl -fsSL https://pkgs.netbird.io/install.sh | sudo bash sudo apt update sudo apt install netbird -y ``` Finally, start Netbird again: `sudo netbird up` Worked for me
Author
Owner

@szEvEz commented on GitHub (Dec 5, 2024):

Same Issue on AlmaLinux 9.5, we had to pin to 0.26.3

@szEvEz commented on GitHub (Dec 5, 2024): Same Issue on AlmaLinux 9.5, we had to pin to `0.26.3`
Author
Owner

@s0me1newithhand7s commented on GitHub (Jan 12, 2025):

Same on NixOS 25.05,

[hand7s@nixos:~]$ netbird version
0.35.2
@s0me1newithhand7s commented on GitHub (Jan 12, 2025): Same on NixOS 25.05, ```Shell [hand7s@nixos:~]$ netbird version 0.35.2 ```
Author
Owner

@s0me1newithhand7s commented on GitHub (Jan 19, 2025):

Same on NixOS 25.05,

[hand7s@nixos:~]$ netbird version
0.35.2

funny enough, but setting up custom DNSes helped with this issue on my side

@s0me1newithhand7s commented on GitHub (Jan 19, 2025): > Same on NixOS 25.05, > > [hand7s@nixos:~]$ netbird version > 0.35.2 funny enough, but setting up custom DNSes helped with this issue on my side
Author
Owner

@andiikaa commented on GitHub (Mar 19, 2025):

@abewartech solution worked for me only for the login part with a setup key.

sudo netbird up still fails to connect with

Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded

We are also stuck with 0.26.3 for quite a time .

@andiikaa commented on GitHub (Mar 19, 2025): @abewartech solution worked for me only for the login part with a setup key. `sudo netbird up` still fails to connect with ```bash Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded ``` We are also stuck with `0.26.3` for quite a time .
Author
Owner

@sleb23 commented on GitHub (Mar 27, 2025):

Just in case it helps anyone else - I'm self-hosting using SWAG/Nginx, and I was having this same issue all of a sudden. However, I noticed that my 'netbird' subdomain wasn't getting included during my cert generation, but it was present in my SWAG docker compose file. In my case, my Ansible playbook brought up the Netbird containers before rebuilding SWAG; so without the <netbird.domain> cert, the gRPC comms weren't making it to management or the service couldn't respond.

The fix for me was to `docker compose down' on both Netbird and SWAG, then 'docker compose up -d' on SWAG, then the same on Netbird - basically just ensured the cert was proper.

@sleb23 commented on GitHub (Mar 27, 2025): Just in case it helps anyone else - I'm self-hosting using SWAG/Nginx, and I was having this same issue all of a sudden. However, I noticed that my 'netbird' subdomain wasn't getting included during my cert generation, but it was present in my SWAG docker compose file. In my case, my Ansible playbook brought up the Netbird containers before rebuilding SWAG; so without the <netbird.domain> cert, the gRPC comms weren't making it to management or the service couldn't respond. The fix for me was to `docker compose down' on both Netbird and SWAG, then 'docker compose up -d' on SWAG, then the same on Netbird - basically just ensured the cert was proper.
Author
Owner

@Luk1e commented on GitHub (Mar 28, 2025):

The issue occurs when you shut down your PC without disconnecting NetBird. On some PCs, this causes problems where the state file becomes corrupted. The corrupted state file leads to errors and NetBird failing to work as expected.

Steps to reproduce:

  1. Shut down the PC without disconnecting NetBird.
  2. On some systems, when restarting, NetBird will encounter errors related to the corrupted state file.

Affected Files:

You can find the state file and related files on Windows at:
C:\ProgramData\Netbird

The four files present are:

Image

Error:

When the issue occurs, you will see errors in the netbird.err file, and the state.json file will be corrupted.

Solution:

  1. Delete all files in the C:\ProgramData\Netbird folder.

  2. Run the following commands:

    netbird service install
    netbird service start
    
    
  3. Important: To start NetBird, you have two options:

  • NetBird setup with a custom network
  • Interactive SSO login

You must log in using SSO (e.g., Google) first. This is crucial because only logging in via SSO creates the correct state.json file, which is why the error persists otherwise.

  1. Once logged in via SSO, you can proceed with the netbird setup to configure your network
@Luk1e commented on GitHub (Mar 28, 2025): The issue occurs when you shut down your PC without disconnecting NetBird. On some PCs, this causes problems where the state file becomes corrupted. The corrupted state file leads to errors and NetBird failing to work as expected. **Steps to reproduce:** 1. Shut down the PC without disconnecting NetBird. 2. On some systems, when restarting, NetBird will encounter errors related to the corrupted state file. **Affected Files:** You can find the state file and related files on Windows at: `C:\ProgramData\Netbird` The four files present are: ![Image](https://github.com/user-attachments/assets/17f68753-d6b9-4530-9dcd-6829269a324c) **Error:** When the issue occurs, you will see errors in the `netbird.err` file, and the `state.json` file will be corrupted. **Solution:** 1. Delete all files in the `C:\ProgramData\Netbird` folder. 2. Run the following commands: ```bash netbird service install netbird service start 3. Important: To start NetBird, you have two options: - NetBird setup with a custom network - Interactive SSO login You must log in using SSO (e.g., Google) first. This is crucial because only logging in via SSO creates the correct state.json file, which is why the error persists otherwise. 4. Once logged in via SSO, you can proceed with the netbird setup to configure your network
Author
Owner

@trevorijones commented on GitHub (May 3, 2025):

Having the same issue on OpenWrt 22.03.4 (adapt to your arch):

  • netbird_0.17.0-1_aarch64_cortex-a53.ipk --> OK
  • netbird_0.24.3-1_aarch64_cortex-a53.ipk --> OK
  • netbird_0.39.2-r1_aarch64_cortex-a53.ipk --> KO
@trevorijones commented on GitHub (May 3, 2025): Having the same issue on OpenWrt 22.03.4 (adapt to your arch): - netbird_0.17.0-1_aarch64_cortex-a53.ipk --> OK - netbird_0.24.3-1_aarch64_cortex-a53.ipk --> OK - netbird_0.39.2-r1_aarch64_cortex-a53.ipk --> KO
Author
Owner

@HaleTom commented on GitHub (Jun 27, 2025):

I had a very similar problem.

Service startup:

Jun 27 20:39:31 svelte systemd[1]: Started Netbird Service (main).
Jun 27 20:39:31 svelte netbird[452398]: 2025-06-27T20:39:31+07:00 INFO client/cmd/service_controller.go:25: starting Netbird service
Jun 27 20:39:31 svelte netbird[452398]: 2025-06-27T20:39:31+07:00 INFO client/cmd/service_controller.go:73: started daemon server: /var/run/netbird.sock
Jun 27 20:39:31 svelte netbird[452398]: 2025-06-27T20:39:31+07:00 INFO client/internal/connect.go:122: starting NetBird client version 0.49.0 on linux/amd64
Jun 27 20:39:31 svelte netbird[452398]: 2025-06-27T20:39:31+07:00 INFO util/net/env_linux.go:70: system supports advanced routing
Jun 27 20:39:32 svelte netbird[452398]: 2025-06-27T20:39:32+07:00 ERRO management/client/grpc.go:349: failed to login to Management Service: rpc error: code = PermissionDenied desc = peer login has expired, please log in once more

And when trying:

% netbird up
Please do the SSO login in your browser.
If your browser didn't open automatically, use this URL to log in:

https://login.netbird.io/authorize?audience=https%3A%2F%2Fapp.wiretrustee.com%2F&client_id=x3KvnKHEDY2j3b0n0wLq4eu8SiPDKq6o&code_challenge=X3rAk1N_LMJyZEh3M1opj
MdXaRtvQkaRKRmZ8giCvyA&code_challenge_method=S256&max_age=0&redirect_uri=http%3A%2F%2Flocalhost%3A53000%2F&response_type=code&scope=openid+profile+email+offline
_access+api+email_verified&state=b7bb35dcde1862b3869962601568dcbc75ef42f7e0c0f536

Error: waiting sso login failed with: rpc error: code = PermissionDenied desc = invalid user

Work around: delete: /etc/netbird/main.json

Perhaps there could be some output that directs people to this file, or the credentials within it?

@HaleTom commented on GitHub (Jun 27, 2025): I had a very similar problem. Service startup: ``` Jun 27 20:39:31 svelte systemd[1]: Started Netbird Service (main). Jun 27 20:39:31 svelte netbird[452398]: 2025-06-27T20:39:31+07:00 INFO client/cmd/service_controller.go:25: starting Netbird service Jun 27 20:39:31 svelte netbird[452398]: 2025-06-27T20:39:31+07:00 INFO client/cmd/service_controller.go:73: started daemon server: /var/run/netbird.sock Jun 27 20:39:31 svelte netbird[452398]: 2025-06-27T20:39:31+07:00 INFO client/internal/connect.go:122: starting NetBird client version 0.49.0 on linux/amd64 Jun 27 20:39:31 svelte netbird[452398]: 2025-06-27T20:39:31+07:00 INFO util/net/env_linux.go:70: system supports advanced routing Jun 27 20:39:32 svelte netbird[452398]: 2025-06-27T20:39:32+07:00 ERRO management/client/grpc.go:349: failed to login to Management Service: rpc error: code = PermissionDenied desc = peer login has expired, please log in once more ``` And when trying: ``` % netbird up Please do the SSO login in your browser. If your browser didn't open automatically, use this URL to log in: https://login.netbird.io/authorize?audience=https%3A%2F%2Fapp.wiretrustee.com%2F&client_id=x3KvnKHEDY2j3b0n0wLq4eu8SiPDKq6o&code_challenge=X3rAk1N_LMJyZEh3M1opj MdXaRtvQkaRKRmZ8giCvyA&code_challenge_method=S256&max_age=0&redirect_uri=http%3A%2F%2Flocalhost%3A53000%2F&response_type=code&scope=openid+profile+email+offline _access+api+email_verified&state=b7bb35dcde1862b3869962601568dcbc75ef42f7e0c0f536 Error: waiting sso login failed with: rpc error: code = PermissionDenied desc = invalid user ``` Work around: delete: `/etc/netbird/main.json` Perhaps there could be some output that directs people to this file, or the credentials within it?
Author
Owner

@nazarewk commented on GitHub (Jun 27, 2025):

@HaleTom it's described in https://docs.netbird.io/how-to/troubleshooting-client#client-login-failures

Perhaps there could be some output that directs people to this file, or the credentials within it?

Sounds like a good idea if it's possible to detect at all, I'll check in with the team.

@nazarewk commented on GitHub (Jun 27, 2025): @HaleTom it's described in https://docs.netbird.io/how-to/troubleshooting-client#client-login-failures > Perhaps there could be some output that directs people to this file, or the credentials within it? Sounds like a good idea if it's possible to detect at all, I'll check in with the team.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#404