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

I have a windows 2008 server that I am running two websites on. I first setup both websites with normal HTTP access and was able to hit both sites. I now want to add HTTPS access, so I added it the Default Web site and then setup the first site successfully.

When I try to add HTTPS to the second site, the site automatically shuts down in IIS and when I try to start it, I get the error message:

This Web site cannot be started.  Another website may be using the same port.

Both sites are bound to the same IP address, but have different host name's.

Why is it that everything worked when there was only HTTP, but when I added HTTPS it started throwing an error?

What would be the proper way to configure HTTPS on two websites running on the same server?

share|improve this question
up vote 5 down vote accepted

Using Server Name Indication requires IIS 8.0. It was not supported in prior versions of IIS.

To resolve the problem, do one of the following:

  • Update to IIS 8.0 (and Server 2012).
  • Use a web server other than IIS.
  • Use unique IP addresses for each SSL-enabled web site.
share|improve this answer

In addition to what Michael Hampton said, another option if you're restricted to a single IP address is to bind additional sites to new ports. Not exactly an ideal situation, but it can get you by. To make it absolutely seamless you have to play games with URL rewrites. But if you can get along with having to specify the port number in the URL for the additional HTTPS sites it can work for you.

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.