Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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'm having a strange issue with a website in IIS on Windows Server 2003. It has a valid wild card certificate on it, however when I use HTTPS on the page I get a 404 not found. Without HTTPS it shows up fine. Also, if I go to the domain root of the site using HTTP the homepage shows up, but with HTTPS it REDIRECTS ME to a totally different website installed on the same IIS server. I am quite confused. I tried giving each site a unique IP address but it didn't change anything, I also tried changing the SSL ports, no luck. This IIS is setup to run PHP also. What could I check to resolve this?

share|improve this question
up vote 2 down vote accepted

Usually what I do with SSL-enabled sites is assign them the required dedicated IP address, and then set all of the hostnames/domains to that IP. Within IIS, set the website entry to use that IP address only with no hostnames specified (and ensure the SSL port is bound to the same IP as well). Here's a screen capture for how the settings would look for IIS6:

SSL Settings

Usually if you have different results for non-SSL vs. SSL it means that the SSL entry for the IP address that the domain points to is bound to a different website entry within IIS. Double-check that the IP is assigned to the same entry in IIS all around.

share|improve this answer
yep this was it, thanks – ioSamurai Jun 7 '10 at 16:33

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.