No “Proceed Anyway” option on NET::ERR_CERT_INVALID in Chrome on MacOS

FYI: Chrome on MacOS treats this different than Windows. MacOS version won't see the proceed button even you click advanced button.

To still proceed the visit as you are sure this page is safe, here is a easy way to do:

There's a secret passphrase built into the error page. Just make sure the page is selected (click anywhere on the screen), and just type thisisunsafe.

Ref: https://twitter.com/zairwolf/status/1196878125734486021

---

There is a hidden way to bypass that error, even if no button allows it. Of course, this should be used for your own sites only – where you are perfectly sure that site is not hacked, but simply local and therefore without a valid internet certificate.

Simply click anywhere on the denial page and type “thisisunsafe”.

Sounds crazy, but works to bypass chrome’s supervision of your safety. Chrome should get kicked for not accepting the certificate of devices in my local network. This is not IoT, this is "Ny Net"!

---

This solution worked for me.

Right click, select inspect element

click on console tab

Copy paste sendCommand(SecurityInterstitialCommandId.CMD_PROCEED) press Enter

Boom! it should load the page :)

---

i just typed “thisisunsafe”, it worked for me

---

To make even macOS Chrome show the "Proceed" link under advanced, make sure to create the certificate with the TLS Web Server Authentication in the X509 extensions.

Here's a oneliner to create with that extension:

openssl req \
  -newkey rsa:2048 \
  -x509 \
  -new \
  -nodes \
  -keyout server.key \
  -out server.crt  \
  -subj /CN=test1   \
  -sha256  \
  -days 3650  \
  -addext "subjectAltName = DNS:foo.co.uk,IP:127.0.0.1,IP:192.168.1.1" \
  -addext "extendedKeyUsage = serverAuth"

If you MacOS openssl does not have addext option, then use this alternate form:

openssl req \
  -newkey rsa:2048 \
  -x509 \
  -nodes \
  -keyout server.key \
  -new \
  -out server.crt \
  -subj /CN=test1 \
  -extensions v3_new \
  -config <(cat /System/Library/OpenSSL/openssl.cnf \
  <(printf '[v3_new]\nsubjectAltName=DNS:a.spectrocloud.com\nextendedKeyUsage=serverAuth')) \
  -sha256 \
  -days 3650

The key being extendedKeyUsage=serverAuth.

---

After a long search, I have found a solution. This solution is for mac.

First, got to settings. Search for manage certificates. KeychainAccess will open. Try to find the name of the certificate, for example localhost was the name in my case. If you click on the certificate it will show the details. Then the Trust section you have to select Always Trust for "when using this certificate". Now check in the browser again. You will directly be able to access the page. Privacy error, Your connection is not private message will not come.

---

in MacOS Catalina I had it working by:

copy pasting the PEM certificate content into a text editor (such as vi) and saving it as a .pem file (e.g. localhost.pem) in finder, open the cert file you've just created and add it to the System Keychain a Keychain Access window will be show; open your localhost cert set "Always Trust" for Secure Sockets Layer (SSL) as depicted below

https://i.stack.imgur.com/3jmaN.png

That's it, refresh your browser and it should work just fine :)

---

Make a browser trust an SSL certificate

In Chrome, we can write the following URL in the search bar: chrome://flags/#allow-insecure-localhost and activate the relative option.

courtesy:https://www.thomasvitale.com/https-spring-boot-ssl-certificate/

---

Just click on "Not Secure" on search bar of chrome denial page , then click certificate, then you can see your certificate. click on Trust option do always trust.

---

So after adding this question a colleague found this thread.

There seem to be two options to solve this issue:

Just install the certificate in MacOS key chain. Then double click on it and under "trust" select "always trust".

Generate a certificate according to the new MacOS Catalina specs.

---

A possible solution is to launch Chrome with parameter "--ignore-certificate-errors".

Steps for Mac OS:

Close Chrome.

From the Finder, select “Go” > “Utilities“.

Launch “Terminal“.

Type the following command, then press “Enter“: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --ignore-certificate-errors &> /dev/null &

Solution from https://www.technipages.com/google-chrome-bypass-your-connection-is-not-private-message

---

I was struggling with same issue on multiple browsers. After banging my head around, I looked for any invalid certificate(s) or entries having red cross icon underneath, and deleted them. Afterwards, I never came across that error screen saying 'You connection is not private'

If you are on Mac, follow steps below:

Open Keychain Access

Select System Roots from left bar

Navigate to Certificates Tab

Locate any invalid certificate with red cross icon, Right click and hit Delete

And also follow:

Select System from left bar

Navigate to All Items and Passwords Tab(s)

Locate any invalid entry with red cross icon, Right click and hit Delete

Now refresh and see if it works for you.

---

This error can be simply bypassed by starting the chrome in insecure mode as follows.

google-chrome --args --disable-web-security --allow-running-insecure-content --user-data-dir=/tmp/chrome-insecure/ -ignore-certificate-errors

---

This worked for me in 2021 on my 2007 iMac:

https://www.youtube.com/watch?v=m3FgAztrYYo

Letsencrypt root certificate link is included.

---