Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems logging into netbird #14

Closed
Digital-Daz opened this issue Nov 13, 2024 · 2 comments
Closed

Problems logging into netbird #14

Digital-Daz opened this issue Nov 13, 2024 · 2 comments

Comments

@Digital-Daz
Copy link

Digital-Daz commented Nov 13, 2024

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.

@marcportabellaclotet-mt
Copy link
Contributor

marcportabellaclotet-mt commented Nov 13, 2024

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:

nginx.ingress.kubernetes.io/backend-protocol: GRPC
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
nginx.ingress.kubernetes.io/server-snippet: |
  grpc_connect_timeout 3600s;
  grpc_read_timeout 3600s;
  grpc_send_timeout 3600s;

@Digital-Daz
Copy link
Author

Thank you, I would just like to add that I have been monitoring and this does appear to have resolved my issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants