Super User is a question and answer site for computer enthusiasts and power users. 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 have a number of network devices that I access over HTTPS. However, they are self-signed certificates, so Chrome displays a warning page.

enter image description here

In earlier versions of chrome, I seem to remember an "add exception" button on this screen, or on the certificate's information window (if you clicked the HTTPS in the address bar). However, that has long since disappeared.

How can I add an exception for specific self-signed certificates in Chrome 28?

share|improve this question

migrated from Aug 14 '13 at 22:08

This question came from our site for system and network administrators.

Are you trying to get this done on multiple workstations or just yours? – Tanner Faulkner Aug 14 '13 at 15:23
Just a single workstation. – Force Flow Aug 14 '13 at 15:26
Why didn't you ask this on SU? – Tanner Faulkner Aug 14 '13 at 15:28
related:… – yms Jun 7 at 20:28
up vote 15 down vote accepted

Export the certificate from Chrome, and then import the certificate into your trusted root certification authority store. Unfortunately Microsoft made this difficult to do.

Go to Start | and run the command certmgr.msc.

Expand the tree to get to Trusted Root Certification Authorities | Certificates. Go to All Tasks, choose Import and import the certificate in question.

To export the certificate from Chrome:

Click on the Certificate icon in the address bar. Click on Certificate Information | Details and then Copy to File.

share|improve this answer
Thanks @Forceflow -- that's a shortcut I'll use myself in the future. – Quinten Aug 14 '13 at 15:24
Well, I imported the cert successfully, but when I refreshed the HTTPS page, it still showed the certificate warning. When I looked in the certificate manager, I couldn't find the imported certificate anywhere. – Force Flow Aug 14 '13 at 15:30
You still need to make sure the name matches the website address you are connecting to. You could edit your /etc/hosts file as one solution. – Quinten Aug 14 '13 at 15:40
I should say that the CN needs to match--can be an IP address or a hostname. – Quinten Aug 14 '13 at 15:43
Doesn't work anymore... – Mrchief Aug 17 '15 at 17:00

For Mac OS X:

Click on the Certificate icon in the address bar. Click on "Certificate Information", then drag and drop the certificate image to your desktop or any other folder.

Double click the cer file you've just saved, it will open in the Keychain Access.

Choose a keychain to store it (I think this step is specific to Yosemite), for example "login", and finally click "always trust".

If you're not being asked where to save it or if you should trust it, locate the newly added certificate (it should be at the top of your list), right click it, choose "get info" and then choose "Always trrust" in the Trust tab, under "When using this certificate".

share|improve this answer
This procedure does not work for my Synology NAS. I can confirm, that the certificat is imported into KeyChain. But I still get the same error message from Chrome. – BetaRide Apr 18 '15 at 6:32
I'm experiencing similar issues, as BetaRide, but I think this is down to the hostname of the cert, which is different to the name the cert was created with – Andrew Jul 26 '15 at 5:52
When I put the certificate in my "login" chain, it didn't make any difference. I had to put it in the chain for my username and changed the "Use Custom Settings" trust level to "Always Trust", which changed all of the other options to that setting, not just the one for "X.509 Basic Policy". – L S Aug 7 '15 at 16:51
Thanks for your comment @L S, hopefully it will help other users with the same issue ;-) – Capsule Aug 10 '15 at 7:49
Actually, you can leave it in the login keychain, right click it, choose "get info" and then choose "Always trrust" in the Trust tab, under "When using this certificate" – Capsule Oct 2 '15 at 5:46

For OS X, to do it from the command line:

sudo security add-trusted-cert -p ssl -d -r trustRoot -k ~/Library/Keychains/login.keychain selfsigned.crt

If you don't have a .crt file (selfsigned.crt in this command) already to reference, view the cert in Chrome and drag it to your desktop.

share|improve this answer

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.