Presumably the cached cert expired or something, but I am still interested to know where this information is stored and how to verify it. I still don’t know what caused it or how it resolved itself. UPDATE: It seems to have “fixed itself” today. On the Google Chrome Help Form, there is a description of what sounds like the same issue however, no resolution is found. I did all the things I could think of (dumped my cache, deleted certs from the Personal and Other People page in the Manage Certificates dialog, Ctrl+ F5, etc.). So it is clearly some sort of cache thing. NewPowerGear 8 Inch Chrome Burner Drip Pan Bowl Replacement For WB32X5063 WB32X5049. One interesting note: When hitting the page from a incognito session ( Ctrl+ Shift+ N), it works correctly. Spektrum S901 DB XL Servos: Toys & Games. 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. (net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH): 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |