RE: HTTPS setup

I encountered a problem setting up multiple secure sites on the same server using host headers. If your sites currently all share the same IP address, you can't set them all up on port 443. The two solutions that I found were: 1. Set up each site on a separate port. 2. Give each site it's own IP

RE: HTTPS setup

> The key's all set up properly, but it just finds nothing if you > browse to it... > we've set the SSL port to be 443 in IIS, so it should know it > exists. We've also > set the IP and headers with that port. > > We're definitely using the URL the key was registered for. > > Any ideas? You aren'

Re: HTTPS setup

Thanks for the quick replies from Bob and yourself... even if I didn't get back to it until now because of my mail backlog... ;) We do have other sites on the same IP, but none of them use SSL. That shouldn't matter, should it? The default site if you go in by IP is a different site, but that's o

RE: HTTPS setup

> We do have other sites on the same IP, but none of them use SSL. > That shouldn't > matter, should it? The default site if you go in by IP is a > different site, but > that's only for port 80, so I guess its irrelevant. Is it possible for you to try making the SSL site the one with no host head

RE: HTTPS setup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > We do have other sites on the same IP, but none of them use SSL. > > That shouldn't > > matter, should it? The default site if you go in by IP is a > > different site, but > > that's only for port 80, so I guess its irrelevant. > > Is it possible

RE: HTTPS setup

Or its own port. -Original Message- From: Zachary Bedell [mailto:[EMAIL PROTECTED]] Sent: January 11, 2001 5:28 PM To: CF-Talk Subject: RE: HTTPS setup -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > We do have other sites on the same IP, but none of them use SSL. > > Th