Common SSL Certificate Errors and How to Fix Them

When a browser cannot verify a website’s SSL certificate, it shows a full-page warning such as “Your connection is not private”. Most visitors will leave immediately. The good news is that most SSL errors have a small number of common causes.

Before troubleshooting

• Check the exact error message and code shown by the browser.
• Test in another browser and on another device or network.
• Use an online SSL checker to inspect the certificate chain and expiry date.

1. Certificate has expired

Typical message: NET::ERR_CERT_DATE_INVALID or “certificate has expired”.

Fix: Renew or reissue the certificate. For free certificates in cPanel, run AutoSSL again from SSL/TLS Status. If renewal keeps failing, check that your domain still points to the correct server. See installing a free SSL certificate in cPanel.

2. Certificate name does not match the domain

Typical message: NET::ERR_CERT_COMMON_NAME_INVALID or “certificate is not valid for this domain”.

Causes:

• The certificate covers yourdomain.com but not www.yourdomain.com, or the other way round
• A subdomain is not included
• The domain is pointing to a server hosting a different website’s certificate

Fix: Reissue the certificate to include every hostname you use, or choose a wildcard or multi-domain certificate. Confirm DNS points to the correct hosting account.

3. Certificate is not trusted

Typical message: NET::ERR_CERT_AUTHORITY_INVALID.

Causes: a self-signed certificate, a missing intermediate certificate, or a certificate from an untrusted issuer.

Fix: Install a certificate from a trusted certificate authority and make sure the full certificate chain, including intermediate certificates, is installed. An SSL checker will show if the chain is incomplete.

4. Mixed content warnings

Symptom: the site loads over HTTPS but the padlock is missing or some elements are broken.

Fix: Update resources that load over HTTP. Follow our guide to fixing mixed content.

5. Too many redirects

Typical message: ERR_TOO_MANY_REDIRECTS.

Causes: conflicting HTTPS redirect rules in .htaccess, a plugin, the WordPress settings, or a CDN or proxy.

Fix: Use one method to force HTTPS. Temporarily disable redirect plugins, check your .htaccess rules and CDN SSL settings. See how to force HTTPS correctly.

6. Outdated protocol or cipher

Typical message: ERR_SSL_VERSION_OR_CIPHER_MISMATCH.

Fix: The server must support modern TLS versions. This is a server configuration issue; contact your hosting provider.

7. Wrong date on the visitor’s device

If only one person sees the error, check that their device’s date and time are correct. An incorrect clock can make valid certificates appear expired or not yet valid.

Quick troubleshooting table

Final thoughts

Most SSL errors come down to expiry, missing hostnames, an incomplete chain or redirect conflicts. If you have tried these steps and the warning remains, contact Salama Hosting support with a screenshot of the error.