IIS 7 and Above
Assistance Installing a Wildcard Card
Last post Jul 24, 2013 01:39 PM by terri8502
Jul 22, 2013 01:46 PM|terri8502|LINK
I have one webserver (windows 2008, iis 7) running 2 separate sites, each with their own IP addresses. One site is currently using a certificate purchased for it, the other is using a wildcard cert (which we have just started using). I now want the original
site using the wildcard certificate also. Is this possible? Here is what happens
In the configuration for the site using the wildcard cert, I have the IP address selected, the wildcard cert selected, and the port as port 443.
In the configuration for the site I want to start using the wildcard cert on, I have tried these two things....
1. If I put in the IP address, I get a message that "the certificate associated with this binding is also assigned to antoher site's binding. Editing this binding will cause the HTTPS binding of the other site to be unusable. Do you still want to continue?
2. If I leave out the IP address and use "all unassigned" I get a message that "At least one other site is using the same HTTPS binding and the binding is configured with a differencdt certificate. Are you sure that you want to reuse this HTTPS binding and
resassign the other site or sites to use the new certificate?
I am not sure why I am getting message 2, the other site is using the same certificate as this one will be using, but I do not have a test area to try the change in and do not want to mess up my production site.
Any assistance is appreciated.
Jul 23, 2013 07:54 PMfirstname.lastname@example.org|LINK
Normally, one certificate, one site. You can use host headers with certificates in IIS7/8, which may solve your issue. See:
Jul 24, 2013 01:39 PM|terri8502|LINK
Thank you for your response. I have book marked the article you referenced because that information is going to be useful for another scenario I have on our intranet site, but the problem I was facing was two sites, two ip addresses, and the article was
for two sites, one ip address.
I suspect that the message I was getting was because we have the default website (even though we do not use it) using port 443 with "all unassigned" and the original certificate. This was an important piece of information I left out of the original post,
and I apologize for that. Once I thought about what the message was really telling me, I went and looked for the site using that port and certificate and found it. Since we don't use the default website, I never even looked at it. Bad me.
I gave my wildcard cert a friendly name (I had imported it without) and then made sure my binding on each site had the IP address (no "unassigned"), told IIS to make the changes when I received the error message, and moved forward.
Of course, before I made any changes I took one of our VM production servers off line and made a snapshot first.
Everything is now working. Thank you again for your response.