ERR_CERT_COMMON_NAME_INVALID -200
Net error -200
The certificate doesn't match the domain.
Also searched as: NET::ERR_CERT_COMMON_NAME_INVALID, certificate name mismatch, error -200
What it means
Chrome shows 'Your connection is not private' with NET::ERR_CERT_COMMON_NAME_INVALID. The certificate is valid but was issued for a different hostname than the one in the address bar, for example 'example.com' when you typed 'www.example.com'.
Applies to: Chrome, Edge, Brave, Opera, Vivaldi, Android
How to fix ERR_CERT_COMMON_NAME_INVALID
- Check the URL; try the version with or without 'www'
- Disable VPN, proxy and antivirus HTTPS scanning, which may present certificates for the wrong name
- Try another network to rule out captive portals redirecting HTTPS
- If you own the site: list the names in the certificate with 'openssl s_client -connect yourdomain:443 -servername yourdomain </dev/null | openssl x509 -noout -ext subjectAltName'
- If you own the site: reissue the certificate including every hostname you serve (both apex and www), e.g. 'certbot -d example.com -d www.example.com'
- If you own the site: make sure each virtual host or SNI entry points to the right certificate, and that a CDN covers the subdomain
Why it happens
Browsers check the hostname against the certificate's Subject Alternative Name list (the Common Name alone is ignored). A missing www or subdomain entry, a shared hosting default certificate, or the wrong vhost being selected cause the mismatch.
FAQ
Why does it work with www but not without?
The certificate only lists one of the two names. The site owner must add the other name to the certificate or redirect it correctly.
Related errors
Source: Chromium net_error_list.h · fixes written and reviewed by the editors (see our editorial policy)
Last updated: