Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am stuck in a situation which I cannot figure out. Here is my issue.

I got an SSL certificate from a trusted authority and installed it in my server. Then, I configured my website to use that certificate in port 443 with an IP address which is unused.

Then, I navigated to my web site to see if it works but I see that IIS gives the wrong certificate for this request. So, the browser blocks the response from being rendered.

I thought that IIS did something wrong while configuring and I checked the certificate mappings with the following command:

netsh http show sslcert

I get the Certificate Hash and run the following command to see if the certificate is the one that I need:

get-item cert:\LocalMachine\My\DC0D3FF5D752CD58FD291C48F30646FD9E0D8AED

It is indeed the one I needed. But, strangely I am still getting the wrong certificate when I navigate the web page.

Can u guide me where else I should look and what might be the cause of this?

share|improve this question
You should add your answer AS an answer, then you can accept it. That will be helpful to people who see this question in the future. – squillman Jun 6 '12 at 11:58
up vote 1 down vote accepted

It is so ironic that the answer popped up in my stupid head after I submitted this question. DNS Host A record was pointing to wrong IP address and that's why I was getting the wrong cert. Changed the IP address for the DNS Host A record and it is all working now.

share|improve this answer

Just to follow up on this for others that could not resolve it using the above solution, I had experienced a similar problem whereby the server was delivering the wrong certificate for HTTPS connections to a website with a host header value.

In my case, it turned out to be that the binding was set to receive connections from * instead of the actual server IP address. Modifying the binding to be bound to the IP address resolved the issue.

share|improve this answer
I noticed you said "with a host header value", what version of IIS are you using? – austinian Jul 20 '15 at 15:05
We're on IIS 8 on Windows Server 2012. – Martin Parkin Jul 20 '15 at 15:42
Ah, k. IIS 7.5 (what was asked about in the question) doesn't have support for host headers with SSL/TLS (SNI). Have you tried to serve multiple HTTPS sites from one IP on this server? – austinian Jul 20 '15 at 15:46
@austinian Indeed, that is exactly what we are doing currently. We have multiple certificates and multiple sites. One site in particular wasn't working but this was due to what I described above with the binding to * instead of a specific IP address. – Martin Parkin Jul 20 '15 at 15:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.