Management Service login issue

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:

Install Netbird
sudo netbird up
restart machine
sudo netbird up
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

Thanks for help

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

For me, errors with the connection to Management Server start as soon as seconds after the registration as a peer. (see image attached)
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!

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

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).

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

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?

@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.

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?

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.

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:
@.***>

Same here with newest version:

Exactly same when --management-url provided

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

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 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.
2023-09-07T20:18:09+02:00 DEBG client/internal/login.go:93: connecting to the Management service https://api.wiretrustee.com:443 2023/09/07 20:18:09 INFO: [core] [Channel #1] Channel created 2023/09/07 20:18:09 INFO: [core] [Channel #1] original dial target is: "api.wiretrustee.com:443" 2023/09/07 20:18:09 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/07 20:18:09 INFO: [core] [Channel #1] fallback to scheme "passthrough" 2023/09/07 20:18:09 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/07 20:18:09 INFO: [core] [Channel #1] Channel authority set to "api.wiretrustee.com:443" 2023/09/07 20:18:09 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/07 20:18:09 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first" 2023/09/07 20:18:09 INFO: [core] [Channel #1 SubChannel #2] Subchannel created 2023/09/07 20:18:09 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING 2023/09/07 20:18:09 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2023/09/07 20:18:09 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.wiretrustee.com:443" to connect 2023/09/07 20:18:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000010018, {CONNECTING <nil>} 2023/09/07 20:18:09 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 on [::1]:53: read udp [::1]:46850->[::1]:53: read: connection refused" 2023/09/07 20:18:09 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 on [::1]:53: read udp [::1]:46850->[::1]:53: read: connection refused" 2023/09/07 20:18:09 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com on [::1]:53: read udp [::1]:46850->[::1]:53: read: connection refused" 2023/09/07 20:18:09 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000010018, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com on [::1]:53: read udp [::1]:46850->[::1]:53: read: connection refused"} 2023/09/07 20:18:09 INFO: [core] [Channel #1] Channel Connectivity change to TRANSIENT_FAILURE 2023/09/07 20:18:10 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to IDLE, last error: connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com on [::1]:53: read udp [::1]:46850->[::1]:53: read: connection refused" 2023/09/07 20:18:10 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000010018, {IDLE connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com on [::1]:53: read udp [::1]:46850->[::1]:53: read: connection refused"} 2023/09/07 20:18:10 INFO: [core] [Channel #1] Channel Connectivity change to IDLE 2023/09/07 20:18:10 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING 2023/09/07 20:18:10 INFO: [core] [Channel #1 SubChannel #2] Subchannel picks a new address "api.wiretrustee.com:443" to connect 2023/09/07 20:18:10 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000010018, {CONNECTING <nil>} 2023/09/07 20:18:10 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING 2023/09/07 20:18:10 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 on [::1]:53: read udp [::1]:44802->[::1]:53: read: connection refused" 2023/09/07 20:18:10 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 on [::1]:53: read udp [::1]:44802->[::1]:53: read: connection refused" 2023/09/07 20:18:10 INFO: [core] [Channel #1 SubChannel #2] Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com on [::1]:53: read udp [::1]:44802->[::1]:53: read: connection refused" 2023/09/07 20:18:10 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000010018, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing: dial tcp: lookup api.wiretrustee.com on [::1]:53: read udp [::1]:44802->[::1]:53: read: connection refused"} 2023/09/07 20:18:10 INFO: [core] [Channel #1] Channel Connectivity change to TRANSIENT_FAILURE

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?

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://hidden 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

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

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

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?

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

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

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

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 that's only accessible via the VPN causes this.

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

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.
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?

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.

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

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?

for nam

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.

Same for me on desktop with Ubuntu 22.04.4 LTS and the latest version 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 <IP_ADDRESS> but still no luck
Reboot made no difference

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
root@unknown:~# 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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 (<IP_ADDRESS>): 56 data bytes 64 bytes from <IP_ADDRESS>: seq=0 ttl=114 time=11.965 ms 64 bytes from <IP_ADDRESS>: seq=1 ttl=114 time=12.270 ms 64 bytes from <IP_ADDRESS>: seq=2 ttl=114 time=12.027 ms
cat /etc/resolv.conf search lan nameserver <IP_ADDRESS> 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?

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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 <IP_ADDRESS>: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 (<IP_ADDRESS>): 56 data bytes 64 bytes from <IP_ADDRESS>: seq=0 ttl=114 time=11.965 ms 64 bytes from <IP_ADDRESS>: seq=1 ttl=114 time=12.270 ms 64 bytes from <IP_ADDRESS>: seq=2 ttl=114 time=12.027 ms
cat /etc/resolv.conf search lan nameserver <IP_ADDRESS> 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.

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.

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.

@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

Having the same issue on Zorin OS 17.1

possibly related to #2116

I also see the error
Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
After setting OKTA as SSO provider (without OKTA it worked).
netbird version on the peer (which can't connect) - 0.28.9
OS: Linux my-host 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug  2 20:41:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 24.04.1 LTS
full output of the
bash -c 'GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info netbird up -F -l debug' :
https://gist.github.com/yakaviuk/b09ece635f2aea7b51f407c81c33c1e4
long story short:
2024/09/06 10:07:54 WARNING: [core] [Channel #1 SubChannel #2]grpc: addrConn.createTransport failed to connect to {Addr: "my.manager.url:443", ServerName: "my.manager.url:443", }. Err: connection error: desc = "error reading server preface: http2: frame too large"
2024/09/06 10:07:54 INFO: [core] [Channel #1 SubChannel #2]Subchannel Connectivity change to TRANSIENT_FAILURE, last error: connection error: desc = "error reading server preface: http2: frame too large"
2024/09/06 10:07:54 INFO: [core] [pick-first-lb 0xc000372660] Received SubConn state update: 0xc0003726f0, {ConnectivityState:TRANSIENT_FAILURE ConnectionError:connection error: desc = "error reading server preface: http2: frame too large"}
Is it issue on OKTA side?
Is it possible to connect peers using setup keys in case logging via OKTA is enabled?

Same issues on archlinux on a laptop:
Error: login backoff cycle failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded

Using official api

Was fixed with a reboot in my case...

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

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

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

Same Issue on AlmaLinux 9.5


[CSTOR] after reboot issue on node, some pods can't attach volume.

Hello, i get reboot issue on 1 of my CSTOR node, pods cant attach volumes.
I have cluster with 3 cstor nodes.
Was trying to restart pods:

cstor-disk-pool1
openebs-cstor-admission-server-588f985bc8-47gh5
openebs-cstor-csi-controller-0
openebs-ndm-6mp2k on node when pod trying to start
openebs-ndm-operator-69b5fcf66b-4brtn
openebs-cstor-csi-node-6zjk5 on node when pod trying to start
pvc-e91190f9-f453-475e-bb77-e886522b3070-target-7ff8b6fcf-dqcnv

DESCRIBE POD
kubectl -n infra-allure describe po allure-ee-rabbitmq-0
Events:
  Type     Reason       Age                 From     Message
  ----     ------       ----                ----     -------
  Warning  FailedMount  11m (x20 over 95m)  kubelet  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[config-volume healthchecks data kube-api-access-27rjp]: timed out waiting for the condition
  Warning  FailedMount  30s (x48 over 97m)  kubelet  MountVolume.MountDevice failed for volume "pvc-d4d4cdaa-59c2-447a-832a-78d2d92d43d4" : rpc error: code = Internal desc = format of disk "/dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2016-09.com.openebs.cstor:pvc-d4d4cdaa-59c2-447a-832a-78d2d92d43d4-lun-0" failed: type:("ext4") target:("/data/k8s/plugins/kubernetes.io/csi/cstor.csi.openebs.io/0cfa738b104e1ec933a3895c59a47ec21a281e5da84ba0bce1ffed425dc0b8a5/globalmount") options:("defaults") errcode:(exit status 1) output:(mke2fs 1.44.1 (24-Mar-2018)
Could not open /dev/disk/by-path/ip-<IP_ADDRESS>:3260-iscsi-iqn.2016-09.com.openebs.cstor:pvc-d4d4cdaa-59c2-447a-832a-78d2d92d43d4-lun-0: No such device or addres

POD
kubectl -n infra-allure get po allure-ee-rabbitmq-0
NAME                   READY   STATUS              RESTARTS   AGE
allure-ee-rabbitmq-0   0/1     ContainerCreating   0          96m

PVC
kubectl get pvc -n infra-allure
NAME                                  STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
data-allure-rabbitmq-0                Bound    pvc-e91190f9-f453-475e-bb77-e886522b3070   8Gi        RWO            cstor-csi-disk1   285d

CStorVolume
kubectl get CStorVolume -n openebs -l openebs.io/persistent-volume-claim=data-allure-rabbitmq-0
NAME                                       CAPACITY   STATUS    AGE
pvc-e91190f9-f453-475e-bb77-e886522b3070   8Gi        Healthy   285d

### CStorVolumeReplica

kubectl get CStorVolumeReplica -n openebs -l cstorvolume.openebs.io/name=pvc-e91190f9-f453-475e-bb77-e886522b3070
NAME                                                             ALLOCATED   USED    STATUS    AGE
pvc-e91190f9-f453-475e-bb77-e886522b3070-cstor-disk-pool1-9r9x   7.93M       21.9M   Healthy   285d
pvc-e91190f9-f453-475e-bb77-e886522b3070-cstor-disk-pool1-hzg5   7.93M       21.9M   Healthy   285d
pvc-e91190f9-f453-475e-bb77-e886522b3070-cstor-disk-pool1-z9bb   7.93M       21.9M   Healthy   285d

fixed, recreated

Hi @allanian, I'm facing a similar problem. Can you elaborate on what you did to fix this? What did you recreate and how? Thanks!

choyuansu i dropped cva on this node and moved my pod to another node, also you can try with
trying to remove pvc and recreating this, but be careful.


Example Configuration Profile Should Include additional details when setting IdPAttributeProfile = azure

It may be helpful to include additional information for setting the configuration to use:
IdPAttributeProfile = azure
In this case, the profile sets the NameIDFormat to persistent, among other settings and overrides any other specified attributes defined in the configuration file:
https://docs.rstudio.com/connect/admin/authentication/saml/#the-azure-profile
This becomes an issue if you want to create a user ahead of time using the RStudio Connect API and apply permissions prior to the user logging in the first time. The NameIDFormat should be set to emailAddress or some other unique identifier because when it's set to persistent, then the value gets hashed and you don't know what the value is ahead of time. So using the API will not work.
API for creating user for SAML: https://docs.rstudio.com/connect/api/#post-/v1/users
So you may want to have this in your configuration file in this situation:
[SAML]
NameIDFormat = emailAddress
UniqueIdAttribute = NameID
UsernameAttribute = http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
FirstNameAttribute = http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
LastNameAttribute = http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname
EmailAttribute = http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailAddress

More details on the NameIDFormat configuration in RStudio Connect and how it works: https://docs.rstudio.com/connect/admin/authentication/saml/#name-id-format

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e7bcbffe-af83-cd84-294e-bd07c7e4e8d8
Version Independent ID: 719c2b9b-dcf8-25a7-82fa-9ca7522b016a
Content: Tutorial: Azure AD SSO integration with RStudio Connect SAML Authentication
Content Source: articles/active-directory/saas-apps/rstudio-connect-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@dareneiri
I have assigned the issue to the content author for further review.

Updating the document as suggested.
#please-close


Sidebar not responding

The sidebar isn't responsive. I've inspected the elements in the browser's console and noticed that the media queries for different screen sizes for the sidebar isn't working. Upon inspection of the dist/ file after the npm install, the media queries seem about correct in its setup. Am I missing something?

Sorry for the really late response!  You are correct, we never got around to implementing the hamburger menu after a certain screen size (or hiding the desktop menu).
We haven't been maintaining this in the last year but if anyone wants to make a pull request to add the hamburger menu for small screen sizes, I'm happy to merge that in.


filter for pages only

Hi,
I think there is a need for regex filter for url before a filter is executed...
it seems to apply header for static files as well such as images and css and js

Is this for static, or dynamic ??

I think it will be nice that we can set filter for both, but I'm actually
talking about filter for csrf that will only applies to HTML format or non
static paths
On May 20, 2016 8:33 AM, "Pete Morgan"<EMAIL_ADDRESS>wrote:

Is this for static, or dynamic ??
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/revel/revel/issues/1046#issuecomment-220488565

it seems to apply header for static files as well such as images and css and js

That's due to the fact that in Revel static assets are served using Serve action. So, there is no difference between static files and dynamic actions, actions take part in both cases.
When implementing CSRF protection you can check whether current c.Controller.Action to make sure it is not equal to Static.Serve. Though, this feels kind of hacky.

Yes I added my work around aka the manual if before running filter. Would
be nice if we have option to pass in file extension. But this will need the
.ext in route to work as well
On May 20, 2016 1:34 PM, "alkchr"<EMAIL_ADDRESS>wrote:

it seems to apply header for static files as well such as images and css
and js
That's due to the fact that in Revel static assets are served using Serve
action
https://github.com/revel/modules/blob/master/static/app/controllers/static.go#L45-L53.
So, there is no difference between static files and dynamic actions,
actions take part in both cases.
When implementing CSRF protection you can check whether current
c.Controller.Action to make sure it is not equal to Static.Serve. Though,
this feels kind of hacky.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/revel/revel/issues/1046#issuecomment-220521069

You can use FilterConfigurator to change the chain of filters for an action. For example
 FilterAction(Serve.Static).Remove(SessionFilter)


Add DuelEvent

PR related to issue described in #135
Added DuelEvent for:
•	StatsBomb, Opta & WyScout (v2 & v3); including tests
•	Added DuelTypes: AERIAL, GROUND, LOOSE_BALL & SLIDING_TACKLE
•	Added .get_qualifier_values() to get a list of qualifiers instead of the first value.
@probberechts  can you take a look, whether this suffices?

Thanks for this pull request!
Some minor comments and can you make sure to merge master in as there seem to be some conflicts.

@koenvo should be good to merge.


Steve reviews Rust by Example.

r? @rust-highfive
(rust_highfive has picked a reviewer for you, use r? to override)

Wooo


[BISERVER-14720] Upgrade log4j2

:x: Build failed in 1m 6s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
assemblies/core/lib,assemblies/core/static,assemblies/lib,assemblies/static,core,engine,plugins,plugins/pur/core

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message

:x: Build failed in 3h 17m
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
assemblies/core/lib,assemblies/core/static,assemblies/lib,assemblies/static,core,engine,plugins,plugins/pur/core

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message


insert examples directly (without lay-by) when you know where

e.g. when there is only a single sense and the example container is underneath

We'll have a look at this in new editor


Add basic scaffolding for QGB module

Description
Adds basic scaffolding for the QGB module.
closes https://github.com/celestiaorg/celestia-app/issues/197

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

@evan-forbes Please take a look when you have time

@evan-forbes if we need to include: https://github.com/celestiaorg/celestia-app/issues/199 also in this PR. Then, I can turn it into draft to add that stuff

@evan-forbes if we need to include: https://github.com/celestiaorg/celestia-app/issues/199 also in this PR. Then, I can turn it into draft to add that stuff

no that was my mistake, we shouldn't attempt to finish that in this PR. This PR introduces the DataCommitmentConfirm msg, which confused me briefly. #199 just needs to be clarified.

@evan-forbes For the DataCommitmnetConfirm, it only contains a dummy field... I can remove it from this PR, then introduce it in the next https://github.com/celestiaorg/celestia-app/issues/199 one. What do you think ?

sounds good!

@evan-forbes Can you take a look now please. Removed the dummy field from DataCommitment

@evan-forbes Should we merge this one, then add the remaining logic in the next PR ?

@evan-forbes Should we merge this one, then add the remaining logic in the next PR ?

yep! I think so


less-475 upstream sha256 change

I'm getting a

should have sha256 hash ‘1w7d10h6hzgz5zww8g4aja2fbl7xwx30vd07hcg1fcy7hm8yc1q2’, instead has ‘16703m6g5l97af3jwpypgac7gpmh3yjkdpqygf5a2scfip0hxm2g’

for the upstream "http://www.greenwoodsoftware.com/less/less-475.tar.gz".
This agrees with what I see if I manually download the file
$ wget -d http://www.greenwoodsoftware.com/less/less-475.tar.gz
$ nix-hash --flat --type sha256 --base32 less-475.tar.gz
16703m6g5l97af3jwpypgac7gpmh3yjkdpqygf5a2scfip0hxm2g

Not sure what has changed as I don't have the original.  Maybe 475 isn't a stable release point as it isn't actually listed on their download page (the last one listed is 471)?  I guess they could also have got hacked...?

Perhaps email upstream and ask them whether it changed (and ask them to avoid changing it if it was intentional)?

Bah, didn't notice this issue before opening https://github.com/NixOS/nixpkgs/pull/7721. Anyway, I worked out the diff in that PR. Maybe we should indeed revert to an earlier less release if these aren't supposed to be stable releases.

I sent an email and received the following response back yesterday from Mark

Yes, that was due to a procedural error on my part.  No hacking involved.  But I didn't think it would matter to anyone since less-475 hasn't been announced yet."

That agrees well with the diff dezgeg provided in #7721.
Cheers!  -Tyson

Ah, thanks for looking into this!

BTW, I got the 475 release from monitor.nixos.org, which in turn got it from Gentoo.

Fixed via 901849ec


Bring plugin back online

Relates to https://github.com/hypothesis/product-backlog/issues/1527

This is the reason the plugin was closed, and the steps to follow to bring it back:
Reason

The email associated with the plugins owner's user account bounced. As such, all plugins associated with the account were closed, because we do require your email to be functional.

What to do next

Make sure the email on the user account is valid
If the email is a group mail or mailing list, make sure it can receive email from external domains or non-members (Google changed their defaults in 2019 due to GDPR laws)
If the email forwards, check all addresses to make sure they're valid and do not forward bounces
If the ownership of the plugin is in doubt, let us know what accounts are supposed to have access and be the official owners so we can transfer them appropriately
You must update the plugin readme to confirm it is compatible with the current release of WordPress. This is to ensure people can actually find your plugin.
Perform a full security and guideline check of your own work. Look for sanitization, remote loading of content, and any other minor bug.
Update all the code and upload it to SVN.
Reply to this email that you are ready for a review

Thanks for your work in reviving this @acelaya. We require the hypothesis WordPress plugin in our bedrocks at Pressbooks. Because the plugin was deactivated at WordPress at org, the mirror at wpackagist has been closed and it's not picking up your latest releases: https://wpackagist.org/search?q=hypothesis&type=any&search=

I'm hopeful that reactivating the plugin on WordPress.org will be enough to get the mirror back up and working. In the meantime, however, would you have any interest in registering the plugin directly with packagist.org? The process is pretty simple and the GitHub repo already has the required composer.json file. See "Publishing Packages" instructions here: https://packagist.org/. That would allow us to simply run composer require hypothesis/hypothesis to manage the plugin as a dependency, indepedently of whether or not the wordpress.org listing is active and the wpackagist service is mirroring all tagged releases.

In the meantime, however, would you have any interest in registering the plugin directly with packagist.org

This definitely makes sense. People managing their WordPress installations/deployments with composer would definitely benefit from it. I'll try to get it published there today.
Although, now that I look at the package name, it probably needs to be renamed to hypothesis/hypothesis-wp-plugin or something in those lines. The hypothesis/hypothesis name is too "top level", so to speak, and might be needed for other packages eventually.

@SteelWagstaff you can find the plugin in packagist now with the package name hypothesis/wp-hypothesis

Amazing -- thanks!

The plugin has been enabled again by the plugins team. I have also requested the previous owner to transfer ownership to us.

Confirming wpackagist has started to pick up the new updates now that the plugin is listed again