-
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
How to use SSL passthrough in nginx ingress controller without changing the listening port 443 #12262
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. |
@longwuyuan: Closing this issue. In response to this:
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. |
`Change background: How it works usually : TLS termination is handled at the APIM custom domain. Flow is Client device -> APIM DNS ( Cloud Flare ) -> APIM New dual stack setup: apiVersion: networking.k8s.io/v1 - APIM-endpoint.comsecretName: tls-secret-apim-sectigoingressClassName: nginx Backend APIM Here is my nginx.conf Configuration checksum: 15284697795965044210setup custom paths that do not require root accesspid /tmp/nginx/nginx.pid; daemon off; worker_processes 2; worker_rlimit_nofile 1047552; worker_shutdown_timeout 240s ; events { } http {
} stream {
} Before it throws a 403 Invalid client certificates I am getting below error now, After adding SSL passthrough I see this error, curl -4 -k -v --tlsv1.2 --location --request POST 'https://APIM-endpoint.com/api/v2/handshake?' --cert cert.pem --key cert.key --header "Content-Length: 0"
|
pls help on this |
@kmarimuthu90 its unfortunate that you are facing problems to use ssl-passthrough feature. I hope it can be solved soon.
So I suggest that
This will help readers a lot. There are not many resources here as its a community project so you can help others to help you, if you consider the suggestions above Once you have provided all the answers to the questions asked in the bug report template, then you can reopen this issue. |
ok thanks |
etc/nginx $ netstat -nlp I see 442 only listening |
No description provided.
The text was updated successfully, but these errors were encountered: