How to Fix "Your Connection is Not Private" Error (All Browsers, 2026)
The "Your Connection is Not Private" error means your browser couldn't verify the SSL certificate on the website you're visiting. It's a security warning, not a crash — your browser is actively protecting you from a potentially unsafe connection. This guide explains what every error code means and shows you exactly how to diagnose and fix each one.
Attackers might be trying to steal your information from example.com (for example, passwords, messages, or credit cards).
Chrome · This error appears when the SSL certificate has expired or the date is incorrect.
What Each Error Code Means
| Error Code | What It Means | Who Needs to Fix It |
|---|---|---|
NET::ERR_CERT_DATE_INVALID | The SSL certificate has expired, or your device's date/time is wrong | Website owner (expired cert) or visitor (wrong clock) |
NET::ERR_CERT_AUTHORITY_INVALID | Certificate was issued by a CA the browser doesn't trust (self-signed, or unknown root) | Website owner |
NET::ERR_CERT_COMMON_NAME_INVALID | Certificate domain doesn't match the URL (name mismatch) | Website owner |
NET::ERR_CERT_REVOKED | The certificate was explicitly revoked by the CA | Website owner |
NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM | Certificate uses an outdated algorithm (SHA-1 or MD5) | Website owner |
SSL_ERROR_RX_RECORD_TOO_LONG (Firefox) | Non-SSL traffic received on the HTTPS port | Website owner (server misconfiguration) |
Quick Diagnosis: Is It Your Browser or the Website?
Before spending time troubleshooting, determine whether the error is on your side or the server's. Open the SSL Checker and enter the domain showing the error. If the tool also reports a certificate problem, the issue is on the website's server — contact the website owner. If the SSL Checker shows the certificate is valid, the problem is on your browser or network.
SSL Checker — Enter the problem domain:
Certificate expired on: June 15, 2026 — Server needs to renew
Fix #1: Expired Certificate (ERR_CERT_DATE_INVALID)
This is the most common cause. Either the website's certificate expired, or your device's clock is set to the wrong date.
1 Check your device's date and time
Windows: Right-click the clock in the taskbar → Adjust date/time → Turn on "Set time automatically".
macOS: System Settings → General → Date & Time → Enable "Set time and date automatically".
If your clock was off, reload the page. The error should clear immediately.
2 If your clock is correct — the certificate is expired
The website owner needs to renew their certificate. As a visitor, you can't fix this. You can notify the site owner by finding their contact page or sending an email to their webmaster.
If you own the website: See our SSL Certificate Renewal Guide to renew with your CA or auto-renew via Let's Encrypt.
Fix #2: Untrusted Certificate Authority (ERR_CERT_AUTHORITY_INVALID)
The certificate was issued by a CA that your browser's root store doesn't recognize — typically a self-signed certificate or one from a private/internal CA.
1 Check if it's a self-signed cert
2 If you own the website — replace with a CA-signed certificate
A self-signed certificate is never appropriate for a public website. Get a free Let's Encrypt certificate:
Or use the CSR Generator to create a request for a paid CA certificate.
3 Visitors: check if an intermediate cert is missing
Sometimes the CA is trusted, but the server isn't sending the full certificate chain. The SSL Checker will flag this as "Incomplete chain." The website owner needs to configure their server to include the intermediate certificate.
Fix #3: Name Mismatch (ERR_CERT_COMMON_NAME_INVALID)
The certificate covers a different domain than the one you're visiting. Example: you visited www.example.com but the certificate only covers example.com (or vice versa).
1 Check which domains the certificate actually covers
2 Fix by reissuing the certificate with both names
The website owner needs to reissue the certificate, including both example.com and www.example.com as SANs. See the Name Mismatch Fix Guide for full details.
Browser-Specific Fixes for Visitors
If SSL Checker confirms the server certificate is valid but you still see the error in your browser, these browser-side fixes may help:
Clear SSL State (Chrome)
Clear SSL State (Firefox)
Firefox maintains its own certificate database. Go to Settings → Privacy & Security → Certificates → View Certificates → Servers tab. Look for any manually added exception for the problem domain and delete it. Then clear your cache: Settings → Privacy & Security → Clear Data.
Try a Different Network
Corporate firewalls and some antivirus programs perform HTTPS inspection by intercepting SSL connections and replacing certificates with their own. This can cause ERR_CERT_AUTHORITY_INVALID errors on otherwise valid sites. Try connecting from a mobile network or home Wi-Fi to rule this out.
Temporarily Disable Antivirus HTTPS Scanning
Products like Kaspersky, ESET, Avast, and Bitdefender have HTTPS scanning features that can cause these errors. Look for "Web Shield" or "HTTPS scanning" in your antivirus settings and temporarily disable it for testing. If that fixes the error, add the affected site to the antivirus exclusion list.
If You're the Website Owner
Run a full SSL audit to identify the exact issue:
FAQs
- Can I safely bypass the error and visit the site anyway?
For sites you own or fully trust (like an internal development server), clicking "Advanced → Proceed" is fine. For public sites asking for login or payment info, do not proceed until the certificate issue is resolved. - The error only appears on one browser — is it the browser's fault?
Possibly. Different browsers maintain different certificate trust stores. Chrome/Edge use the OS certificate store; Firefox has its own. If the error only appears in Firefox, check Firefox's Certificate Manager for any conflicting manual exceptions. - Why does this error appear on a site I visited yesterday without issues?
The certificate likely expired between visits (it happens at midnight on the expiry date), or the website owner made a configuration change that introduced a mismatch. Use the SSL Checker to confirm.
Diagnose the exact cause in seconds
Run your domain through the SSL Checker to see exactly what your visitors are seeing — certificate validity, chain completeness, and error codes.