Contents
Chrome's "Your connection is not private", Firefox's "Warning: Potential Security Risk Ahead" and Safari's "This Connection Is Not Private" all say the same thing: the browser could not trust the site's SSL certificate. Most visitors leave at this screen, and an online store stops selling. This article shows how to tell whether the problem is on your site or on the visitor's device, and how to fix each cause.
The error code tells you the cause
Click Advanced on the warning screen to see an error code. The most common ones:
| Error code | Meaning | Where? |
|---|---|---|
| NET::ERR_CERT_DATE_INVALID | The certificate has expired, or the device clock is wrong | Usually the site, sometimes the device |
| NET::ERR_CERT_COMMON_NAME_INVALID | The certificate was not issued for this address | The site |
| NET::ERR_CERT_AUTHORITY_INVALID | The certificate was not signed by a trusted authority, or the intermediate certificate is missing | The site |
| ERR_SSL_PROTOCOL_ERROR | The server and browser could not agree on a secure connection | The site, or a network device in between |
First find out where the problem is
Open the site from another device and over mobile data. If the error appears on one device only, the problem is that device: the date and time may be wrong, an old operating system may not know current root certificates, or an antivirus or company network may be intercepting HTTPS traffic. If every device shows the error, the problem is your site; read the causes below.
Cause 1: The certificate has expired
This is the most common cause, and it will happen more often: since March 15, 2026, certificates are valid for at most 200 days, and the limit keeps shrinking (our news on SSL certificate lifetimes). The free certificate in your hosting account normally renews by itself. If it has not, open SSL/TLS Status in cPanel and click Run AutoSSL. If the renewal fails, the page says why; usually it is the DNS problem below.
Cause 2: The certificate does not cover this name
If the certificate was issued for example.com but the visitor comes to www.example.com or shop.example.com, the browser warns. The fix is a certificate that covers every name in use: for the free certificate, the subdomain's DNS record only has to point to the server; for many subdomains, a wildcard SSL may fit.
Cause 3: The domain points to another server
The free certificate is issued after verifying that the domain points to your hosting server. If the A record points to an old server or a CDN, validation fails and the certificate is not renewed. Check your domain's A and AAAA records. A forgotten AAAA (IPv6) record is the most often missed cause.
Cause 4: The intermediate certificate is missing
If you installed a paid certificate by hand, you also have to install the intermediate certificate (CA bundle) sent by the certificate authority. When it is missing, some browsers open the site and some do not, which makes it hard to notice. In cPanel, fill in the "Certificate Authority Bundle" field under SSL/TLS > Install and Manage SSL for your site.
A padlock but a different warning: mixed content
If the page opens but the address bar says "not secure" or shows a padlock with a warning, the certificate is fine; the page loads an image, script or font over http://. In WordPress, check that the site address starts with https:// and update old addresses in the content.
Test it yourself
- Click the padlock in the browser and check who the certificate was issued to and until when.
- On your computer, this command shows the certificate the server sends and its expiry date:
openssl s_client -connect example.com:443 -servername example.com </dev/null | openssl x509 -noout -subject -enddate
Do not ask visitors to "proceed anyway"
The "proceed to site" link on the warning screen technically opens the site, but asking visitors to use it is wrong: the same screen also appears during a real attack. Fix the problem at the source and make sure certificate renewals happen automatically.
Fiberserver hosting plans include free SSL with automatic renewal. If you need organization validation or a wildcard, see our SSL certificates, and send any error you cannot solve to support together with its error code.

Comments0
No Comments Yet
Be the first to share your thoughts.
Please sign in or sign up to leave a comment.