Windows – Self signed certificate is not appearing in Chrome after importing

google-chromesslwindows 7

I have a Synology NAS that creates a self signed certificate for SSL access.

I'm using the latest Chrome on Windows 7.

Upon visiting the NAS's landing page, Chrome presents a red warning to say that "Server's certificate is not trusted". This is what I did to try to resolve it to no avail:

  1. Click on the lock
  2. Click on Certificate Information
  3. Click Details tab
  4. Click Copy to file… which saves the certificate locally. (I tried this with all the export option presented here – X.509, #PK7)
  5. Double clicked on the file then click Install Certificate
  6. Ensured that it is installed in the "Trusted Root Certification Authority" section
  7. Type "certmgr.msc" in Start menu to confirm that the certificate has been installed correctly
  8. Restarted Chrome
  9. Visit NAS landing page… Low and behold, same bloody thing.
  10. Go to Chrome settings > Advanced settings > Manage Certificates, to find that the certificate is not listed or recognised by chrome, even though it is stored correctly by windows.
  11. Tried importing to chrome using the import button in the Chrome settings. Still no luck.

Can anyone confirm that this is normal behaviour? If not, please advise how this can be solved?

Best Answer

Thanks to all the comments so far. After some tweaking around I stumbled upon this which was very helpful to me: http://forum.synology.com/enu/viewtopic.php?f=145&t=77919

The NAS actually creates 2 types of certificates, one for the website, and one for the root authority.

It first tries to identify the website's certificate. Upon inspection it sees that the certificate has been issued by a particular Certification Authority. You can't simply install the website's certifcate. You need to actually install the CA's certificate generated by the NAS.

Upon doing this I closed Chrome using the X button. That didn't work. I did this a couple more times, and then I used the chrome "Exit" menu. This worked! So lesson learned... X does not necessarily restart Chrome.

This is now resolved!

Related Question