![]() So it is clearly some sort of cache thing. One interesting note: When hitting the page from a incognito session ( Ctrl+ Shift+ N), it works correctly. This site works in all other browsers on my machine so it’s just a Chrome problem. My guess is that Chrome cached the key for the self-signed cert and it doesn’t match that of the legitimate cert. When I hit the site from my machine in Chrome it throws the following error: Now I have installed the legitimate cert on that server. During testing, I created a self-signed cert on this server and hit it from my desktop using Chrome to test that stunnel was working correctly. ![]() I have a HAProxy / stunnel server that handles SSL for our sites on AWS.
0 Comments
Leave a Reply. |