0

So We have noticed a weird issue happening in our (soon to be production) network.

We have 3 IIS Servers, using shared configuration and using Centralized Certificates. Each site has up to 6 bindings (3 for non www for each of the hosts, 3 for www for each of the hosts) Sample IIS Binding Each of the SSL Binding's are configured like this IIS Binding

When we go to the non www version of the site the SSL certificate is picked up fine, however when we go to the www version a mismatch is thrown and it tries to use the hosts wildcard certificate. If I disable centralized certificates, install the cert on the host and set it in the IIS binding for the WWW entries everything works..

Kind of stumped on this one

  • Since you have 6 bindings, you need six certificate files matching the host names in Centralized Certificate Store. Do you have only three at this moment? – Lex Li May 12 '18 at 1:34
  • So for example than, a certificate file must match the binding name 1:! aka host1.com : host1.com.pfx www.host1.com : www.host1.com.pfx Even if the host1.com.pfx caries the alt name of the www? – Robert Leiper May 15 '18 at 18:28
  • The certificate naming convention is just like that. – Lex Li May 16 '18 at 0:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.