Quick Answer: NET::ERR_CERT_COMMON_NAME_INVALID means the website’s security certificate was issued for a different domain name than the one you’re visiting. Unlike an expired certificate, this usually points to a real misconfiguration on the site, a captive portal intercepting the connection, or you reaching the site through the wrong address (like a raw IP instead of its domain).
What Causes This Error
- The site’s certificate was issued for a different domain (e.g., missing the “www” subdomain, or covering only one of several domains it serves)
- Visiting a site by its raw IP address instead of its domain name
- A captive portal (like a hotel or school Wi-Fi login page) intercepting your connection and presenting its own certificate
- A misconfigured content delivery network (CDN) serving the wrong certificate for that domain
- A man-in-the-middle proxy on a managed network inspecting HTTPS traffic
How to Fix It
Step 1: Check the address you typed
Confirm you’re using the exact domain, including or excluding “www” as the site expects. Try both versions, since a certificate issued for one won’t always cover the other.
Step 2: Look for a Wi-Fi captive portal
If you’re on hotel, airport, or guest Wi-Fi, open a new tab and try a plain HTTP site, or check for a login page notification. You may need to complete the network’s sign-in page before HTTPS sites work correctly.
Step 3: Try the site on a different network
Switch to a mobile hotspot. If the certificate error disappears, the original network (often a school or office one) is intercepting HTTPS traffic with its own certificate.
Step 4: Check the date and time
An incorrect system clock can sometimes trigger confusing certificate errors alongside this one. Go to Settings > Date and time and confirm “Set time zone automatically” is on.
Step 5: Report it if it’s a real site misconfiguration
If you reach the site through its normal, correct address and still get this error on multiple networks, the site’s own certificate setup is broken. There’s nothing to fix on your end; wait for the site owner to correct it.
Still Not Fixed?
Never click “Proceed anyway” on this warning for a site handling logins, payments, or personal data. If you must access the site urgently and you’re certain of the cause (like a known captive portal), only proceed on sites you fully trust.
FAQ
Is this the same as NET::ERR_CERT_DATE_INVALID?
No. ERR_CERT_DATE_INVALID means the certificate expired or isn’t valid yet. This error means the certificate’s domain name doesn’t match the site you’re visiting, which is a different, often more serious mismatch.
Should I ever bypass this warning?
Only if you fully understand the cause, such as a known internal tool with a certificate issue you’re aware of. For any public website, treat this warning seriously.
Can my school or work network cause this on legitimate sites?
Yes. Managed networks that inspect HTTPS traffic sometimes present their own certificate, which won’t match the real site’s domain and triggers exactly this error.
