You open your own website and, instead of your homepage, you see a full-screen warning: “Your connection is not private.” Visitors see the same thing, and most of them leave immediately. Every hour it stays broken costs you visitors, leads and trust.
The good news: this error is almost always caused by your site’s SSL certificate, the small file that gives you the padlock and “https”. It’s usually fixable in 10 to 30 minutes from your hosting dashboard, without a developer.
The quick answer: the certificate is missing, expired, or doesn’t match the exact address people are visiting. Find out which (the error code tells you), then reissue or fix the certificate in your host’s SSL settings.
First, check whether it’s just you
Before changing anything, rule out a problem on your own device:
- Check your computer’s date and time. If your clock is wrong, every certificate can look expired. Set the date and time to update automatically.
- Open the site on your phone using mobile data, not office Wi-Fi. If it works there, the problem is your network or device, not the website.
- Try a private or incognito window to rule out an old cached version.
- Run a free online test. Enter your domain at an SSL checker such as SSL Labs (ssllabs.com/ssltest) or WhyNoPadlock. It shows whether the certificate exists, when it expires and which domain names it covers.
If the online test shows a problem, it’s your website. Keep reading.
Read the error code: it tells you the cause
On the warning page, look for the small code under the message. In Chrome and Edge, click Advanced to see more detail. In Firefox, the page says “Warning: Potential Security Risk Ahead” and shows a code after you click Advanced.
| Error code | What it means | Most likely cause |
| NET::ERR_CERT_DATE_INVALID | The certificate has expired, or isn’t valid yet | Auto-renewal failed, or the visitor’s clock is wrong |
| NET::ERR_CERT_COMMON_NAME_INVALID (Firefox: SSL_ERROR_BAD_CERT_DOMAIN) | The certificate is for a different address | It covers yourdomain.com but not www.yourdomain.com, or the reverse |
| NET::ERR_CERT_AUTHORITY_INVALID | The browser doesn’t trust who issued the certificate | A self-signed or default host certificate, or a missing intermediate certificate |
| ERR_SSL_PROTOCOL_ERROR or ERR_SSL_VERSION_OR_CIPHER_MISMATCH | The secure connection couldn’t be set up at all | No certificate installed, or old SSL settings on the server |
Write down the code you see, then jump to the matching fix below.
How to fix each cause
Fix 1: The certificate expired (ERR_CERT_DATE_INVALID)
Most hosts give you a free Let’s Encrypt certificate that renews automatically every few months. When renewal fails, often because DNS changed or the domain briefly pointed somewhere else, the certificate quietly expires.
- Log in to your hosting dashboard and open the SSL/TLS or Security In cPanel, it’s SSL/TLS Status or AutoSSL.
- Find your domain and click Renew, Reissue or Run AutoSSL.
- Wait 5 to 15 minutes, then reload your site in a private window.
If renewal fails again, the error message usually says why. The most common reason is that the domain’s DNS doesn’t point to this host. Check the A record, as explained in domain, hosting and DNS explained, or ask your host’s support to reissue it.
Fix 2: The certificate doesn’t cover the address (ERR_CERT_COMMON_NAME_INVALID)
A certificate lists the exact names it’s valid for. If it covers yourdomain.com but someone visits www.yourdomain.com, the browser shows this error.
- In your host’s SSL section, reissue the certificate and make sure both versions are included: with and without www.
- If you added a subdomain, like shop.yourdomain.com, include that too, or issue a separate certificate for it.
- Pick one main version (with or without www) and redirect the other to it. Most hosts have a setting for this, and in WordPress the address under Settings → General should match.
Fix 3: The browser doesn’t trust the certificate (ERR_CERT_AUTHORITY_INVALID)
This usually means the site is showing a self-signed or default server certificate instead of a real one, or the certificate was installed without its intermediate (chain) certificate.
- If you’re on a host with free SSL, delete the old certificate in the SSL section and issue a fresh Let’s Encrypt
- If you bought a certificate, reinstall it and paste the full CA bundle (chain) that came with it, not just the main certificate.
- Run the SSL Labs test again. It flags “chain issues” clearly.
Fix 4: No certificate at all, or a protocol error
If the site never had SSL, or you’ve just moved hosts, the new server may not have a certificate yet. Hosts can only issue a free certificate after the domain points to them, so:
- Confirm the domain’s DNS points to the new host.
- Turn on the free SSL in the host’s dashboard.
- Wait a few minutes and test again.
Just moved your site? This is the most common cause. Our guide to moving a WordPress site without downtime covers SSL right after the switch.
Fix 5: You use Cloudflare
If your site runs through Cloudflare, two certificates are involved: one between visitors and Cloudflare, and one between Cloudflare and your host.
- In Cloudflare, open SSL/TLS → Overview and choose Full (strict) if your host has a valid certificate, which is the most secure option, or Full while you fix the host’s certificate.
- Make sure the DNS records for your domain and www are Proxied (orange cloud), so Cloudflare’s own certificate covers them.
- Avoid Off, and don’t use Flexible long-term. Flexible often causes redirect loops on WordPress and leaves the connection to your server unencrypted.
What about “Not secure” instead of the full warning?
If the site opens but the address bar says “Not secure” or the padlock has a warning, the certificate is fine. Some images, scripts or links on the page still load over plain “http://”. This is called mixed content. In WordPress, update Settings → General so both addresses start with https, and replace old http links in your content. A search-and-replace plugin can do this in one go, after you’ve taken a backup.
After the fix
- Test in a private window on a laptop and on your phone using mobile data.
- Run SSL Labs again. An “A” grade means the certificate and chain are correct.
- Clear caches: your caching plugin, your host’s cache and Cloudflare’s cache if you use it.
- Check both addresses: with and without www, plus any subdomains you use.
- Open Google Search Console and check the HTTPS report under Experience over the next week. It should show all your pages as HTTPS.
How to stop it happening again
Certificates are getting shorter lives. Under rules agreed by the CA/Browser Forum, the group of browser makers and certificate issuers, the maximum validity of public SSL certificates dropped to 200 days in March 2026, falls to 100 days in 2027 and reaches 47 days by 2029. That means renewing by hand is no longer realistic. Renewal has to happen automatically.
- Use your host’s free auto-renewing SSL (Let’s Encrypt or similar) instead of a manually installed certificate, where possible.
- Don’t break renewal by accident. Renewals fail most often after DNS changes, so after moving hosts or editing DNS, check your SSL status the same day.
- Set up an expiry alert. Free uptime monitors such as UptimeRobot can warn you by email before a certificate expires.
- Keep the www and non-www versions on the same certificate, and redirect one to the other.
- Pick a host that handles SSL for you. Most good hosts now issue and renew certificates automatically. See our guide to the best web hosting for small business websites.
SSL is just one part of keeping a site safe. For the rest, see our small business cybersecurity checklist.
Related guides: WordPress Troubleshooting: How to Fix the Most Common Errors · How to Fix “There Has Been a Critical Error on This Website” in WordPress · How to Fix the “500 Internal Server Error” in WordPress
FAQ
Why does my site say “Your connection is not private”?
Almost always because of its SSL certificate: it has expired, it doesn’t cover the exact address being visited (for example the www version), it isn’t trusted, or it isn’t installed. Occasionally the visitor’s device clock is wrong. The error code under the warning tells you which.
Is my website hacked if it shows this error?
Usually not. It’s normally a certificate problem, not a hack. But treat it as urgent, because visitors can’t tell the difference, and most will leave.
How long does it take to fix?
With a free host certificate, reissuing usually takes 5 to 15 minutes. If you’ve just changed DNS or hosts, it can take up to a few hours, until the domain fully points to the new server and the host can issue the certificate.
Do I need to buy an SSL certificate?
No, not for most small business sites. Free Let’s Encrypt certificates are trusted by all major browsers and give the same padlock and encryption. Paid certificates mainly add business verification and support.
Will this error hurt my Google rankings?
A short outage fixed within hours shouldn’t cause lasting harm. If it lasts for days, visitors leave, Google can’t load the secure version of your pages, and rankings can drop. Fix it quickly, then check Search Console.
Final word
“Your connection is not private” looks alarming, but on your own site it usually comes down to one of four things: an expired certificate, a missing www version, an untrusted certificate, or no certificate after a move. Read the error code, reissue or fix the certificate in your host’s SSL settings, check Cloudflare’s SSL mode if you use it, and test again in a private window.
Then make sure renewal is automatic and set up an expiry alert, because with certificates getting shorter lives every year, automation is what keeps this warning from coming back.


