SelfSSL and multiple sites in IIS6?

SelfSSL and multiple sites in IIS6?

am 05.07.2006 10:59:02 von McZeb

Hi,
I've been using SelfSSL before to secure web sites in IIS 5 and 6 using
https, and it works fine. Now I want to secure two web sites on the same
server. Each site has it's own IP address, but I can't get both working at
the same time!(?). If I generate a cert for site 1, site 2 stops working with
SSL (https) and vice versa. I use port 443 for both sites, but with different
IP addresses, and I'm NOT using "Host Headers"! HTTP on port 80 allways works
fine for both sites at the same time!

What's missing?

BR, Björn

Re: SelfSSL and multiple sites in IIS6?

am 06.07.2006 02:40:17 von Ken Schaefer

There is a bug in SelfSSL :-(

You can setup Microsoft Certificate Services and issue multiple certs, or
use another tool to generate certificates.

Cheers
Ken

"McZeb" wrote in message
news:B2597B75-47AD-4874-BF4A-23679E61B0E9@microsoft.com...
> Hi,
> I've been using SelfSSL before to secure web sites in IIS 5 and 6 using
> https, and it works fine. Now I want to secure two web sites on the same
> server. Each site has it's own IP address, but I can't get both working at
> the same time!(?). If I generate a cert for site 1, site 2 stops working
> with
> SSL (https) and vice versa. I use port 443 for both sites, but with
> different
> IP addresses, and I'm NOT using "Host Headers"! HTTP on port 80 allways
> works
> fine for both sites at the same time!
>
> What's missing?
>
> BR, Björn

Re: SelfSSL and multiple sites in IIS6?

am 06.07.2006 11:01:03 von McZeb

Ken,
I solved the problem by installing a cert from our own CA instead!

How to implement SSL in IIS
http://support.microsoft.com/kb/299875/en-us

Thanks and hopefully this will help other people!

BR,
Björn

"Ken Schaefer" skrev:

> There is a bug in SelfSSL :-(
>
> You can setup Microsoft Certificate Services and issue multiple certs, or
> use another tool to generate certificates.
>
> Cheers
> Ken
>
> "McZeb" wrote in message
> news:B2597B75-47AD-4874-BF4A-23679E61B0E9@microsoft.com...
> > Hi,
> > I've been using SelfSSL before to secure web sites in IIS 5 and 6 using
> > https, and it works fine. Now I want to secure two web sites on the same
> > server. Each site has it's own IP address, but I can't get both working at
> > the same time!(?). If I generate a cert for site 1, site 2 stops working
> > with
> > SSL (https) and vice versa. I use port 443 for both sites, but with
> > different
> > IP addresses, and I'm NOT using "Host Headers"! HTTP on port 80 allways
> > works
> > fine for both sites at the same time!
> >
> > What's missing?
> >
> > BR, Björn
>
>
>

Re: SelfSSL and multiple sites in IIS6?

am 07.07.2006 00:54:14 von someone

The bug in SelfSSL is fixed and redistributed with SSLDiag 1.1.

http://blogs.msdn.com/david.wang/archive/2005/04/20/SelfSSL_ Bug_with_websites.aspx

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"McZeb" wrote in message
news:A7EFEB78-F349-4D19-B3BA-3529F65B1D20@microsoft.com...
> Ken,
> I solved the problem by installing a cert from our own CA instead!
>
> How to implement SSL in IIS
> http://support.microsoft.com/kb/299875/en-us
>
> Thanks and hopefully this will help other people!
>
> BR,
> Björn
>
> "Ken Schaefer" skrev:
>
>> There is a bug in SelfSSL :-(
>>
>> You can setup Microsoft Certificate Services and issue multiple certs, or
>> use another tool to generate certificates.
>>
>> Cheers
>> Ken
>>
>> "McZeb" wrote in message
>> news:B2597B75-47AD-4874-BF4A-23679E61B0E9@microsoft.com...
>> > Hi,
>> > I've been using SelfSSL before to secure web sites in IIS 5 and 6 using
>> > https, and it works fine. Now I want to secure two web sites on the
>> > same
>> > server. Each site has it's own IP address, but I can't get both working
>> > at
>> > the same time!(?). If I generate a cert for site 1, site 2 stops
>> > working
>> > with
>> > SSL (https) and vice versa. I use port 443 for both sites, but with
>> > different
>> > IP addresses, and I'm NOT using "Host Headers"! HTTP on port 80 allways
>> > works
>> > fine for both sites at the same time!
>> >
>> > What's missing?
>> >
>> > BR, Björn
>>
>>
>>