Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If users with IE8 go directly to, SSL cert is fine. Users going directly to have no issues with cert. If users start at one site and go to the other, they get invalid cert with xyz being used on zyx which should not be happening.

Reading the forums NGINX has SNI enabled and I have the correct version of OpenSSL to be able to handle multiple certs.

IE8 seems to be the issue but these are customer facing sites. Is there a fix to make NGINX work for the customers experiencing the issue.

share|improve this question
I bet you that all those users with problems have Windows XP. – Michael Hampton Dec 4 '12 at 22:39

SNI requires both server AND client (web browser + OS) support. For OSes/web browsers not supporting SNI, such as Windows XP or IE6, the browser will be ignoring the SNI SSL header and still request the default SSL certificate of the server which will most probably mismatch with the actual domain you are visiting.

To be able to support almost all popular platforms I would suggest obtaining an different IP for each one of the domains you need to supply with SSL support and configure nginx to listen on a separate address for each one of these domains.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.