If Chrome shows ERR_CERT_COMMON_NAME_INVALID, the website’s security certificate does not match the address you typed, and the fix is usually one of three things: correct the URL, update the server’s certificate, or (for testing only) bypass the warning. This error appears when the certificate’s Common Name (CN) or Subject Alternative Name (SAN) does not include the exact hostname in the browser’s address bar.
What This Error Means
Every HTTPS website presents a digital certificate that proves its identity. The certificate contains a list of hostnames it is valid for—either in the Common Name field (older style) or, more commonly today, in the Subject Alternative Name (SAN) extension. When you visit https://example.com, Chrome checks that example.com appears in that list. If it does not, Chrome blocks the connection and shows ERR_CERT_COMMON_NAME_INVALID.
This is different from other certificate errors:
- ERR_CERT_DATE_INVALID – the certificate has expired or is not yet valid.
- ERR_CERT_AUTHORITY_INVALID – the certificate was issued by an unknown or untrusted certificate authority.
- ERR_CERT_COMMON_NAME_INVALID – the certificate is valid and trusted, but it was issued for a different hostname.
For example, a certificate issued for www.example.com will not work for example.com unless the certificate also lists the bare domain. Similarly, a certificate for example.com will not work for sub.example.com.
Why It Happens: Common Causes
The most frequent scenarios that trigger this error are:
- Typo in the URL – you typed
exampel.cominstead ofexample.com. - Missing or extra “www” – the certificate covers one variant but not the other.
- Using an IP address – certificates are rarely issued for raw IPs; if you access a site by IP, the certificate won’t match.
- Internal or self-signed certificates – a server on your local network may have a certificate for a name like
server.localbut you’re accessing it via192.168.1.10. - Misconfigured server – the web server is serving a certificate for a different site (common on shared hosting).
- Outdated cached certificate – your browser may have cached an old certificate; a hard refresh or clearing cache can help.
How to Fix It: Step-by-Step
Try these in order, from simplest to most involved:
- Double-check the URL – look for spelling mistakes, extra dots, or a missing “www”. If the site is supposed to be
www.example.com, try that instead ofexample.com. - Try the other hostname – if you’re on
www.example.com, tryexample.com(or vice versa). Many sites redirect to the correct one. - Clear Chrome’s cache and SSL state – go to
chrome://settings/clearBrowserData, select “Cached images and files” and “Cookies and other site data”, then click “Clear data”. Also, inchrome://net-internals/#hsts, you can check if the domain is on the HSTS list and delete it if needed (only for testing). - Check the certificate details – click the padlock icon (or “Not secure”) in the address bar, then “Certificate”. Look at the “Subject” and “Subject Alternative Name” fields. If the hostname you typed is not listed, that’s the problem.
- If you control the server – obtain a new certificate that includes the correct hostname. Most modern certificate authorities require you to list all hostnames in the SAN field. For testing, you can use a self-signed certificate, but you must add it to your system’s trusted root store.
- For testing only – you can bypass the warning by clicking “Advanced” on the error page and then “Proceed to [site] (unsafe)”. This is not recommended for production use and will not work if the site uses HSTS.
How to Prevent It on Your Own Website
If you run a website and want to avoid this error for your visitors:
- Use a certificate that covers both
example.comandwww.example.com– most modern certificates include both in the SAN field. - Set up a redirect from the non-www to the www version (or vice versa) so all traffic uses the hostname that matches the certificate.
- If you use a shared hosting provider, ensure the server is configured to serve the correct certificate for each domain.
- For internal servers, use a certificate issued by a private CA and install that CA on all client machines.
When It’s Safe to Proceed (and When Not)
If you are a developer testing a local site or a staging server, proceeding past the warning may be acceptable. But if you are on a public website and see this error, it could mean someone is intercepting your connection (a man-in-the-middle attack). In that case, do not proceed. Always check the certificate details: if the issuer is unknown or the hostname is clearly wrong, leave the site.
Also note that Chrome’s warning is stricter than some other browsers. Firefox and Safari may show similar warnings, but Chrome is often the first to enforce the SAN requirement fully. That means a site that works in Firefox may still fail in Chrome if the certificate lacks the correct SAN.
Frequently Asked Questions
Why does this error appear on my own computer but not on my phone?
Different devices may have different cached certificates or may be accessing the site through different DNS servers. Also, your phone might be using a different network that routes to a different server (e.g., a load balancer) that has a valid certificate.
Can I fix this error without contacting the website owner?
If you are a visitor, the only fixes are to try the correct URL or clear your browser cache. You cannot fix a server-side certificate issue from your browser. If you are the site owner, you need to update the certificate on the server.
Does this error mean the site is hacked?
Not necessarily. It usually means a configuration mistake. However, it can also indicate a malicious redirect or a proxy intercepting traffic. Check the certificate details and the URL carefully.
How do I add a self-signed certificate to Chrome’s trust store?
On Windows, you can import the certificate into the “Trusted Root Certification Authorities” store via the certificate manager (certmgr.msc). On macOS, use Keychain Access and set the certificate to “Always Trust”. On Linux, the method depends on your distribution. After importing, restart Chrome.
Why does Chrome show this error for a site that worked yesterday?
The certificate may have expired and been replaced with one that has a different hostname, or the site moved to a different server with an incorrect certificate. It could also be a temporary DNS issue that sends you to the wrong server.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to View Wi-Fi Password on iPhone
- How to Stream on Twitch from PC
- GTM vs Facebook Pixel: What’s the Difference?
- Windows 10 Won’t Boot? Fix It in 30 Minutes
- Ubuntu 26.04 LTS Requirements & Hardware Checks
- ATK0100 Driver: Do You Need to Install It?