I recently upgraded my Nginx to version 4.13.0 after updating to 4.11.5 due to some CVEs, but now I'm facing a problem with all my application ingresses failing to work in the browser. They are showing a 'fake certificate' error even though they all have valid certificates and were functioning well under version 4.11.5. This is tested in my development environment. Has anyone else experienced this, and is there a solution? The discussions on GitHub haven't provided much help so far.
4 Answers
You should check the controller logs. They usually spell out what’s wrong. There was a recent change regarding server snippets; that might be causing your issues now.
Have you made any config changes when moving from 4.11 to 4.13? Running with verbose logging could help identify the issue.
Are your redirects set up properly? Also, check your logs. If you were using variables like `$redirect_url`, note that changes in version 4.12+ broke them due to a security fix, which might be why your ingress isn't deploying properly.
Definitely check the logs on the controller. I often face similar issues where it can’t find a certificate within my ingress namespace, which leads to it using a self-signed certificate, causing SSL problems.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures