Skip to content
webfixed

Guides / General

"Your connection is not private" on my own website

By Michael Broadbridge. Last checked 14 November 2026 on Chrome, Safari and Edge.

Short answer

Click Advanced on the warning and read the error code. NET::ERR_CERT_DATE_INVALID usually means the SSL certificate has expired. NET::ERR_CERT_COMMON_NAME_INVALID means it does not cover the address you typed, often the www version. NET::ERR_CERT_AUTHORITY_INVALID means it is not from a trusted issuer. Renew or reissue the certificate where your site is hosted.

Symptoms

You may see one of these messages:

Your connection is not private

Privacy error

NET::ERR_CERT_DATE_INVALID

NET::ERR_CERT_COMMON_NAME_INVALID

NET::ERR_CERT_AUTHORITY_INVALID

Your clock is behind

Your clock is ahead

  • A full-page warning appears instead of your website, and the browser tab says Privacy error.
  • The page says "Your connection is not private" in Chrome, or shows a similar warning in Edge or Safari.
  • The warning appears on the www version of your address but not the other, or the other way round.
  • Customers say they cannot reach the site, or the warning appears on your device only.

Causes, most likely first

  1. The certificate has expired

    Certificates have an end date. Let’s Encrypt certificates, which many hosts use, last 90 days by default and are meant to renew automatically, so an expiry usually means the renewal failed.

  2. The certificate does not cover the address

    A certificate lists the exact names it is valid for. If it covers yourbusiness.co.uk but not www.yourbusiness.co.uk, visitors to the www address see the warning.

  3. The domain points to a host that has not issued a certificate for it

    After a move to a new host or platform, the domain may still point at the old server, or the new one may not have issued a certificate yet. The server then presents a certificate for a different name, or none that matches.

  4. The certificate is self-signed or not from a trusted issuer

    The server may be presenting a self-signed certificate, or one from an issuer the browser does not recognise. Browsers do not accept either for a public website.

  5. The problem is on the visitor’s device

    A wrong date or time on the device, antivirus software that scans secure connections, a work network proxy or a public Wi-Fi sign-in page can all trigger the warning on a site that is working.

How to fix it

Read the error code

  1. Open your site in Chrome. On the warning page, click Advanced.
  2. Read the sentence that starts "This server could not prove that it is" followed by your domain. It says why, for example that the certificate expired a number of days ago, or that it is from a different domain.
  3. Note the error code, which starts with NET::ERR_CERT.
  4. Try the address with and without www, and note which ones show the warning.
  5. Open the site on a phone using mobile data rather than your Wi-Fi. If the warning only appears on one device or network, go to the last part of this guide.

What each code means for a site owner

  • NET::ERR_CERT_DATE_INVALID. The certificate has expired or, less often, is not valid yet. If every visitor sees it, renew the certificate. Chrome also shows this code when the visitor’s clock is wrong.
  • NET::ERR_CERT_COMMON_NAME_INVALID. The certificate was issued for a different name from the one in the address bar. Usually the certificate is missing the www or the bare version of the domain, or the domain is pointing at a server that holds a certificate for another site.
  • NET::ERR_CERT_AUTHORITY_INVALID. The certificate is self-signed or from an issuer the browser does not trust. On your own site, check that the host has installed a certificate from a recognised issuer, such as Let’s Encrypt. On a work network, a proxy can also cause it.

Fix the certificate where it is issued

The certificate is issued by whoever hosts the site, not by the browser. Shopify, Wix and Squarespace issue certificates automatically for domains that are connected correctly. On WordPress, the certificate is managed in your hosting control panel.

  1. Find out who hosts the site. If you are not sure, check where the domain’s A record or CNAME record points at your domain provider.
  2. Open the SSL or security section of the hosting control panel, or the domains page on your website platform, and check the certificate’s status, expiry date and the names it covers.
  3. If it has expired, renew it. If renewal fails, the hosting company can see why.
  4. If it does not cover both versions of your address, reissue it so that it includes yourbusiness.co.uk and www.yourbusiness.co.uk.
  5. If you recently moved host or platform, check that the A and CNAME records match the values the new host gives, and remove any extra A or AAAA records left over from the old one.
  6. Open the site again in a private browsing window and test all four versions of the address: http and https, each with and without www.

For the "Not secure" label in the address bar, missing redirects from http to https and mixed content, see the guide to a website not showing as secure.

If only you, or only some visitors, see it

  1. Check the date and time on the device. Chrome shows "Your clock is behind" or "Your clock is ahead" when the clock is the cause. Set the device to update the time automatically.
  2. If the device has antivirus software with HTTPS or secure connection scanning, turn that feature off briefly and test again. Turn it back on afterwards.
  3. On public Wi-Fi, open any http address to bring up the network’s sign-in page, then try again.
  4. On a work computer, the company’s proxy may be causing the error. Ask the IT team rather than installing certificates yourself.

If that didn’t work

  1. An old DNS record still points some visitors elsewhere

    An extra A or AAAA record can send some visitors to a previous host that has no certificate for your domain. Check every record for the domain and the www version.

  2. The certificate renews but expires again

    If the warning keeps coming back, automatic renewal is failing. The hosting company or platform support can see the renewal error.

  3. The www version is a separate record

    If the bare domain works and www does not, the www record may point somewhere different from the main domain. Point it at the same host and reissue the certificate.

When to get help

Stop and ask for help if the fix needs DNS changes you do not recognise, because a wrong record can take the website or your email offline. Also get help if the host says the certificate is fine but visitors on different networks still see the warning.

What a developer would check

  • The certificate’s issuer, expiry date and the names it covers.
  • DNS records for the domain and www, including extra A or AAAA records.
  • Whether automatic renewal is running and why it last failed.
  • Any service in front of the site, such as a content delivery network, that presents its own certificate.

Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.

Related questions

Should I tell customers to click Advanced and carry on?
No. Chrome warns that attackers might be trying to steal information such as passwords and card details. Fix the certificate instead, so that nobody has to bypass the warning.
Does this warning mean my website has been hacked?
Usually not. Chrome’s own text says it may be caused by a misconfiguration or an attacker intercepting the connection. On your own site, an expired or mismatched certificate is far more common.
Why do I see the warning when other people do not?
Something on your device or network is likely the cause, such as a wrong clock, antivirus software that scans secure connections, a work proxy or a Wi-Fi sign-in page.

Written by Michael Broadbridge, Founder of Webgro. First published 14 November 2026. Last checked 14 November 2026 on Chrome, Safari and Edge.