Your connection is not private: what it means and how to fix it

11 min readUpdated

Your connection is not private is the heading Chrome shows when it cannot verify a site's certificate, and it stops before loading the page [1][7]. Firefox stops at the same point under its own heading, Warning: Potential Security Risk Ahead [4]. The heading only says that a check failed. On our test server Chrome put the same heading over every certificate fault it rejected, from an expired certificate to a missing intermediate, and only the error code behind Advanced told them apart [7]. Find that code first: it tells you whether the fix is on your device or at the site. The codes themselves are explained one by one under SSL certificate errors.

Quick facts

Where it appears
Chrome, as the page heading; the tab reads Privacy error [1]
Firefox equivalent
Warning: Potential Security Risk Ahead; on a site that uses HSTS, Did Not Connect: Potential Security Issue [4]
What failed
one of the checks on the site's certificate: the name, the dates or the issuer [5][7]
Where the code is
behind Advanced in both browsers: NET::ERR_CERT_... in Chrome, Error code: ... in Firefox [7]
Who fixes it
the visitor when the device clock, a Wi-Fi login page or HTTPS-scanning software is the cause; otherwise the site owner [1][4]
Can you continue?
for the faults in our test, yes, from the Advanced section; not on a site that uses HSTS, and in Chrome not for a revoked certificate [1][6][7]

What the warning means

Before it shows a page over HTTPS, the browser checks the site's certificate. The certificate has to name the host in the address bar, the current date has to fall inside its validity period, and it has to chain up to a root the browser trusts (RFC 5280, sections 4.1.2.5 and 6) [5]. On our test hostname, Chrome worded a name failure as "This server could not prove that it is good.lab.test; its security certificate is from other.lab.test" [7]. If any of these fails, the browser cannot confirm that it reached the real site.

Chrome's explanation after Advanced says as much: "This may be caused by a misconfiguration or an attacker intercepting your connection" [7]. A forgotten renewal and an interception look the same from the browser's side, so it stops in both cases.

The wording "your connection is not private" is narrower than it sounds. If you chose to proceed anyway, the connection would still be encrypted. What is missing is proof of who holds the other end, and an encrypted connection to an unverified party is exactly what an interceptor needs.

Find your code

In Chrome, select Advanced. The code appears in the form NET::ERR_CERT_DATE_INVALID, with a sentence that names the problem, such as "its security certificate expired" followed by how long ago [7]. In Firefox, select Advanced…; the line reads Error code: SEC_ERROR_EXPIRED_CERTIFICATE or similar [4][7]. Neither browser shows the code before you open that section [7].

We served each fault below from a test server, with certificates from a test authority of our own, and recorded what each browser showed [7]:

Faults served from our test server and the codes Chrome and Firefox showed
Fault on the serverChromeFirefoxRead
certificate expiredNET::ERR_CERT_DATE_INVALIDSEC_ERROR_EXPIRED_CERTIFICATEERR_CERT_DATE_INVALID
certificate not valid yetNET::ERR_CERT_DATE_INVALIDMOZILLA_PKIX_ERROR_NOT_YET_VALID_CERTIFICATEERR_CERT_DATE_INVALID
certificate for another hostnameNET::ERR_CERT_COMMON_NAME_INVALIDSSL_ERROR_BAD_CERT_DOMAINwhich names a certificate covers
self-signed certificateNET::ERR_CERT_AUTHORITY_INVALIDMOZILLA_PKIX_ERROR_SELF_SIGNED_CERTself-signed certificates
issuer the browser does not trustNET::ERR_CERT_AUTHORITY_INVALIDSEC_ERROR_UNKNOWN_ISSUERERR_CERT_AUTHORITY_INVALID
intermediate certificate not sentNET::ERR_CERT_AUTHORITY_INVALID, or no warning (see below)SEC_ERROR_UNKNOWN_ISSUERERR_CERT_AUTHORITY_INVALID
certificate revoked (not in our test)NET::ERR_CERT_REVOKED [3]—certificate revocation

How to fix it as a visitor

Work down this list. The first step that changes the result tells you the cause.

  1. Look for a Wi-Fi login page. A public network that wants you to sign in can get in the way first; Chrome has a Connect to Wi-Fi screen for this, Firefox an Open Network Login Page button [1][4]. Sign in, then reload.

  2. Check the date and time on your device. A certificate is valid only between two dates [5], so a wrong clock makes a valid one look expired or not yet valid. On an expired certificate both browsers printed the device's date and asked you to check it [7]; Chrome also has a Your clock is behind screen [1].

  3. Try another network, such as mobile data instead of Wi-Fi. If the site loads there, the first network is interfering.

  4. Check security software. Software that scans HTTPS traffic puts its own certificate in place of the site's; Chrome has a separate screen for this case, headed An application is stopping Chrome from safely connecting to this site [1]. Firefox advises turning off the antivirus feature "often called “web scanning” or “https scanning”" [4].

  5. Try another browser. A test site that left out its intermediate certificate loaded in Chrome and failed in Firefox [7]; a result that differs by browser points at the site.

When the fault is at the site

If the site fails the same way on a second network and a second device, the problem is at the site. For name and unknown-issuer faults Firefox says so on the screen: "there is nothing you can do to resolve it" [4][7]. Only the site owner can fix the certificate; telling them the error code saves them a step.

Can you get past the warning?

For each fault in our test, both browsers let you continue: in Chrome, Advanced, then Proceed to example.com (unsafe); in Firefox, Advanced…, then Accept the Risk and Continue [1][4][7]. Doing so repairs nothing. It tells the browser to use a connection whose other end it could not verify.

