My server application currently has a self-signed certificate and because I must use Google Chrome, I am trying to find a way to add a certificate exception. Recent Chrome 'improvements' appear to have removed this ability.
In Firefox, opening a page with a certificate error is easy to correct (of course, when it is safe to do so) with two steps:
1) Click I Understand the Risks
2) Click Add Exception
Done! The ssl error will no longer appear for this IP.
Question: What are the equivalent steps in Google Chrome?
When opening a page with a certificate error in Chrome, you see the message, "Your connection is not private...Attackers might be trying to steal your information..."
Then you must click, Advanced, see another ominous warning and then click on Proceed to xxx.xxx.xxx.xxx (unsafe) to continue to the intended web page.
This warning is repeated every time I need to access my web server. Very annoying!
I have even attempted (in vain) to add the certificate into Chrome's cert listing. For example:
1. Click on certificate icon in address bar
2. Certificate information
3. Details tab
4. Copy to file
5. Select Base-64 encoded .cer
6. Save file
7, From Chrome Advanced settings Manage SSL, import it to Trusted RCA
Unfortunately, even those steps (and variations) failed to stop this error!
Ideally, I just want to add in an exception!
1) Getting a proper cert is not an option, at this time.
2) I need to use Chrome (even if FF will immediately solve this issue :))
3) I can't use the CLI and add --ignore-certificate-errors because I don't want to blanket ignore all cert errors.
Anyone know how to add a ssl exception in Chrome?
Thanks so much!