-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Can't get Kong 0.14.0 to serve my certificates on HTTPS #3721
Comments
How did you add the certificate(s) to Kong? |
Hi,
Thanks for replying,
I added certificates just like any other object, via kong admin api.
|
Right... but did you use a JSON file with the |
yes, I did a POST request with body like:
|
adding my kong configurations:
|
Did your certificate contain |
If using JSON, the certificate and key objects should use |
NICE ! Thanks allot ! |
No problem. Kong should do a better job of validating body content. |
I am having the same symptoms as the original issue here. My certificates are being loaded properly (I think), and yet kong isn't picking them up. When it returns the created or updated response, I see the line breaks are I used to add these certificates in 0.13.x like this:
But if I do that now, it returns a "missing key" error. If I use |
I forgot to mention the way I am doing it now:
|
Never mind, turns out I was generating the certs improperly. Thanks! |
Thanks @benjaminprojas, you save my day 💯 |
I feel like this is resolved now. Btw. the |
that is a so big trap |
Thank you! This is the only way that worked after an hour of trying. |
Summary
After configuring Certs with SNIs Kong route is ignoring the configuration and serves localhost cert (default)
Steps To Reproduce
Expected result
Kong will serve the certificate that it's SNI fits the Host of the Route.
Additional Details & Logs
setup is on kubernetes with postgres DB.
HTTP access is good- I get response as expected.
my Service object:
my Route object:
my SNI object:
The text was updated successfully, but these errors were encountered: