Multiple SSL sites using wildcard certificate

1.Please open properties for each virtual web server, go to WebSite tab,
click "Advanced" button next to IP address and make sure that each web
site has an unique binding for SSL port (443).

2. MAy be your IIS run multiple website in the same port so you are getting this error so check these

https://www.experts-exchange.com/questions/20867595/Can't-Start-Second-Web-Site-in-IIS-6-0-Duplicate-Port.html

Wont changing my ssl port setting cause problems for people trying to access my site when they enter in xxx.mydomain.com?

Hi,

Ok then binding port 443 for site .

Anyway - I tested this years ago. what you can do is:
-setup each site with the same ip/port + different host header xxx.mydomain.com,
yyy.mydomain.com, etc
-make sure cert is associate with each site
-make sure port 443 is assign in each site
-do a netstat -ano, and make sure port 443 is binding to the IP.

http://chris-linfoot.net/d6plinks/CWLT-6MREJL
http://www.microsoft.com/technet/prodtechnol/isa/2004/maintain/wildcard.mspx

When you say same ip/port are you referring to the ipaddress under the web site tab?

When I specify the ip address I still get the same error.

Hi,

Yes... If you use the same ip and port then binding that port .However, the stuff doesn`t work on single ip/port combination. it would load one site`s content only. here`s a good explanation of the process
---------------------------------------------------------
Here's a quick description, to demonstrate why:

1. The client takes the URL and resolves the name into an IP address, and a port (usually a default port).
2. The client connects to that IP address, on the requested port
3. The server running at that IP address and port answers.
4. The client sends a "hello" message, asking the server to send its certificate.
5. The server sends the certificate to the client.
6. The client checks the name in the certificate against the name it had in step 1.
7.1. If the certificate matches, the client and server start encrypted exchanges.
7.2. If the certificate doesn't match, the client displays an error to the user and stops.

8. The client sends HTTP request headers, encrypted, to the server.
9. The server sends back HTTP responses, encrypted, containing content requested.

Note that host headers are sent in step 8, but the server has to pick a certificate to send in step 5, and that certificate must have the server name that the user asked for.  The server has no clue as to which
certificate it must pick, so it must have a single certificate to send back on that IP address and port.

There is work under way to produce a "next version" of TLS, that will allow a client to send the host name it wants in step 4, so that the server can choose among several certificates, but it is not clear exactly when (if
ever) this will be implemented in browsers or web servers - and it has to be implemented, and enabled, in both if it is to work.


http://www.instantssl.com/ssl-certificate-products/ssl/wildcard-ssl-p...

http://groups.google.co.in/group/microsoft.public.inetserver.iis.security/browse_thread/thread/390923dded889258/9438d4f0e8ac3441?lnk=st&q=wildcard+ssl+configuration&rnum=3&hl=en#9438d4f0e8ac3441

Thanks for all the help.  I found that the cause of my problem was the default website.  Once I deleted it and recreated my websites the adustil worked and I was able to apply my wildcard ssl to all the site.