Do not continue on any page where you would sign in, pay or enter personal details. Chrome's own warning names what is at risk: "passwords, messages, or credit cards" [1]. If you do continue, treat whatever you send as visible to someone else.

When there is no way past

A site that uses HSTS has told browsers to accept only verified HTTPS connections, and RFC 6797 requires the browser to terminate the connection on any such error (section 8.4) and advises doing it with "no user recourse" (section 12.1) [6]. We visited a test site that sent HSTS, then served it an expired certificate. Chrome replaced Back to safety with Reload, showed no proceed link, and said "You cannot visit hsts.lab.test right now because the website uses HSTS". Firefox changed the heading to Did Not Connect: Potential Security Issue and said "You can’t add an exception to visit this site" [7]. That is intended: the site asked for exactly this. Chrome also offers no proceed option for a revoked certificate [1].

How to fix it as the site owner

When the error code points at the certificate, the fix is on your server, and nothing visitors do in their browser will clear it. As the site owner, start from the code your visitors see under Advanced and find it in the table above, then check what the hostname actually serves, from a machine other than the server:

$ openssl s_client -connect example.com:443 -servername example.com </dev/null | openssl x509 -noout -subject -issuer -dates -ext subjectAltName

The output answers the three checks in turn: the names covered (subject, Subject Alternative Name), the issuer, and the dates (notBefore, notAfter). For our wrong-name test certificate the last line read DNS:other.lab.test [7]. A certificate that looks correct on disk and wrong here is installed but not served: for example, the server was not reloaded, or a load balancer or CDN in front of it holds its own copy.

When only some visitors see it

A missing intermediate can split visitors by browser. Our test certificate carried the address of its intermediate in the Authority Information Access field (RFC 5280, section 4.2.2.1) [5]. With the intermediate left out, Chrome fetched it from that address and loaded the page, while Firefox showed SEC_ERROR_UNKNOWN_ISSUER; without the address, both failed [7]. With a publicly trusted certificate the Firefox result may differ: desktop Firefox preloads the intermediate certificates that public authorities disclose, while our test authority is not among them [8]. A check from your own browser therefore proves little. Count what the server sends instead:

$ openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null | grep -c 'BEGIN CERTIFICATE'

The server that sent its chain gave 2, the one without the intermediate 1 [7]. See certificate chains for the fix.

After a fix, test again

Chrome reports one code even when a certificate fails several checks: its source checks the faults in a fixed order and reports "the most serious error" [2]. An expired certificate for the wrong name showed only NET::ERR_CERT_COMMON_NAME_INVALID in Chrome and SSL_ERROR_BAD_CERT_DOMAIN in Firefox; the same dates on the right name showed NET::ERR_CERT_DATE_INVALID [7]. Fix the reported fault, then load the page again before you call it done.

When it is a different screen

This site can't provide a secure connection is a different Chrome screen [1]. When we pointed both browsers at a plain HTTP listener over https://, Chrome showed it with ERR_SSL_PROTOCOL_ERROR in plain sight and no way to proceed, and Firefox showed Secure Connection Failed [4][7], and Safari's version is covered under Safari can't establish a secure connection. A page that loads with a missing or broken padlock is not this warning either; one cause is mixed content, an HTTPS page loading some resources over plain HTTP.

FAQ

What does "your connection is not private" mean?

The browser could not verify the site's certificate, so it stopped before loading the page. The certificate may have expired, may not cover the address, or may come from an issuer the browser does not trust. The code under Advanced names which.

How do I fix "your connection is not private"?

Sign in to the Wi-Fi if it has a login page, check your device's date and time, try another network, and turn off HTTPS scanning in security software for a moment. If the site fails the same way on another network and device, the fault is at the site and only its owner can fix it.

How do I get past "your connection is not private"?

Select Advanced, then Proceed in Chrome or Accept the Risk and Continue in Firefox. It does not fix the connection, so never do it on a page where you would sign in, pay or type personal details. Sites that use HSTS do not offer the option.

Is it safe to continue to the site?

Only for reading, and only if you accept that the connection is unverified. Anything you send could be read by whoever is in a position to intercept it, and the warning cannot tell you whether anyone is.

Why do I see this warning on every website?

Something on your device or network is affecting all connections: a wrong system clock, security software scanning HTTPS, a corporate network that inspects traffic, or a public Wi-Fi login page. One site with a certificate problem would not affect the others.

Sources

  1. Chromium, components/security_interstitials_strings.grdp (warning screens: privacy error, clock, Wi-Fi login, interfering software, HSTS and revoked) and components/error_page_strings.grdp.

  2. Chromium, net/cert/cert_status_flags.cc (MapCertStatusToNetError).

  3. Chromium, net/base/net_error_list.h.

  4. Firefox, toolkit/locales/en-US/toolkit/neterror/netError.ftl and certError.ftl.

  5. IETF, RFC 5280, Internet X.509 Public Key Infrastructure Certificate and CRL Profile, sections 4.1.2.5, 4.2.2.1 and 6.

  6. IETF, RFC 6797, HTTP Strict Transport Security (HSTS), sections 8.4 and 12.1.

  7. Our test setup: Python HTTPS servers with certificates from a test authority of our own, Chrome and Firefox in headless mode, and OpenSSL 3.0.

  8. Mozilla Security Blog, Preloading Intermediate CA Certificates into Firefox.