Your Connection Is Not Private Warning
Higher-risk issue — be cautious and consider professional help sooner.
Visitors get a full-page browser warning — "Your connection is not private" — instead of your website, and nearly all of them will turn back rather than click through.
Common signs of this issue
- Instead of your website, visitors see a full-page warning: "Your connection is not private" with a code such as NET::ERR_CERT_DATE_INVALID or NET::ERR_CERT_AUTHORITY_INVALID.
- Safari shows "This Connection Is Not Private" and Firefox shows "Warning: Potential Security Risk Ahead" — same problem, different wording.
- The warning appears on every page of the site, often suddenly, with no changes you made.
- It may affect only one version of your address — for example www.yourdomain.com warns while yourdomain.com loads fine, or the reverse.
- Customers report it by phone or email; traffic, orders, and inquiries drop sharply at the same time.
- Sometimes only one person sees it, on every website they visit — which points at their computer, not your site.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- First, work out who sees it. Try your site from your phone on mobile data and ask someone outside your office. Everyone sees it: your site's certificate. One person sees it, especially on many different websites: their device.
- If it is one person: have them check their computer's date and time. A wrong clock makes valid certificates look expired, and it is the most common cause of one-visitor warnings.
- Write down the exact NET::ERR code from the warning page. DATE_INVALID means expired (or a wrong clock). AUTHORITY_INVALID means the certificate wasn't issued by a recognized authority — often a host's placeholder or self-signed certificate. COMMON_NAME_INVALID means the certificate covers a different name than the one being visited.
- Test both versions of your address — with www and without. If one warns and one doesn't, your certificate covers only one of them, which is a coverage gap rather than an expiry.
- Run your domain through a free online SSL checker (search "SSL checker" — no login needed). It shows the certificate's expiry date, who issued it, and exactly which names it covers — a diagnosis instead of guesswork.
- Think about what changed recently: did the site move hosts, did DNS change, did you put the site behind Cloudflare or change its SSL mode? A site pointed at a new server that has no certificate yet produces exactly this warning.
- Check your email — including spam — for renewal-failure notices from your host or from Let's Encrypt. Certificates renew automatically until one day the renewal quietly fails, and the notice often arrived weeks before the warning did — and if the certificate has simply expired, your host can usually reissue one in minutes.
What this usually means
The warning means the browser could not verify your site's SSL certificate — the small file that proves your site is really yours and encrypts traffic to it. Browsers treat an unverifiable certificate as a possible impersonation and put a wall in front of the page. It does not mean your site was hacked — but visitors can't know that, and the browser actively discourages them from continuing.
When everyone sees it, the causes are mundane: the certificate expired because an automatic renewal silently failed; the certificate covers the wrong name (only www, only non-www, or the host's own placeholder); DNS was recently pointed at a server with no certificate for your domain yet; or, on Cloudflare sites, the SSL mode is mismatched with what the origin server actually has. When one visitor sees it everywhere, their computer's clock is wrong or their network — often corporate or hotel Wi-Fi — is interfering with secure connections.
Treat a site-wide certificate warning as an outage, not a cosmetic issue. In practical terms your website is offline: almost nobody clicks past this screen, and every hour it shows costs you visitors who would have called, booked, or bought. The repair is usually quick and often free — speed, not cost, is what matters.
What not to do
- Don't tell customers to click "Advanced" and proceed past the warning. It trains dangerous habits, looks unprofessional, and some browsers barely allow it anymore.
- Don't panic-buy an expensive certificate before checking with your host — most hosts include free certificates and can reissue one in minutes.
- Don't assume you were hacked. This is a certificate problem in almost every case; treating it as an intrusion wastes the hours that matter.
- Don't change Cloudflare SSL settings at random if you use Cloudflare. The wrong mode trades this warning for redirect loops or an insecure connection; change one thing at a time.
- Don't wait to see if it clears up on its own. An expired certificate stays expired, and the traffic you lose in the meantime doesn't come back.
- Don't trust your own desktop as proof the site is fine — your browser may have an old session or a cached copy. Trust the test from a phone on mobile data.
When to get help
If the SSL checker shows an expired or mismatched certificate and your host's control panel has an obvious renew or reissue option, this may be a ten-minute fix or a single support ticket. Where a professional earns their fee is the murkier cases: a renewal that fails repeatedly, a Cloudflare setup where the visitor-facing and server-side certificates disagree, or a recent migration where DNS, the old server, and the new server are all in play at once. Someone who handles certificates weekly can usually find which layer is presenting the bad certificate within the hour, and — just as valuable — fix the renewal setup so it is the last time. While the warning shows, your site is effectively invisible to customers, so a same-day fix is almost always cheaper than a weekend of lost business.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
What does "Your connection is not private" actually mean?
The visitor's browser could not verify your site's SSL certificate — the file that proves the site's identity and encrypts the connection. Rather than risk an impersonated site, the browser blocks the page behind a warning. It is a certificate problem, not a sign the site was hacked.
What does NET::ERR_CERT_DATE_INVALID mean?
The certificate's dates don't check out — usually it has expired. If one visitor sees this code on many sites, their computer's clock is wrong. If everyone sees it on your site, the certificate expired and needs renewing.
What does NET::ERR_CERT_AUTHORITY_INVALID mean?
The certificate wasn't issued by an authority browsers trust. On small business sites this usually means the server is presenting a self-signed or hosting-company placeholder certificate instead of a real one for your domain — common right after a move to a new server.
What does NET::ERR_CERT_COMMON_NAME_INVALID mean?
The certificate is valid but for a different name than the one being visited — classically it covers yourdomain.com but not www.yourdomain.com, or it belongs to the hosting company's own domain. The fix is a certificate that covers both forms of your address.
How fast do I need to fix this?
Treat it like the site being down: inquiries and sales stop almost completely while the warning shows, because very few visitors click past it. The fix is usually quick — often just a certificate renewal by your host — so same-day action is realistic.