Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Make sure that the CN ("Common Name") attribute matches in your URL and certificate. For example, if you created your certificate using the CN=localhost, but you are accessing it in IE using something like <a href="https://machine.domain.topleveldomain" rel="nofollow">https://machine.domain.topleveldomain</a>, then IE will complain that machine.domain.topleveldomain is not the same as localhost. I believe it does a string comparison.</p> <p>Make sure that the certificate was installed in the Trusted Root Certification Authorities (TRCA) under the Local Computer physical store.</p> <p>If all is installed correctly, then there is one more possibility. Windows has a "feature" that wipes out untrusted certificates (untrusted according to mircosoft) from the TRCA. You can disable this feature first and then reinstall the certificate.</p> <p>Open up <code>gpedit.msc</code> and drill down to <code>Computer Configuration &gt; Administrative Templates &gt; System &gt; Internet Communication Management &gt; Internet Communication Settings &gt; Turn off Automatic Root Certificates Update</code>. Enable <code>Turn off Automatic Root Certificates Update</code>.</p> <p>Microsoft provides some details about what that feature does---its a security feature where your TRCA is compared against microsoft's database of valid root certificates.</p> <p>If it is <em>still</em> not working after you turn that feature off, then there is a problem with the way in which you created that certificate. You can make a certificate using <code>makecert</code>. <a href="http://msdn.microsoft.com/en-us/library/bfsktky3(v=vs.80).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/bfsktky3(v=vs.80).aspx</a></p> <p>If your computer's fully qualified name is: machine.domain.com, you can do this:</p> <p><code>makecert -n "CN=machine.domain.com" c:\file.cer</code></p> <p>Eventually you can access your resources by: <a href="https://machine.domain.com" rel="nofollow">https://machine.domain.com</a></p> <p>Hope this helps. I have had my fair share of self-signed certificate woes.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload