How to fix the TLS Server Name Indication issue under Windows XP on Nginx using a different IP

Question

I have a server that is using two different domains with two different certificates. Everithing work fine except IE8 on Windows XP because the TLS Server Name Indication is not supported there. In order to fix this problem I want buy a dedicated IP for the second domain and set this IP on the nginx listen configuaration file.

The question is, it is possible set a dedicate IP on the listen nginx parameter?

If you have only a couple of sites sharing an IP, you could just buy a certificate with multiple alternative names. This works correctly on XP with IE. — Hubert Kario, Nov 14 '12 at 01:34
I need a wildcard for one domain plus 2 subdomain for the other domain — Marco C, Nov 14 '12 at 01:45
Setting the dns and the ip on the listen parameter the server is not responding — Marco C, Nov 14 '12 at 04:25

score 0 · Accepted Answer · answered Sep 30 '13 at 05:08

0

Setting a different IP on each domain fix the problem.

answered Sep 30 '13 at 05:08

Marco C

153
9

Isn't setting up a different IP for each domain exactly what SNI exists to help avoid having to do? – ngl817 May 21 '14 at 13:46
Yes, but it has limited browser support: http://nginx.org/en/docs/http/configuring_https_servers.html#sni – Marco C May 22 '14 at 03:40

How to fix the TLS Server Name Indication issue under Windows XP on Nginx using a different IP

1 Answers1