I get the following error in Chrome:
ERR_SSL_PROTOCOL_ERROR when trying to connect to a client website.
This only happens in Chrome and for everyone.
The "website" is hosted in IIS and is just a web.config with a redirect to a site hosted elsewhere.
The certificate is installed into a custom certificate store (just a folder on another drive) which is mirrored on a second server. The IIS binding is correct, the HTTPS certificate is set to pull from the certificate store. The two web servers are mirroring correctly. This is a normal setup for many of our website for our client.
Originally I thought this problem was due to a missing SAN (the non www. domain) and asked the client to reissue the certificate with the added SAN hoping it'd fix.
Upon installation of the newly reissued certificate (with new valid from/to dates), I noticed that different SSL checkers would report the old certificate sometimes. Looking just now with FF dev tools, I can the non www. domain returning an the old certificate, where the www. domain returns the new certificate.
I am assuming Chrome detects this weirdness and just bottoms out, whereas the other browsers are happy, but it could be a red herring.
What's weird is, I purged the server of all the old certificates so I've no idea how they're being returned. The hosting provider is convinced it's not the load balancer.
Anyone have any idea?
