-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
LibreSSL/3.3.6: error:1404B42E:SSL routines:ST_CONNECT:tlsv1 alert protocol version - protocol issue #11893
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Just checking the version of openssl
Can you output the nginx.conf and see how the directive for test.domain.com looks and what version of TLS is configured? https://kubernetes.github.io/ingress-nginx/troubleshooting/#check-the-nginx-configuration |
Sure @strongjz |
The information you providing is indicating only but not ample data for analyzing or reproducing problem in minikube or kind cluster. If you look at the template of a new bug report, and edit your issue description here, to answer all the questions asked in the template of a new bug report, then it provides data that can be analyzed. /kind support |
my issue was in the full values file (which not provided here), I've added:
which cause all https to use http port. |
Thanks for updating. Glad resolved. The static manifest published by project for termnating on LB is different from the manifest for terminating on controller. If you see the diff, those port related values are truly the significant ones. |
My stack is EKS (1.30) with ingress-nginx-controller (chart 4.11.1) and cert-manager (chart 1.15.3)
Expected:
I want to have web application (in my example small nginx container). To do so, I have subdomain for my domain in route53 direct to my NLB, the NLB have 2 listeners TCP:443 and TCP:80 which forward to my nginx ingress controller pods
I created a new ingress, and got certificate from my cert-manager, example:
Here is my nginx-ing-controller service annotation:
NGINX logs look like that:
When doing
curl
to my subdomain this is the result:from browser I'm getting:
Not sure how to debug this, and what to check next or why I'm getting this error. From the documenation I can understand NGINX use by default "tls1.2" or "tls1.3" so I'm not sure where am I failing.
The text was updated successfully, but these errors were encountered: