In short. Your browser shows "Your connection is not private" when it cannot verify your website's security certificate, the proof of identity that makes the secure connection (the padlock) possible. Your visitors then see a warning and may leave without entering your site. It is up to you, or to your hosting provider or web provider who manages the certificate, to fix it. The error code shown names the cause, and the fix usually takes a few minutes of configuration.
"Your connection is not private" is the title of the warning page Chrome shows when it cannot verify a site's security certificate. If it is your site, the cause is almost always on your side: an expired certificate, a certificate that does not cover the address being visited, or a certificate the browser does not trust. The code shown under the message (NET::ERR_CERT_…) tells you which of the three.
Last verified: November 18, 2026, in the Chromium and Firefox source code and in Apple's help.
What your visitors see
In Chrome, the tab is titled "Privacy error" and the page shows, in large type: "Your connection is not private". The browser blocks access and offers to go back. Continuing anyway means clicking Advanced and then a link ending in "(unsafe)": most visitors stop there.
Firefox shows a different page, "Warning: Potential Security Risk Ahead", with its own codes: see our page on the Firefox warning. Safari shows a certificate warning with a Show Certificate button, according to Apple's guide.
For the site, the result is the same everywhere: visitors leave, forms go unfilled, a shop stops selling.
The error code gives the cause
| Code shown by Chrome | What Chrome says | Cause on the site side | Page |
|---|---|---|---|
NET::ERR_CERT_DATE_INVALID | the certificate has expired (or is not valid yet) | renewal forgotten or failed | Fix it |
NET::ERR_CERT_AUTHORITY_INVALID | the certificate is not trusted | self-signed certificate, or incomplete chain | Fix it |
NET::ERR_CERT_COMMON_NAME_INVALID | the certificate was issued for a different name | address not covered (www, subdomain) | Fix it |
The code is written in small type under the warning text. Clicking the code, or Advanced, also shows Chrome's detailed explanation.
Is it the site or the visitor?
Test from another device, on another network (a phone on 4G/5G is enough):
- The error shows up everywhere: the problem is the site. This is the most common case.
- The error shows up on one device only: that device's clock may be wrong. Chrome flags this itself for an expired certificate: its message shows the computer's time and asks whether it is right. An antivirus that inspects connections, or a company network, can also trigger the warning.
Check your certificate for free. Our tool reads your site's certificate from the Internet, like a browser, and tells you whether it has expired, whether it covers your address and whether the chain is complete. Check my certificate
What not to do
- Ask visitors to "proceed anyway": they learn to ignore a warning that exists precisely to catch attacks, and most will not do it.
- Turn HTTPS off: Chrome and Safari will then show "Not secure" in the address bar. See our page on the "Not secure" site.
Why this happens more often than before
The maximum lifetime of certificates is shrinking. The CA/Browser Forum, which sets the rules for certificate authorities, voted in April 2025 for a gradual reduction from 398 days to 47 days, in stages from March 2026 to March 2029. A manual renewal done once a year will no longer be enough: automatic renewal becomes essential.
Frequently asked questions
My site has shown this warning since this morning. Where do I start?
Note the code under the message, then check the certificate's expiry date. A certificate that expired overnight is the most frequent cause of a sudden warning.
The error only appears on my computer. What should I do?
Check the computer's date and time, then briefly turn off the antivirus's HTTPS inspection if it has one. If the error disappears on other devices, the site is not at fault.
My host says the certificate is installed. Why does the error persist?
The certificate may be installed but not cover the address being visited (with or without www), or be served without its intermediate certificates. Our free tool shows what a browser actually receives.
Sources
Accessed on 11/18/2026.
- Chromium, warning page texts (
components/security_interstitials_strings.grdp,components/ssl_errors_strings.grdp) and translations (components/strings/components_strings_<language>.xtb): https://github.com/chromium/chromium/tree/main/components - Firefox, certificate error page texts (
certError.ftl, en-US): https://github.com/mozilla-firefox/firefox - Apple, Avoid fraud by using encrypted websites in Safari on Mac: https://support.apple.com/en-us/guide/safari/sfri40697/mac
- CA/Browser Forum, Ballot SC-081v3 (04/11/2025): https://cabforum.org/2025/04/11/ballot-sc081v3-introduce-schedule-of-reducing-validity-and-data-reuse-periods/