Certificate problem


We have a problem with certificates.On server (Win 2000 / IIS 5.0) that hosts 4 web sites, we have to install 2 certificates on two nondefault web sites with same IP address. There is no firewall and SSL ports are opened. On properties of both sites ->Directory Security tab ->Secure communication ->Edit, I checked option Require secure chanell and proceed in code redirection for http to https. When we try to open https:// site_address it displays Security alert and after that ‘The page cannot be displayed’. On Default web site we don’t have certificates.

Then, I try to install one of these certificates on Default Web site, and do redirection but I getThe page cannot be displayed
The page you are looking for cannot be displayed because the page address is incorrect.

In right corner I can see the padlock with valid certificate.

It seems that when he try to approach secure connection, first checks what is on Default Web site, and as on Default Web site there is no certificate, he gets error message.

On the other server, with only one Web Site it all works fine (same certificate install procedure is applied).

What we should do to make these certificates work?



For SSL, the requirement is one IP per SSL enabled domain.

So, if I understand what you are trying to do then you will need 2 IPs.
And each domain will have to be set to its specific IP, and not the ‘All Unassigned’ setting.

It might be possible for you to use Host Headers to do this using one IP, however we do not support that.



Thank you for advice.

Unfortunately, each site on server have the same IP address and I think that might be a problem. The sites are public and in use so I have to set certificate as soon as possible.
Could I use Host Headers, or something else? As I mention, on that server there is 4 web sites, but only 2 sites needs certificates.

I am really need help.



If you only have one IP then Host Headers is the only option I can think of.

However as previously mentioned, we cannot support the use of Host Headers as it is Microsofts implementation…any issues implementing it would have to be addressed by Microsoft.