Configuring Chrome to Ignore SSL Warning on Specific Addresses

25

5

I guess there no need to introduce the "Privacy error" page in Chrome that appears whenever one uses SSL to access an uncertified website that has no signed certificate (red "X" on the lock icon).

Thing is, I use SSL to access numerous personal locations which I vouch for and know for a fact they're OK (they're mine). Since I'm visiting those location more than once a day, I'm forced to go through two clicks before I enter the website and that's tedious.

Is there a way add an "exception" specifically for this matter, for specific websites (a white list essentially)? Any other way of achieving this is of course more than welcomed.

Thanks!

voronoi

Posted 2015-06-20T12:35:40.297

Reputation: 541

1Are you aware of letsencrypt who will give you free SSL certificates?

That won't work if it's for sites on an internal network though. – Mikael Kjær – 2016-11-24T10:42:37.083

I've heard of it. Do you mean that it would not work for LAN resources like NAS devices and/or home servers? – voronoi – 2016-12-05T08:58:29.243

Only if it has an external hostname with a valid TLD, like mydomain.com – Mikael Kjær – 2016-12-05T10:15:25.027

2I've been beating my head against this. I don't care about the sites security, its just a testing site. Chrome is just playing it too hard. In Firefox you just click one button to ignore the error for a particular site, and that's that. I concluded I'm better of using Firefox than rather than waste a few more hours making Chrome happy with a bad certificate about which I don't really care. – Kris – 2018-05-18T00:39:09.567

Answers

7

I don't believe there is per-website setting that specific in Chrome.

If you have, or can get an SSL certificate, you may be able to copy your certificate directly into Chrome's certificate store, and mark it as Trusted Root. Navigate to "Settings > Advanced > HTTPS/SSL > Manage Certificates..." to import it. See Getting Chrome to accept self-signed localhost certificate for more information about how to do this.

Alternatively, you can try to add the site to your Trusted Sites list (located in "Control Panel > Internet Options > Security tab") which may alleviate the error. Be sure to untick the "Require server verification (https:) for all sites in this zone" checkbox.

Floofies

Posted 2015-06-20T12:35:40.297

Reputation: 167

With the second solution you offered, are you sure you were referring the Chrome? I couldn't find a security "tab" (the Chrome control panel is not tabbed) anywhere, but I might be doing something wrong. – voronoi – 2015-06-20T16:03:27.970

Sorry. Internet Options is located in the Windows Control Panel. – Floofies – 2015-06-20T16:07:29.590

2Hi, I tried everything described in that discussion (that is relevant), and nothing worked. Maybe the solutions offered there a outdated, and versions of Chrome released since require a different approach? – voronoi – 2015-06-30T08:14:04.293

3

You must create a self-signed certificate, and have the SAN (Subject Alternative Name) element configured within the certificate for the appropriate server name. Then import the certificate into Chrome, giving it "Trusted" status. Without the SAN element configured properly, errors will still occur.

Mitch R.

Posted 2015-06-20T12:35:40.297

Reputation: 31

1@Mitch, this sounds exactly like what I'm looking for. Is there any guide that describes how to do this? – voronoi – 2017-10-15T05:10:50.780

The procedure varies, dependent upon the OS one uses. A few simple searches should bring up the procedure for a particular OS.

One can use an "online generator" as well, but the SAN is usually not colinfigurable, and thus produces varying results once imported into the browser's security store and marked as 'trusted".

Mobilefish Generator

SSLChecker Generator

– Mitch R. – 2017-10-16T09:44:23.380

2

Another quick option to get past this is to type in Chrome's "interstitial bypass keyword" whilst the offending page has focus. At the time of writing, this is thisisunsafe but it has changed in the past and is likely to do so in future.

The usual caveats apply - only use it if you know what you're doing. More detailed info is in the links below:-

Steve Chambers

Posted 2015-06-20T12:35:40.297

Reputation: 618