blog

"Your Connection Is Not Private" on Your Site: How to Fix It

Visitors see Chrome's privacy warning on your site? Read the error code, then fix the expired, mismatched or untrusted SSL certificate behind it.

6 min readFixesSslDomains

A client writes: "Your site says my connection is not private." You open it and see a full-page warning instead of the homepage. Visitors leave, and payment forms stop working, because almost nobody clicks past it.

This guide is for the person who runs the site, yours or a client's. The warning comes from the site's SSL certificate, and Chrome tells you exactly which part failed. Below: how to read that, then the fix for each case on your own server, Vercel, Netlify and Cloudflare.

What your visitors see

In Chrome, the tab is titled "Privacy error" and the page says:

Your connection is not private

Attackers might be trying to steal your information from example.com (for example, passwords, messages, or credit cards).

Just below that paragraph, Chrome shows the error code in small letters, for example NET::ERR_CERT_DATE_INVALID. Click Advanced to see the explanation in words, such as "its security certificate expired 3 days ago", and, in most cases, a link "Proceed to example.com (unsafe)". If your site uses HSTS, there's no such link: Chrome says "You cannot visit example.com right now because the website uses HSTS", and nobody gets in until the certificate is fixed.

The wording here is from Chrome's own interface text. Google's help page, Fix connection errors, lists these errors for visitors.

Find your error code

Ask the person who reported it for a screenshot, or open the site yourself in a private window. Then match the code:

  • NET::ERR_CERT_DATE_INVALID: the certificate has expired, or the visitor's clock is wrong. Renew it, as in "Certificate expired" below.
  • NET::ERR_CERT_COMMON_NAME_INVALID: the certificate is for a different name, such as example.com instead of www.example.com. Add the name, as in "Certificate doesn't match the name".
  • NET::ERR_CERT_AUTHORITY_INVALID: Chrome doesn't trust whoever signed the certificate. Fix the chain, as in "Certificate not trusted".

Before you dig in, make sure your host isn't having a wider problem: Vercel's live status shows whether it's them. Not sure the site is down for everyone? Here's how to check if a website is down.

Certificate expired (NET::ERR_CERT_DATE_INVALID)

When the SSL certificate on your website has expired, every visitor gets the warning at once. Certificates last a fixed time and must be replaced before the end date.

On your own server with Let's Encrypt and Certbot. Let's Encrypt certificates last 90 days by default, and it recommends renewing every 60 days. Certbot usually sets up automatic renewal when you install it. From Certbot 4.0.0, it renews a certificate when less than a third of its lifetime is left. To find out what went wrong:

  1. See which certificates exist and when they expire: sudo certbot certificates.
  2. Check that renewal is scheduled: look for certbot renew in systemctl list-timers or in your crontab.
  3. Try a renewal without changing anything: sudo certbot renew --dry-run.
  4. Renew for real: sudo certbot renew.

If the dry run fails, its message names the problem, often a domain that no longer points to this server. If renewal works but browsers still see the old date, your web server is still using the old certificate: reload it, and add a --deploy-hook so Certbot does that after every renewal.

On Vercel, Netlify or Cloudflare. All three issue and renew certificates for you, but each renewal must prove again that you control the domain. That fails when:

  • The domain moved. DNS now points somewhere else, or only some records were moved. Vercel renews 14 to 30 days before expiry and asks you to keep the domain correctly configured; check the status in the project's Settings, then Domains. Netlify also needs your DNS set up before it can include a domain on the certificate.
  • A proxy is in the way. Vercel's docs say to route /.well-known/acme-challenge/* to Vercel without caching, redirects or authentication, or to set Cloudflare to "DNS only" for that record.
  • A CAA record blocks it. A CAA record lists which authorities may issue certificates for your domain. If it exists and doesn't allow Let's Encrypt, both Vercel and Netlify fail. Vercel's docs give 0 issue "letsencrypt.org" as the record to add. With Universal SSL, Cloudflare adds the CAA records it needs automatically once you add any CAA record.

