Errors / Network errors

Your connection is not private

Chrome could not confirm the site is who it claims to be, because of a problem with its security certificate.

Most visitors leave at the warning; browsers and search engines treat the site as unsafe.

Seeing it on someone else’s site?

• The code under the message says why: NET::ERR_CERT_DATE_INVALID (expired), NET::ERR_CERT_COMMON_NAME_INVALID (made for another address), NET::ERR_CERT_AUTHORITY_INVALID (not issued by anyone trusted).
• Check your computer's date and time first: a wrong clock makes valid certificates look expired.
• On public Wi-Fi it can be the network's sign-in page; open any http:// site to trigger it.
• Do not type passwords or card numbers past this warning on a site you do not control.

Why it happens, if it is your site

• The certificate expired because automatic renewal failed.
• The certificate does not cover this exact address (www versus the bare domain, a subdomain).
• A self-signed certificate, or a missing intermediate certificate in the server's chain.

How to fix it

1. Renew the certificate (Let's Encrypt is free), and find out why renewal failed.
2. Cover every address the site answers on, or redirect the extra ones to the covered one.
3. Serve the full certificate chain; an SSL checker shows a missing intermediate.

Whose problem it is

Either the site's own code or a third party's, depending on where it comes from.

Often seen with

• ERR_CERT_DATE_INVALIDThe site's security certificate has expired.
• ERR_CERT_COMMON_NAME_INVALIDThe site's certificate was made for a different address than the one being visited.
• ERR_CERT_AUTHORITY_INVALIDThe site's security certificate was not issued by anyone the browser trusts.