Why is site serving different SSL certs to different browsers? [closed]

Solution 1:

So it turns out that in Plesk 11.0 it isn't enough to assign an SSL cert with a website on a dedicated IP address. You also have to go to the list of IP addresses (Server Management > Tools and Settings > Tools & Resources > IP Addresses) and set the "Default site" for each IP address to be the site on that address.

If you don't do that, Plesk serves the cert in a manner which requires SNI, which rather obviates the benefits of putting each secured site on a dedicated IP address in the first place.

You can also set the SSL cert there, but that is unnecessary. This seems to be more confusing than necessary.

Solution 2:

When I accessed the website https://www.menswearireland.com from my company LAN (firewall proxy and all) I got an SSL error:

VERIFY DENY: depth=0, (18) self signed certificate: "Parallels Panel"
VERIFY DENY: depth=0, CommonName "Parallels Panel" does not match         
URL "www.menswearireland.com"

This would mean that the certificate is apparently a self-signed certificate and that's a big NO GO for Internet Explorer.

Solution 3:

I know that this is an old thread, but it helped me solve a similar issue. I determined it to be IPv6 related as opposed to SNI. It turns out that Verizon Wireless and other ISPs are increasingly using IPv6 instead of IPv4. It was a frustrating issue because the only commonality that I could come up with was that the majority of my customers that were having the issue were using Verizon, but not all Verizon LTE connections use IPv6 so some worked correctly. In my case, I needed to assign the certificate to the IPv6 address on my Plesk Server as well as the IPv4 address and the problem was solved.