Re: can't connect to SSL site

From: Jeff Cochran (jcochran.nospam_at_naplesgov.com)
Date: 02/27/04 

Date: Fri, 27 Feb 2004 20:50:32 GMT

On Fri, 27 Feb 2004 11:58:00 -0800, "John Smith"
<anonymous@discussions.microsoft.com> wrote:

>I have a web server with a default web site that works
>fine. I added a new site, same IP and different port (81).
>The second site works fine (http://domainname:81/directory)
>until I try to install SSL on the second site. I set up a
>certificate server, requested a server certificate on the
>second web site, installed it and when I "view
>certificate" everything's ok.
>
>As soon as I check "Require secure channel (SSL)", clients
>can't access the site from their browser.
>Am I missing something?

SSL needs a separate IP and not a different port.

Jeff

Relevant Pages

  • Re: Muliple Websites on Mutliple IP address with certicles [SSL]
    ... each has it's own certificate. ... Have you checked that the DNS for the second site is returning the correct ... and so you're connecting to the SSL ... port for both websites. ...
    (microsoft.public.inetserver.iis.security)
  • Multiple Site
    ... My administrator installed a certificate for SSL on the ... but now there we have a second site using ... port 81. ...
    (microsoft.public.inetserver.iis.security)
  • Problem with ejabberd and SSL on port 5223
    ... have used and install ssl based on the tutorial here ... encrypted connection using port 5223. ... % SSL-enabled client-2-server service ...
    (Debian-User)
  • Re: Multiple FTP sites problem
    ... Default FTP site, port 21, no user isolation, read + write. ... The second site returns an error when I ... but I'm guessing that your FTP client is running behind a NAT ... NAT routers at the client end cannot handle Active Mode FTP ...
    (microsoft.public.inetserver.iis.ftp)
  • Re: Error when creating a new web site with IIS
    ... These two lines show you having a web site already at 10.10.2.2 and ... then adding a second site at 10.10.2.2 without using host headers or ... You can't run two sites on the same IP and port ... without using host headers, so the second one can't start. ...
    (microsoft.public.inetserver.iis)