Chrome stops a page and prints NET::ERR_CERT_COMMON_NAME_INVALID when the name written on a site’s SSL certificate does not match the address you asked for. Most cases trace back to the server. A smaller share come from your own device, a rogue extension, or security software sitting in the middle. The fixes below run from quickest to most technical.
What Does ERR_CERT_COMMON_NAME_INVALID Mean?
The common name is the exact domain a certificate was issued for. A certificate bought for shop.example.com vouches for that name and nothing else.
Request example.com instead and the browser spots a mismatch, then refuses the connection. Chrome prints “Your connection is not private” above the code. Firefox and Safari word the same fault differently.
What Causes the ERR_CERT_COMMON_NAME_INVALID Error
Three places produce it. The host machine serves a certificate that does not cover the hostname or subdomain being requested. Your device carries a wrong clock, a faulty add-on, or stale SSL data. Outside software such as a firewall or antivirus intercepts the encrypted traffic.
Self-signed certificates cause the same block. Those belong on internal test machines, and Chrome removed the old workaround for self-signed certificates on localhost in version 119.
How to Fix ERR_CERT_COMMON_NAME_INVALID in Chrome
Correct the date and time
A laptop or phone running the wrong day or hour fails certificate validation outright. Open your system panel and switch on automatic sync.
The same wrong clock also produces a date-based certificate warning, so check this before anything else.
Rule out a broken extension
Load the page in an incognito window. Extensions stay off there by default, so a clean load points straight at an add-on.
Press the three-dot button, pick More tools, then Extensions. Switch items off one at a time until the page opens. Once you find it, follow the steps for removing add-ons from Chrome and get rid of it.
Inspect the certificate on the server
Click “Not secure” beside the web address, then choose Certificate. Read the “issued to” line and compare it against the hostname in your address bar.
An SSL Labs scan gives a sharper answer, including every Subject Alternative Name attached to the certificate. If none of them match, the certificate needs reissuing.
Cover both www and non-www
Some certificates protect only one spelling of a domain. Redirecting visitors from the bare address to the www version then trips the mismatch.
Pick a certificate that lists both. A wildcard or multi-domain product covers every subdomain you run under one purchase.
Fix ERR_CERT_COMMON_NAME_INVALID on WordPress
Owners switch a site to HTTPS with nothing bought and nothing installed. Chrome answers with the error on every page load.
Buy a certificate and install it on the host. Or drop back to HTTP, which leaves traffic unencrypted.
Clear the stored SSL state
Cached certificate data goes stale and keeps the block alive after the real fault is gone. In Edge and Internet Explorer, open Internet properties, go to the Content tab, and press Clear SSL state.
Chrome reaches the same panel through Settings, Advanced, then Open proxy settings. A wider browser data cleanup helps if pages keep loading oddly, and flushing Chrome’s DNS cache clears any wrong IP still pinned to the domain.
Check your proxy configuration
Automatic detection left unticked limits web access on some networks. Right-click your network icon to reach Internet Properties.
Open the Connections tab, then LAN Settings. Tick “Automatically detect settings” if the box sits empty and reload the page.
Update Chrome and your operating system
Old builds miss support for current TLS versions. That gap shows up as certificate errors and as protocol mismatches during the handshake.
Open the three-dot menu, select Help, then About Google Chrome. Install anything waiting, then restart.
Read firewall and antivirus logs
Security suites that scan HTTPS traffic insert their own certificate into the chain. Open the log files and confirm neither tool is blocking the site.
Read the stated reason before acting. Switching antivirus off permanently is not the answer.
When ERR_CERT_COMMON_NAME_INVALID Belongs to the Site Owner
Try the site on a second device and a second network. If it fails on both, nothing on your end will fix it.
The owner has to reissue or reinstall the certificate. A related code, the untrusted authority warning, points at a different part of the same chain and needs its own set of steps.
FAQs
What does ERR_CERT_COMMON_NAME_INVALID mean?
It means the domain on the site’s SSL certificate does not match the address in your browser. Chrome cannot verify the site is who it claims, so it blocks the connection.
How do I bypass ERR_CERT_COMMON_NAME_INVALID?
Click Advanced on the warning page, then Proceed. Do this only on sites you already trust, and never while entering passwords or payment details.
Is ERR_CERT_COMMON_NAME_INVALID a virus?
No. The code reports a name mismatch on a certificate. Server misconfiguration explains most cases, though a hijacked or spoofed domain can produce the same warning.
What is the common name in an SSL certificate?
The common name is the domain a certificate was issued for, such as example.com. Modern browsers also read Subject Alternative Name entries, which list extra domains and subdomains.
Can I fix ERR_CERT_COMMON_NAME_INVALID if I do not own the site?
Only partly. Correct your clock, test in incognito, clear SSL state, and update Chrome. If the error survives on other devices, the owner must reissue the certificate.
