How to Quickly Fix Your Connection is Not Private on Google Chrome

How to bypass Google Chrome privacy error

Hey there! Some links on this page may be affiliate links which means that, if you choose to make a purchase, I may earn a small commission at no extra cost to you. I greatly appreciate your support!

In this short tutorial, you will learn how to bypass the “Your connection is not private” message in Google Chrome. While this fix will work for most websites, it won’t work 100% of the time.


Please do not proceed without considering the consequences. As the error message itself states:

Attackers might be trying to steal your information from (for example, passwords, messages, or credit cards).

Google Chrome is trying to protect you. The error message might read ERR_CERT_INVALID or ERR_CERT_AUTHORITY_INVALID which means there is a problem with the SSL certificate that’s installed on the website that you are trying to access.

In case you’re not familiar, an SSL certificate is what gives a website HTTPS. The “S” in HTTPS means secure. Websites that use the HTTPS protocol are secure because the data transmitted over the internet is encrypted from prying eyes.

Only if you fully trust the website that you are trying to access, then it’s okay to proceed. Otherwise, you are putting yourself at risk to have any potential sensitive data intercepted by a hacker.

Connection is not Private Workaround

To get around the “Your connection is not private” error message in Chrome, you simply need to type the following while the page is visible.


There’s no text box to type it in or anything like that. The browser is programed to listen for this combination of characters at which point will bypass the privacy error and allow you to proceed to the website.

In fact, you can actually see this in the source code for Chrome.

* @param {string} e The key that was just pressed.
function handleKeypress(e) {
// HTTPS errors are serious and should not be ignored. For testing purposes,
// other approaches are both safer and have fewer side-effects.
// See for more details.
var BYPASS_SEQUENCE = window.atob('dGhpc2lzdW5zYWZl');
if (BYPASS_SEQUENCE.charCodeAt(keyPressState) == e.keyCode) {
    if (keyPressState == BYPASS_SEQUENCE.length) {

In this case, the window.atob function converts the base-64 encoded string ‘dGhpc2lzdW5zYWZl‘ to plain text ‘thisisunsafe‘. You can try this conversion yourself.


Meet Tony

Tony from Tony Teaches Tech headshot

With a strong software engineering background, Tony is determined to demystify the web. Discover why Tony quit his job to pursue this mission. You can join the Tony Teaches Tech community here.

4 Responses

  1. That handleKeyPress logic still exists in latest Chromium commit (April 24, 2024) for that source file (/components/security_interstitials/core/browser/resources/interstitial_large.js) — secret phrase string is unchanged, so it should still work.

Leave a Reply

Your email address will not be published. Required fields are marked *