How to Fix Common SSL Certificate Errors

SSL certificate errors show visitors a scary “Not Secure” or “Your connection is not private” warning — and many people leave the moment they see one. The good news is that these errors usually come from a few common, fixable causes. Here is how to diagnose and clear them.

Error: certificate has expired

Certificates are valid for a limited time. If yours lapsed, simply reissue it. Free Let’s Encrypt certificates renew automatically, so if one expired, reinstall it — see installing a Let’s Encrypt SSL certificate.

Error: name mismatch

This means the certificate does not cover the exact address being visited — often the www version is missing, or you are visiting via the server hostname. Reissue the certificate covering both yourdomain.com and www.yourdomain.com.

Error: “Not Secure” despite having a certificate (mixed content)

Your certificate is fine, but some images or scripts still load over insecure http. Fixing those links clears the warning — follow fixing SSL mixed content issues.

Error: site loads on http but not https

The certificate may not be installed, or traffic is not being redirected. Install the certificate, then force HTTPS redirect in cPanel. WordPress users should also enable SSL in WordPress.

Still stuck?

Clear your browser cache and test in a private window first, since browsers cache certificates. If the error persists across devices, open a support ticket and we will check the certificate on the server.

Frequently asked questions

Why does only my browser show the error?

It may be a cached certificate or your device’s clock being wrong. Clear the cache, correct the time, and test elsewhere.

How long do SSL certificates last?

Let’s Encrypt certificates last 90 days and renew automatically. Paid certificates typically last a year and must be renewed manually.

Do I need a new certificate for a subdomain?

Yes — each subdomain needs coverage, either its own certificate or a wildcard. See SSL certificate types.