Link to home
Start Free TrialLog in
Avatar of ncomper
ncomper

asked on

IIS Multiple Secure Site setup

Afternoon All,
      I have a client with a Server 2008 machine running IIS 7, this server is running 15-20 Secure webpages all running from a single SSL certificate (covering the multiple domains) We had a request to add a new domain to this server with the following secure.<newdomain>.com. we have had the certificate updated and the new SSL installed. We created the new site on Port 80 and this will start no problem. When adding the SSL 443 port to the domain we are no longer able to start the site, (we are also not able to add a host header to the 443 host binding....

We get the error: This Website cannot be started. Another Web Site may be Using the Same port.

A NETSTAT is showing that we have ~ 4 sites running on two different external addresses XX.XX.XX.91 and XX.XX.XX.81

I am not a Web/IIS Guy so please do not assume i have complete any previous steps correct to begin with,

Many thanks
Avatar of becraig
becraig
Flag of United States of America image

Try the following command for the new site:

appcmd set site /site.name:"<newdomain>.com" /+bindings.[protocol='https',bindingInformation='*:443:<newdomain>.com']
Avatar of ncomper
ncomper

ASKER

Can i run that from the Cmd Line or will this need to be via Powershell?

Many thanks
you can run it from the command line just find the path where appcmd resides.
Avatar of ncomper

ASKER

Ok, i ran the command but this took down an existing site on the xx.xx.xx.91 IP address.
Can you run the following from powershell it seems there might be a duiplicated ip/port combination.

Import-Module webadministration
gci IIS:\SslBindings\


You can redact your ips in the output.
Avatar of ncomper

ASKER

Thanks for the response, i am getting a few issues when running the script (can not accept argument 'gci') but what i am able to obtain is the following

IP Address       Port Store
----------       ---- -----
192.168.200.81   443  MY
192.168.200.91   443  MY
192.168.200.92   443  MY
192.168.200.93   443  MY

From a Netstat :443
C:\Users\administrator.WEBSERVER>netstat -aon | find ":443"
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING       4
  TCP    192.168.200.81:443     201.XXX.XXX.XXX:27611  ESTABLISHED     4
  TCP    192.168.200.81:443     201.XXX.XXX.XXX:27612  ESTABLISHED     4
  TCP    192.168.200.81:443     201.XXX.XXX.XXX:27648  ESTABLISHED     4
  TCP    192.168.200.81:443     201.XXX.XXX.XXX:27665  ESTABLISHED     4
  TCP    192.168.200.81:443     201.XXX.XXX.XXX:27666  ESTABLISHED     4
  TCP    192.168.200.81:443     201.XXX.XXX.XXX:27667  ESTABLISHED     4
  TCP    192.168.200.81:443     201.XXX.XXX.XXX:27684  ESTABLISHED     4
  TCP    192.168.200.91:443     81.XXX.XXX.XXX:61680       ESTABLISHED     4
  TCP    192.168.200.91:443     209.XXX.XXX.XXX:11886  ESTABLISHED     4
  TCP    192.168.200.91:443     209.XXX.XXX.XXX:21669  ESTABLISHED     4
  TCP    192.168.200.91:443     209.XXX.XXX.XXX:26060  ESTABLISHED     4
  TCP    192.168.200.91:443     209.XXX.XXX.XXX:30710  ESTABLISHED     4
  TCP    [::]:443               [::]:0                 LISTENING       4

Is this supplying any beneficial information?
ASKER CERTIFIED SOLUTION
Avatar of becraig
becraig
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ncomper

ASKER

Thanks