SSL errors: what the browser message means and how to fix it
In short
An SSL error means the browser could not connect to the site securely. The error code shown with the message tells you what exactly is wrong: the certificate has expired, it was issued for a different address, it comes from an unknown issuer, or the server does not answer with an encrypted connection. Find your code in the table and open the guide with the cause and the fix.
List of SSL errors: message, code and guide
| Message or error code | What is wrong | Guide |
|---|---|---|
| “Your connection is not private” (Chrome) “Be careful. Something doesn’t look right.” (Firefox) | the browser could not confirm the site's certificate; the error code shown with the warning gives the cause | Your connection is not private |
NET::ERR_CERT_DATE_INVALID(Firefox: SEC_ERROR_EXPIRED_CERTIFICATE) | the certificate has expired (or the visitor's device clock shows the wrong date) | SSL certificate expired |
| “Your clock is ahead” or “Your clock is behind” (Chrome) | the date or time on the computer or phone is wrong, so the browser cannot check website certificates | Your clock is ahead |
NET::ERR_CERT_COMMON_NAME_INVALID(Firefox: SSL_ERROR_BAD_CERT_DOMAIN) | the certificate was issued for a different address, e.g. only for example.com while the site opens as www.example.com | SSL_ERROR_BAD_CERT_DOMAIN |
NET::ERR_CERT_AUTHORITY_INVALID(Firefox: SEC_ERROR_UNKNOWN_ISSUER or MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT) | the browser does not recognize the issuer: a self-signed certificate, a test certificate or missing intermediate certificates | NET::ERR_CERT_AUTHORITY_INVALID |
ERR_SSL_PROTOCOL_ERROR“This site can’t provide a secure connection” (Chrome) | the server sent a reply the browser cannot understand as an encrypted connection; usually it is plain http on port 443 | SSL protocol error |
ERR_SSL_VERSION_OR_CIPHER_MISMATCH | the server supports only old encryption versions (e.g. TLS 1.0 and 1.1) that browsers no longer use | SSL protocol error |
SSL_ERROR_RX_RECORD_TOO_LONG“Secure Connection Failed” (Firefox) | on port 443 the server answers with plain http, because SSL is not enabled for the domain | SSL_ERROR_RX_RECORD_TOO_LONG |
| the page opens over https://, but looks broken or has no padlock | the page loads images, scripts or styles over http:// (mixed content) | Mixed content |
Where to find the error code
In Chrome the code (e.g. NET::ERR_CERT_DATE_INVALID) is shown right below the description of the warning. Edge shows the same codes. In Firefox click “Advanced”: the code is at the bottom of the expanded section, after the words “Error code”.
If the error is on someone else's website
- Do not enter passwords, card details or personal data on it.
- Check the date and time on your computer or phone. A wrong date makes every certificate look expired or not yet valid (how to fix the clock).
- In hotels, on trains or in cafés, sign in to the Wi-Fi network first, then open the page again.
- If the warning does not go away, let the site owner know. You cannot fix a server-side error yourself.
If it is your website
- Enter the site's address in the certificate checker. It shows when the certificate expires, who issued it, which names it covers and whether browsers trust it. No account needed.
- Open the guide for your error code from the table above: each one explains the causes and the fix step by step.
- If you need a new certificate, generate one for free in the generator (a free account is required) and install it with the guide for your hosting.
How to avoid certificate errors
- The most common cause is an expired certificate. When you save a certificate in your freessl.pl account, we send a reminder by email after two thirds of its validity and another one a week before it ends.
- Always upload the full chain (
fullchain.pem). Missing intermediate certificates can go unnoticed in a desktop browser, while on some phones and in apps the site then does not work. - Issue the certificate for all of the site's addresses, e.g.
example.comandwww.example.com.