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
Netbird behind nginx: stream terminated by RST_STREAM #651
Comments
This issue is caused by grpc and its native keepalive not being supported by revere-proxy. We are implementing a application keepalive tin #771 |
Just for reference: Found this: camunda-community-hub/zeebe-client-node-js#101 |
@ykorzikowski, we notice that running Nginx v1.25.1 solved the issue. Can you test it? |
Hellooo, I dont know. What helped is setting I am still using |
Hello, I'm trying to deploy the netbird management into my k8s cluster v.1.25.12 with the nginx ingress controller 1.19.10 Have specified the annotations in the netbird management and netbird signal ingresses:
Peers are registered and the netbird client connected but vpn doesn't work:
How should I additionally configure my nginx ingress controller and\or ingress resources to solve this issue? PS. I can't add additionaly:
|
Any news? |
Can you post some nginx access / error logs? Maybe this is some ingress configuration issue and noting regarding netbird. |
Nginx ingress controllers' logs don't contain any error:
|
Any news? |
Hey there,
I am successfully running netbird since couple of months. Some clients cant speak with each other. I am investigating this issue right now and found, that I have errors regarding the signal-service in my client-logs (all clients, also the working ones):
Is there a recommendation how to run the netbird service? Like my config or everythin on port 443 like #536 ?
Thank you for any help :)
The text was updated successfully, but these errors were encountered: