"Your connection is not private" is the heading Chrome, Edge, Brave and Opera display when they refuse to continue to an HTTPS site. It is a container, not a diagnosis. The real reason is the code printed underneath, such as NET::ERR_CERT_DATE_INVALID. Safari shows "This Connection Is Not Private" and Firefox shows "Warning: Potential Security Risk Ahead," both with their own codes.
This page is a triage guide. Use it to read the code, jump to the specific fix, and decide whether it is safe to continue.
Step 1: Find the code
Click Advanced. Chrome prints a line like "NET::ERR_CERT_AUTHORITY_INVALID" and a sentence about the issue. In Firefox, click Advanced and read the code, for example SEC_ERROR_UNKNOWN_ISSUER. In Safari, click Show Details.
| Code you see | Meaning | Detailed page |
|---|---|---|
| NET::ERR_CERT_DATE_INVALID | Expired, not yet valid, or wrong clock | ERR_CERT_DATE_INVALID |
| NET::ERR_CERT_AUTHORITY_INVALID | Unknown or untrusted issuer | ERR_CERT_AUTHORITY_INVALID |
| NET::ERR_CERT_COMMON_NAME_INVALID | Certificate does not cover this hostname | ERR_CERT_COMMON_NAME_INVALID |
| SEC_ERROR_EXPIRED_CERTIFICATE (Firefox) | Expired certificate | SEC_ERROR_EXPIRED_CERTIFICATE |
| ERR_SSL_PROTOCOL_ERROR | Handshake failed, not a certificate warning | ERR_SSL_PROTOCOL_ERROR |
| NET::ERR_CERT_REVOKED | The CA revoked the certificate | Reissue from the CA, see below |
| NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM | Old signature algorithm | Reissue with a modern algorithm |
If you are a visitor
- Read the date and time on your device. A wrong clock triggers many of these.
- Look at the network. If you are on public Wi-Fi, open
http://example.comto see whether a login page appears. That is a captive portal intercepting traffic. - Test the same site on another device and network. Failing everywhere points to the site. Failing in one place points to your device, antivirus or network.
- Deal with security software. Antivirus HTTPS inspection and corporate gateways re-sign traffic; if their root is not trusted, every site fails at once.
- Update the browser and operating system. Missing root updates cause authority errors on old systems.
When it is okay to proceed, and when it is not
Clicking through is reasonable only for a page you control yourself, such as a development server or router interface. For anything with logins, payments or personal data, stop. An attacker on your network would produce exactly this screen.
There is also a limit to what you can bypass. Sites that send an HSTS header, including most large services, do not offer a Proceed link, because the site told your browser never to accept a bad certificate. If there is no link, you must wait for the site to fix it. Use the HSTS Checker to see if a domain is sending that policy.
If you own the site
- Run the SSL Checker first. It reports expiry, issuer, hostnames covered and obvious chain problems in seconds, which maps you directly to one of the pages above.
- Check the chain with the SSL Chain Debugger if the code is authority-related.
- Test every hostname variant (apex,
www, subdomains) and both IPv4 and IPv6 addresses, since each can hit a different server. - Check recent changes. A new DNS target, a hosting migration, a renewed certificate not reloaded, or a CDN setting change are the usual triggers. Review the HTTP headers for hints such as a different
Serverheader than you expect. - Remember revocation. If the code mentions revocation, the CA withdrew the certificate. Renewing the old file does not help; request a new certificate (and a new key if it may be compromised).
The warning page can also be shown for pages that load fine but contain insecure resources. That produces a "Not secure" label rather than a full-page block; fix those with the Mixed Content Checker and the mixed content guide.
Confirm the fix
- Reload in a private window so cached decisions are not reused.
- Run the SSL Checker again. It should show a valid certificate with the correct hostnames.
- Use the Website Health Check for a broader pass across DNS, TLS, redirects and headers.
- Set up an uptime monitor with certificate expiry alerts.
Next steps
- Read SSL/TLS certificate errors explained.
- Automate renewal with how to renew SSL certificates.
- Check protocol compatibility with the TLS Version Checker.
- See the full list of site-reachability errors in This site can't be reached.
FAQ
Is this a virus on my computer?
Rarely. It is a trust failure between your browser and the site. A virus or adware can cause it, but a wrong clock, public Wi-Fi or an expired certificate is far more likely.
Why can't I click Proceed?
The site has an HSTS policy, or your organization's browser policy forbids overrides. Both are intentional.
Does the warning mean my data was stolen?
No. It means the browser stopped before sending anything. The risk begins if you override it on an untrustworthy connection.
The warning appeared on a site I run. What should I check first?
Open Advanced, note the code, and run the SSL Checker. The code and the tool output together usually identify the problem in under a minute.
Get notified when this fix updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.