NET::ERR_CERT_COMMON_NAME_INVALID in Chrome on Mac

ERR_CERT_COMMON_NAME_INVALID is a Chrome certificate error. The Chromium source describes it as: “The server responded with a certificate whose common name did not match the host name.”

Fix this with your agentCopies a prompt for Claude Code, Codex or any agent that can use Terminal.

My Mac has this problem: NET::ERR_CERT_COMMON_NAME_INVALID in Chrome on Mac. Read https://kilobat.app/guides/err-cert-common-name-invalid.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Applies to: Google Chrome and other Chromium browsers (Edge, Brave, Arc) on all current macOS versions.Checked: 29 October 2026

Symptoms

  • Chrome shows “Your connection is not private”.
  • The error line reads NET::ERR_CERT_COMMON_NAME_INVALID.
  • The certificate belongs to a different name than the one you typed.

Likely causes

  • A wrong address. You opened the site by an IP address or a name that the certificate does not cover.
  • A server with the wrong certificate. The server sends the certificate of another site.
  • A router or device page. Local devices often use a certificate for another name.
  • A proxy or filter. A device in the path can answer with its own certificate.

How to check

  1. Click the lock or Not secure icon and read the names in the certificate.

  2. Compare with the name in the address bar.

  3. Read the certificate subject with OpenSSL.

    openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -subject
  4. Try the host name that the certificate lists.

How to fix it

  1. Open the site by a name that the certificate covers.

  2. If you run the site, issue a certificate for the name that you use.

  3. For a local device, use its host name, or update its firmware.

  4. Do not proceed past the warning on sites with sign-ins.

With Kilobat

  1. Kilobat's connection doctor tests the address layer by layer: network, proxy, DNS, rules, IPv4, IPv6, TLS and the server. It names the layer that failed.

    kilobat why https://example.com
  2. These Kilobat checks are free. AI agents run them through MCP with diagnose_connection and diagnose_network. See Find why one site or API won't connect.

Questions

Is the site unsafe?

The connection cannot prove that it reaches the site you typed. Do not enter passwords.

Why does www fix it?

The certificate may cover www.example.com but not example.com.

Sources

Checked on 29 October 2026.