“Your Connection Is Not Private” on Your Site: Fix SSL Errors
Visitors see “Your connection is not private” on your site? Learn what the SSL error codes mean and how to fix expired, mismatched or untrusted certificates.
A customer calls and says your website shows a red warning: “Your connection is not private.” It sounds like a hack, but it rarely is. The warning means the visitor's browser could not confirm your site's SSL certificate, the small file that proves the site is yours and lets the connection be encrypted. The code under the warning, such as NET::ERR_CERT_DATE_INVALID, tells you why. Below are the common codes, the fix on your side, and quick checks for when only one visitor sees it.
What the warning actually means
Each time someone opens your site over HTTPS, the browser checks three things about the certificate. Is it within its valid dates? Does it name the exact address the visitor typed? Was it issued by an authority the browser trusts? If any answer is no, the browser shows the warning instead of your page.
Chrome says “Your connection is not private.” Edge says “Your connection isn't private.” Firefox says “Warning: Potential Security Risk Ahead.” Safari says “This Connection Is Not Private.” The cause is the same. In Chrome, the error code appears under the message, and clicking Advanced shows more detail.
First check: is it your site or one device?
Find out who sees it:
- Open the site on your own phone over mobile data, not office Wi-Fi.
- Try another browser on a different computer.
- Ask the customer which exact address they opened, with or without
www.
If everyone sees it, the problem is on the server and the fixes below apply. If only one person sees it, jump to the section on single visitors.
Common error codes and how to fix them
| Error code (Chrome) | What it usually means | Your fix |
|---|---|---|
NET::ERR_CERT_DATE_INVALID | The certificate has expired | Renew or reissue it |
NET::ERR_CERT_COMMON_NAME_INVALID | The certificate does not cover this address | Issue a certificate that includes the name |
NET::ERR_CERT_AUTHORITY_INVALID | Self-signed or untrusted issuer | Replace it with a trusted certificate |
NET::ERR_CERT_DATE_INVALID: the certificate has expired
Certificates are valid for a fixed period. When it ends, every visitor sees the warning at once. Automatic renewal usually prevents this, but it can fail quietly, for example when the domain's DNS records point somewhere else and the issuer cannot confirm you control the domain.
The fix: in your hosting control panel, open the domain's SSL/TLS certificates and check the expiry date, then reissue the certificate. If renewal fails, make sure the domain and its www version point to your hosting, then try again.
NET::ERR_CERT_COMMON_NAME_INVALID: the name does not match
The certificate is valid, but it was issued for a different address. Common cases are a certificate that covers example.com but not www.example.com, or a new subdomain that never got a certificate.
For example, a clinic in Skopje adds a booking subdomain, such as booking.example.com, for a new appointment system. The main site works, but patients who open the booking link see the warning, because the certificate only covers the main domain and www.
The fix: issue a certificate that lists every name you use, including the www alias and each subdomain.
NET::ERR_CERT_AUTHORITY_INVALID: self-signed or untrusted issuer
A self-signed certificate is one the server made for itself. It encrypts traffic, but no trusted authority vouches for it, so browsers reject it. The same error can appear when the server sends the certificate without its intermediate certificates, the links that connect it to a trusted authority.
The fix: replace it with a certificate from a trusted authority, such as a free Let's Encrypt certificate. If you installed a paid certificate by hand, install the full chain, not just the certificate file.
Cloudflare SSL mode set wrongly
If your site uses Cloudflare, a network that sits between visitors and your server, there are two connections: visitor to Cloudflare, and Cloudflare to your server. Cloudflare offers four SSL/TLS modes: Off, Flexible, Full and Full (strict). They mainly control the second connection. In Full (strict) mode, Cloudflare checks your server's certificate. If that certificate is expired or self-signed, visitors see Cloudflare's error 526 page instead of your site.
Fix the certificate on your server rather than lowering the mode. Switching to Flexible hides the error but leaves the connection between Cloudflare and your server unencrypted, and it can cause redirect loops. Cloudflare's standard certificate covers your domain and one level of subdomain, so an address like shop.eu.example.com needs extra coverage.
When only one visitor sees the warning
If your site works everywhere else, the cause is usually on the visitor's side. Three quick checks solve most cases:
- Date and time. If the device clock is wrong, a valid certificate can look expired or not yet valid. Ask the visitor to turn on automatic date and time, then reload.
- Antivirus HTTPS scanning. Some security software inspects encrypted traffic by placing its own certificate in the middle. If that goes wrong, many sites show warnings. Turning off HTTPS or SSL scanning for a moment shows whether this is the cause.
- Public Wi-Fi. Hotel, café and airport networks often show a sign-in page first. Until the visitor signs in, the network intercepts secure sites and the browser may show the warning. Sign in to the Wi-Fi, then try again.
Never click “proceed anyway” on logins or payments
Browsers let you click through the warning. Do not do it, and do not tell customers to do it, on any page that asks for a password, card details or personal data. The warning appears because the browser cannot prove who is on the other end. On a public network, that could be someone reading everything you type. Fix the certificate first, then let people log in or pay.
This guide covers certificate errors only, not mixed content warnings, where a secure page loads images or scripts over plain HTTP. For the difference between free and paid certificates, see our free SSL page. Our help center has a step-by-step guide to installing a free Let's Encrypt certificate.
How Zebra Hosting handles SSL for you
On our hosting, every domain gets a free SSL certificate. We issue and install it while your hosting is set up, and it renews automatically before it expires. Cloudflare CDN and DDoS filtering sit in front of every hosted site: copies of your pages are served close to your visitors, and floods of fake traffic are blocked. If a warning or a 526 error still appears, open a ticket and our team will look at it with you, in Albanian, English or any of our 17 support languages. You can compare plans on our hosting page.