-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
kubernetes ingress-nginx 500 Internal Server Error #969
Comments
Ugh, it fixed by setting |
Glad you fixed it, but I'm not sure entirely why that helps? Seems that Nginx was maybe getting an invalid https response when trying to connect, was it actually going through the load balancer? What effect does the new annotation have? |
I guess It has something to do with the broken proxy protocol header and looks like this is the work around to fix the issue. I can also disable the proxy protocol setting which was enabled by default on them. |
You kind of saved me. I spent most of the day trying to debug this problem. I was adding annotation to the ingresses instead of the nginx-controller service. Ty! |
@atmosx adding the annotation to nginx-controller service (instead of ingress) in result disable authentification. |
Expected Behavior
Successfully running oauth2-proxy with ingress-nginx
Current Behavior
I'm running oauth2-proxy 6.1.1 & ingress-nginx 0.42.0 on DigitalOcean Kubernetes 1.19.3
Steps to Reproduce (for bugs)
oauth2-proxy is deployed with following config:
This is my Ingress config:
Currently Nginx is not passing any traffic to oauth2-proxy container.
Nginx logs:
SSL is terminated at DigitalOcean Load Balancer not on ingress-nginx.
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: