You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every so often I get an error when trying to reauthenticate to netbird.
In the logs I see this kind of thing:
ERRO management/client/grpc.go:278: failed while getting Management Service public key: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); transport: received unexpected content-type "text/html"
2024-11-13T16:18:02Z ERRO client/internal/login.go:105: failed while getting Management Service public key: failed while getting Management Service public key
2024-11-13T16:18:02Z ERRO client/server/server.go:277: failed login: failed while getting Management Service public key
After a short time, logging in again is successful.
The issue is likely on the Netbird side. I’ve added an option to enable the backward-compatible gRPC management port. To use this, upgrade to chart version v1.5.3 or higher and set the following:
management:
useBackwardsGrpcService: true
This will create a dedicated service for the management gRPC, and the management grpc ingress will be configured to point to it.
Also ensure that you use these or similar annotations in your grpc ingress:
Every so often I get an error when trying to reauthenticate to netbird.
In the logs I see this kind of thing:
ERRO management/client/grpc.go:278: failed while getting Management Service public key: rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); transport: received unexpected content-type "text/html"
2024-11-13T16:18:02Z ERRO client/internal/login.go:105: failed while getting Management Service public key: failed while getting Management Service public key
2024-11-13T16:18:02Z ERRO client/server/server.go:277: failed login: failed while getting Management Service public key
After a short time, logging in again is successful.
The only thing I have managed to find when googling this is: kubernetes/ingress-nginx#4836
I'm not sure if that is completely irrelevant.
The text was updated successfully, but these errors were encountered: