Assiging IIS Express SSL Certificate to a stie disconneted the rest of my IIS sites certificates

Question

I'm hosting a couple of sites on IIS 8.5 (Windows server 2012-R2). These https sites are bound using a UCC SSL certificate from GoDaddy.

I created a new site on IIS and added binding using the "IIS Express SSL Certificate". This caused the rest of my sites to stop responding to https requests. I had to reassign the UCC SSL so my sites could work with HTTPS again, but I was wondering if anyone knows why this happens. Having these things happening in a production server is a nightmare so I was wondering if anyone could shed some light on this matter.

Answer 1

This usually happens when you use the same IP or port with all the HTTPS sites. if you want to use the same binding with the different hostname you could use the SNI(Server Name Indication).

Server Name Indication (SNI), which is a TLS extension to include a virtual domain as a part of SSL negotiation. What this effectively means is that the virtual domain name, or a hostname, can now be used to identify the network endpoint. In addition, a highly scalable web hosting store has been created to complement SNI. The result is that the secure site density is much higher on Windows Server 2012 and it is achieved with just one IP address. It should be noted that in order for this feature to be used, your client browsers have to support SNI. Most modern browsers support SNI; however, Internet Explorer (of any version) on Windows XP does not support SNI.

When you assign the https binding to the site you just need to check the Require Server Name Indication checkbox.