-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[nginx] default cert not served in absence of servername (since beta.4+) #693
Comments
@donaldguy Can you please cat the /etc/nginx/nginx.conf generated by the ingress-controller and send here or in a gist? Thanks. |
It's pretty much what you'd expect: https://gist.github.com/donaldguy/d56fa2a5d16195cec840f9e80ec7a198 |
Yup, it seems there is no 443 port listening in this. @aledbf Don't know were this happens, maybe in this SSL Passthrough refactor. |
additionally I can confirm that
|
Yeap, it seems that in the config the 443 port is not being openned. Need to check this. |
I'd put decent odds that the site of the bug is here: https://github.com/kubernetes/ingress/blame/nginx-0.9.0-beta.5/controllers/nginx/pkg/cmd/controller/tcp.go#L49-L60 |
In particular it would appear that p.Default is always nil |
Hum. Don't know when this was inserted in the code and why is there. Anyway I use a modified nginx.tmpl that uses SSL directly (as my traffic is only HTTP/s). But will check this ASAP to see what and when happens. I suggest you doing a modification in this part of the code, to see if this solves. If that's the case, open a PR :) Thanks! |
[nginx] pass non-SNI TLS hello to default backend, Fixes #693
Presumably the result of #614, it is now the case that SNI must be used by a client to complete a TLS handshake even when the servername is ignored on the server side
While I first encountered in production with a valid star cert, I have successfully reproduced in minikube as follows:
I have verified this happens in production with both beta 4 and beta 5. Reverting to beta 3 seems to work.
The text was updated successfully, but these errors were encountered: