“Your connection is not private” is Chrome doing its job. When you see this error, Chrome detected a problem with the SSL certificate that the website presented and refused to load the page without warning you first. That’s the right behaviour — the same mechanism that prevents your data from being intercepted by a man-in-the-middle attack. This fits into the wider topic we cover in our Google Chrome Errors.
The practical question is whether the warning is about a real security problem or a false alarm caused by something on your own machine. In my experience, false alarms are significantly more common than genuine threats — a wrong system clock is responsible for more “your connection is not private” errors than actual certificate problems. The error code beneath the main message is the key to telling them apart.
Read the Error Code Before Doing Anything Else
Chrome shows a specific error code beneath “Your connection is not private” — usually something like NET::ERR_CERT_DATE_INVALID or NET::ERR_CERT_AUTHORITY_INVALID. This code is more useful than the headline message and points directly to the cause.
- NET::ERR_CERT_DATE_INVALID — The certificate’s dates don’t match the current date. Either the certificate has genuinely expired, or (far more commonly) your system clock is wrong. Check the clock first — it’s the cause in the majority of cases.
- NET::ERR_CERT_AUTHORITY_INVALID — The certificate wasn’t issued by a Certificate Authority that Chrome trusts. Appears on self-signed certificates (common on internal tools and routers), and also when antivirus software inserts its own certificate into the SSL chain and Chrome doesn’t recognise it.
- NET::ERR_CERT_COMMON_NAME_INVALID — The certificate was issued for a different domain than the one you’re visiting. The ERR_CERT_COMMON_NAME_INVALID guide covers this specific error in detail.
- NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM — The certificate uses a signing algorithm (like SHA-1) that’s now considered insecure. Chrome blocks these by default; there’s nothing to fix on your end — the site needs to update its certificate.
Once you’ve noted the code, the fix path becomes much clearer. The sections below are organised around the most common codes.
Fix 1: Check Your System Clock (Most Common Fix)
If the error code is NET::ERR_CERT_DATE_INVALID, check your system clock before assuming the certificate has expired. SSL certificates are only valid within a specific date range, and Chrome validates the certificate against your machine’s current date. A clock that’s wrong by even a few hours will cause every SSL certificate to appear either expired or not yet valid.
The same clock and certificate checks apply in other browsers, just under a different name: Firefox’s Secure Connection Failed error is triggered by the identical causes, so the fixes here translate directly if you switch browsers.
This happened to me the first time I saw this error — a power cut had caused the clock to drift forward by about three hours, and suddenly every HTTPS site in Chrome was “not private.” One clock sync fixed everything immediately.
- Right-click the clock in the taskbar → Adjust date and time
- Toggle Set time automatically to On
- Toggle Set time zone automatically to On
- Click Sync now
- Verify the time displayed is actually correct
- Reload the page
If the time looks right after syncing but the error persists, the certificate may genuinely be expired. In that case there’s nothing you can fix locally — the site owner needs to renew their certificate. This is common on smaller sites, internal tools, and any site whose owner has let the certificate expire without realising it.
Fix 2: Clear the SSL State and Chrome Cache
Chrome caches SSL certificate information. When a site renews its certificate after it expired, or when a certificate chain changes, Chrome sometimes keeps showing the old “not private” warning because it’s working from cached certificate data rather than fetching fresh information from the server. Clearing both the Windows SSL state and Chrome’s own certificate cache forces a clean re-evaluation.
- Open Internet Options (search in Start menu)
- Go to the Content tab → click Clear SSL State → OK
- In Chrome, press Ctrl + Shift + Delete → All time → check Cached images and files and Cookies and other site data → Clear data
- Restart Chrome fully and reload the page
This is particularly useful when a site you visit regularly starts showing “your connection is not private” suddenly — the site probably renewed its certificate and the cached old certificate data is causing the mismatch.
Fix 3: Disable Antivirus SSL Scanning
Antivirus products that scan HTTPS traffic work by acting as a man-in-the-middle — they intercept the SSL connection, decrypt it to scan the content, and re-encrypt it before passing it to Chrome. To do this, they substitute the website’s real certificate with their own certificate. If Chrome doesn’t trust the antivirus’s certificate (which happens when the antivirus hasn’t properly installed its root certificate, or when Chrome updates its certificate validation rules), every HTTPS site shows “your connection is not private” with NET::ERR_CERT_AUTHORITY_INVALID.
The giveaway: if every HTTPS site is showing this error simultaneously, not just specific ones. A single expired certificate affects one site. Antivirus SSL scanning affects all of them.
- Temporarily disable SSL scanning, HTTPS scanning, or Web Shield in your antivirus settings
- Test whether “your connection is not private” resolves
- If it does: check for an antivirus update that fixes the certificate installation, or look for a “trust Chrome” option in the advanced web protection settings
Fix 4: Proceed Carefully for Internal Tools You Trust
“Your connection is not private” on internal network resources — your router’s admin page (usually 192.168.1.1), a NAS device, a local development server, a work intranet application accessed by hostname — is expected behaviour. These tools use self-signed certificates that Chrome has no reason to trust, because they’re not issued by a public Certificate Authority. The error is technically correct but the connection is safe in context.
If you’re confident about what you’re accessing: click Advanced on the error page, then Proceed to [address] (unsafe). Chrome loads the tool and remembers the exception for that certificate.
A firm warning: only click through on internal tools you’re certain about — your own router, your own NAS, a locally hosted application you set up yourself, or an internal company tool your IT department runs. Never click through on public-facing websites, sites handling financial or personal data, or sites you’ve never visited before. The warning exists for a reason on those.
Fix 5: Check VPN and Proxy
VPN services with built-in ad blocking or malware protection sometimes inspect HTTPS traffic using their own certificate, similar to how antivirus products do it. If Chrome doesn’t recognise the VPN’s certificate as trusted, “your connection is not private” appears on any site the VPN inspects.
Disconnecting the VPN completely (not just pausing it — fully quitting the application) and testing whether the error resolves confirms this quickly. If it does, look in the VPN application’s settings for an “HTTPS inspection,” “web filtering,” or “safe browsing” feature and disable it. The VPN tunnel for privacy purposes doesn’t require HTTPS inspection to work — that’s a separate (and often unnecessary) feature.
Also check Windows proxy settings: Settings → Network and internet → Proxy. If a proxy is configured, it may be intercepting SSL connections similarly to antivirus software. Temporarily disabling the proxy and testing confirms whether it’s the cause.
Fix 6: TLS Settings in Windows
If “your connection is not private” appears on multiple sites that were previously working fine, and the system clock is correct, checking that TLS 1.2 and 1.3 are properly enabled in Windows is worth a quick look. Security tools and group policies occasionally disable these protocol versions, which causes Chrome to fail SSL handshakes that require them.
- Open Internet Options (search in Start)
- Click the Advanced tab
- Scroll to the Security section
- Confirm Use TLS 1.2 and Use TLS 1.3 are both checked
- Click Apply → OK → restart Chrome
| Error code shown | Most likely cause | Fix |
|---|---|---|
| NET::ERR_CERT_DATE_INVALID | Wrong system clock or expired cert | Fix 1 — sync clock; if clock is right, cert expired |
| NET::ERR_CERT_AUTHORITY_INVALID | Self-signed cert or antivirus intercepting | Fix 4 (trusted internal tool); Fix 3 (antivirus) |
| NET::ERR_CERT_COMMON_NAME_INVALID | Certificate for wrong domain | Dedicated guide; Fix 2 (clear SSL state) |
| All HTTPS sites simultaneously | Antivirus scanning or bad TLS settings | Fix 3 (antivirus); Fix 6 (TLS settings) |
| Started after VPN connected | VPN certificate interception | Fix 5 — disable VPN HTTPS inspection |
Our guide on ERR_SSL_PROTOCOL_ERROR covers the related SSL handshake failure that shares several root causes with “your connection is not private” — particularly the system clock and TLS protocol version issues. The Google Chrome support pages include additional certificate error documentation for enterprise environments where custom Certificate Authorities, certificate pinning, and managed TLS settings cause this error on legitimate internal sites.
Certificate pinning is a less common but worth-understanding cause of “your connection is not private” on specific well-known sites. Chrome has a built-in list of certificates that certain high-value sites (Google properties, major banking institutions, some government sites) are expected to use. When the certificate presented by one of those sites doesn’t match Chrome’s expected certificate for that domain — which can happen if your connection is being monitored by a corporate proxy, a government inspection system, or a compromised network — Chrome shows “your connection is not private” regardless of whether the certificate is technically valid. This is called HSTS (HTTP Strict Transport Security) with certificate pinning, and it’s deliberately designed to prevent certificate substitution even by parties who control a trusted Certificate Authority. If you see “your connection is not private” with NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED or similar codes on a major known site like google.com or gmail.com, a network-level interception (corporate proxy, transparent proxy) is almost certainly the cause, and the fix is operating on a network that doesn’t intercept SSL traffic rather than any change on your local machine.
Chrome’s security warning bypass for specific sites (the “Proceed anyway” link) creates permanent per-certificate exceptions that persist until the certificate changes. This is occasionally useful for internal development environments where a self-signed certificate is used consistently, but it creates a hidden risk: if the certificate on that server changes (because the server was replaced, the certificate was reissued, or because an attacker is substituting their own certificate), Chrome will show the “your connection is not private” error again. Seeing the warning on a site you previously clicked through on is therefore meaningful — it may indicate the certificate legitimately changed, or it may indicate something else changed. Don’t automatically click through a second time without investigating whether the certificate change was expected.
HSTS (HTTP Strict Transport Security) causes a related but distinct variant of connection security errors that’s worth mentioning. When a site has set an HSTS policy, Chrome remembers that the site should always be loaded over HTTPS. If the HTTPS connection subsequently shows a certificate problem, Chrome will not allow any bypass at all — there’s no “Proceed anyway” link. This is intentional: HSTS is designed to prevent users from bypassing certificate warnings on sites that have explicitly requested the strict behaviour. If you’re getting “your connection is not private” with no ability to proceed on a site you know well, the site has HSTS enabled and has a genuine certificate problem that only the site owner can resolve. The only workaround for testing purposes is to clear the HSTS state for that domain: open Chrome’s Settings → Privacy and security → Security → Manage certificates → search for the domain in the HSTS preload list, or use chrome://net-internals/#hsts, enter the domain, and click Delete domain security policies — but this is only appropriate for development and testing scenarios, not for live sites.
Certificate Transparency (CT) is a newer Chrome requirement that adds another layer of certificate validation. Since 2018, Chrome requires that all new certificates issued by trusted CAs be logged in public Certificate Transparency logs. Certificates not appearing in these logs — typically older certificates or certificates from CAs that don’t comply with CT requirements — trigger NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED, which appears as part of the “your connection is not private” error family. This is purely a server-side issue: the site’s certificate needs to be reissued by a CT-compliant CA and logged publicly. Nothing on the client side can bypass this requirement intentionally — Chrome’s CT enforcement is not configurable by users. Seeing this error on a site you manage is a signal to contact your certificate authority and reissue the certificate through a fully CT-compliant process.
For developers who frequently encounter “your connection is not private” on localhost development environments, a more permanent solution than repeatedly clicking through is to generate and install a locally trusted development certificate using a tool like mkcert. mkcert creates a local Certificate Authority that’s trusted by your machine’s certificate store (and therefore by Chrome), then issues certificates signed by that CA for localhost and any development hostnames you configure. The result is legitimate green-padlock HTTPS on local development sites without the security warning. This is significantly more convenient than clicking through the warning on every new browser session and avoids the bad habit of training yourself to dismiss security warnings that Chrome is legitimately trying to show you. You might also run into Microsoft Teams Not Working? Fixes for Audio, Login, and Connection Problems.