Vercel also notifies team owners with a "Certificate renewal failed" notification, so look for it. Certificates you upload yourself are never renewed automatically on Vercel or Netlify.

Certificate doesn't match the name (NET::ERR_CERT_COMMON_NAME_INVALID)

The certificate is valid, but not for the address the visitor typed. Chrome says the server "could not prove that it is www.example.com; its security certificate is from example.com". The classic case is a certificate for example.com but not www.example.com, or the reverse.

  • Certbot: add the missing name to the existing certificate with certbot --expand -d example.com -d www.example.com.
  • Vercel: add both example.com and www.example.com to the project, with the DNS records shown for each in Settings, then Domains.
  • Netlify: the certificate includes your domain aliases, but only those whose DNS was already set up when it was issued. So set up DNS for every alias first, as Netlify's docs ask.
  • Cloudflare: Universal SSL covers the root domain and first-level subdomains, like www.example.com. A deeper name such as dev.app.example.com needs Total TLS or an advanced certificate.

Connecting a domain to an app builder? Our guide to a Lovable custom domain that isn't working covers the www and DNS side.

Certificate not trusted (NET::ERR_CERT_AUTHORITY_INVALID)

Chrome says the certificate "is not trusted". Two causes cover most sites:

  • A self-signed certificate. Fine for testing, never for visitors. Replace it with one from Let's Encrypt or your host.
  • A missing intermediate certificate. Your server sends its own certificate but not the chain that links it to a trusted authority. Certbot's guide says Nginx and Apache 2.4.8 or newer need fullchain.pem, not cert.pem; with cert.pem alone, some browsers show the error "some of the time". Point your server at fullchain.pem and reload it.

When it's only one visitor

If the site opens fine for you and on a phone over mobile data, the problem is on the visitor's side:

  • A wrong clock. Certificates are valid only between two dates. Chrome may show "Your clock is behind" or ask whether the computer's date looks right. Setting the time automatically fixes it.
  • Antivirus or a network filter that inspects HTTPS. Chrome may show "An application is stopping Chrome from safely connecting to this site". A Wi-Fi sign-in screen that interrupts the connection can cause the warning too.

Check every client site at once

One expired certificate rarely comes alone: the same setup mistake often sits on other client sites. Paste up to 50 domains into our free SSL expiry checker to see each certificate's expiry date and days left. The domain expiry checker does the same for domain registrations, which cause their own outages when they lapse.

Get warned before it expires

Pingbuddy reads each site's certificate once a day and warns you 14, 7 and 1 day before it runs out, through your usual alerts (Telegram and email on every plan). The same goes for the domain itself. These warnings are on every plan, including Free (5 sites). If a certificate breaks anyway, the regular check fails and the alert says it's a security certificate problem, so you hear about it before your client does.

Looking after many client sites? Pingbuddy for agencies watches up to 300, with a table of every SSL and domain date.

FAQ

Why does my website say "Your connection is not private"?
Chrome checked your site's SSL certificate and it failed: it has expired, it doesn't cover the address the visitor typed (often www vs no www), or it isn't signed by an authority Chrome trusts. The error code under the warning, such as NET::ERR_CERT_DATE_INVALID, tells you which one.
My hosting renews certificates automatically. Why did mine expire?
Automatic renewal still needs to prove you control the domain. If the domain's DNS was moved, a proxy blocks the validation request, or a CAA record doesn't allow Let's Encrypt, renewal fails quietly until the old certificate runs out. Vercel and Netlify both list these as causes.
Only one person sees the warning. Is my site broken?
Probably not. If the site opens normally on other devices and networks, check that person's date and time, and any antivirus or network filter that inspects HTTPS traffic. Chrome shows a separate page when it detects either.
How do I know before a certificate expires?
Use a monitor that reads the certificate's expiry date. Pingbuddy warns you 14, 7 and 1 day before a certificate or domain runs out, on every plan including Free. To check up to 50 sites once, paste them into the free SSL expiry checker.

Run a free Pingbuddy checkup on any site: see whether it answers and how fast, when its SSL certificate and domain expire, and whether secret keys are visible in its public code.

Run free checkup →