Few things drive visitors away faster than a full-screen browser warning that your connection isn’t private. It usually points to an SSL certificate problem, and the specific cause depends on the error code shown. Let’s work through the common ones.
The certificate hasn’t been issued yet
On a new site or domain, the most common cause is simply that AutoSSL hasn’t issued the certificate yet. In cPanel, open SSL/TLS Status, find your domain, and if it lacks a green padlock, tick it and click Run AutoSSL. Within a few minutes the certificate issues and the warning clears.
The certificate has expired
Certificates expire, and if auto-renewal failed, the browser flags it. AutoSSL renews Let’s Encrypt certificates automatically, so an expired certificate usually means renewal was blocked — often by a DNS misconfiguration or a stray redirect. Re-run AutoSSL and, if it fails, note the error it reports.
Name mismatch (wrong domain on the certificate)
If the error mentions the certificate is for a different site, the certificate doesn’t cover the exact address being visited — commonly the www version isn’t included, or a subdomain like mail. or shop. is missing. Make sure every hostname you use is listed in SSL/TLS Status and covered by AutoSSL.
Mixed content after installing SSL
Sometimes the certificate is fine but the site still isn’t fully secure because some resources load over plain HTTP. That’s mixed content — our SSL guide covers the search-and-replace fix to update those old URLs to HTTPS.
Clock and cache issues on the visitor’s end
Occasionally the problem is on the visitor’s device: a wrong system clock makes valid certificates look expired. If only one person sees the warning while everyone else is fine, ask them to check their date and time and clear their browser cache.
Force HTTPS once it’s working
With a valid certificate in place, add an .htaccess redirect to send all traffic to HTTPS so nobody lands on an insecure version and gets the warning unnecessarily.
If AutoSSL keeps failing to issue or renew, there’s usually a DNS or redirect issue blocking the validation. Send us the error message from SSL/TLS Status and we’ll clear the path so the certificate issues cleanly.
