Lorixen.
EN

ERR_CERT_COMMON_NAME_INVALID on your site: find the missing name

Short answer: NET::ERR_CERT_COMMON_NAME_INVALID, or "certificate name mismatch" in other browsers, means the HTTPS certificate your server presented doesn't list the exact hostname the visitor typed. The usual causes are a certificate covering yourshop.ca but not www.yourshop.ca, a new subdomain without its own certificate, a wildcard that doesn't reach two levels deep, DNS pointing at the wrong server, or a host serving another site's default certificate. Check which names the certificate actually contains, then issue one that includes every hostname you use and make sure DNS points where that certificate lives.

Why browsers check the name

A certificate proves that the server belongs to a particular name. RFC 2818, which describes HTTP over TLS, says that if a certificate has a subjectAltName entry of type dNSName, that must be used as the identity, and if the hostname doesn't match the identity in the certificate, clients must notify the user or end the connection. Despite the "common name" in Chrome's error code, modern browsers look at the Subject Alternative Name list. RFC 2818 already called the Common Name field existing practice that was deprecated.

So the browser compares the address bar's hostname with every name in the certificate. No match, no padlock, and visitors see a full-page warning that most of them won't click through.

Step 1: See what the certificate covers

  1. Visit the failing address and open the certificate details from the warning page or the address bar.
  2. Find Subject Alternative Name (sometimes labelled "DNS Name").
  3. Note every name listed.

Compare that list with the exact hostname that fails. Common findings:

Failing address Certificate lists Problem
www.yourshop.ca yourshop.ca only www not included
shop.yourshop.ca yourshop.ca, www.yourshop.ca New subdomain not included
eu.shop.yourshop.ca *.yourshop.ca Wildcard covers one level only
yourshop.ca server123.hostingco.net Host's default certificate
yourshop.ca anothersite.com Shared IP serving another site's certificate

Step 2: Understand wildcards

Wildcards are a frequent surprise. RFC 2818 explains that * matches a single domain name component: *.a.com matches foo.a.com but not bar.foo.a.com. A wildcard also doesn't cover the bare domain itself; *.yourshop.ca doesn't match yourshop.ca. Many certificates therefore list both yourshop.ca and *.yourshop.ca.

Let's Encrypt's FAQ confirms that one certificate can contain several different names using the Subject Alternative Name mechanism, and that wildcard certificates must be issued using the DNS-01 challenge, which means your DNS provider must support automated record changes or you add records manually.

Step 3: Fix the cause

Missing www or bare domain. Reissue the certificate with both names. Most hosting control panels have checkboxes for "include www". Then redirect one version to the other so visitors always land on your preferred address.

New subdomain. Add it to the certificate, issue a separate certificate for it, or use a wildcard if you create subdomains often.

Host's default certificate. The domain reaches the server, but the server doesn't know which site it belongs to, or the certificate for it hasn't been installed. Add the domain to the site in your hosting panel and issue a certificate for it. On your own server, check the virtual host configuration lists the domain as a server name.

Another site's certificate. On shared hosting or a misconfigured server, a request may reach the wrong site configuration. Contact your host or fix the server configuration so your domain is matched to your site.

DNS pointing to an old server. After moving hosts, an old A record or a leftover AAAA record may send some visitors to the previous server, which no longer has your certificate. Check both IPv4 and IPv6 records.

CDN or proxy in front. If a CDN sits in front of your site, the certificate visitors see is the CDN's. Make sure the hostname is added in the CDN's settings with a certificate issued for it.

Step 4: Test properly

  • Test every hostname: bare domain, www, and each subdomain, over HTTPS.
  • Test from mobile data as well as your office network, especially after DNS changes.
  • Use an online SSL checker that lists the certificate's names and the server's IP addresses.
  • Check that automatic renewal will include all the same names next time.

Name mismatches don't only affect people typing your address. Check the hostnames used in email templates, QR codes on packaging, links inside your mobile app, webhook URLs you've given to payment or shipping providers, and old marketing campaigns. Apps and server-to-server integrations usually fail silently or with a cryptic error instead of a warning page, so an order notification or stock sync may simply stop. List every hostname your business has published, and include each one in your certificate or redirect it from a hostname that is covered.

Keep it from coming back

Most name mismatches appear after a change: a host move, a new subdomain, a CDN switch or a renewal configured differently from the original. Add "test every hostname over HTTPS" to the checklist for any such change, and set up monitoring that checks each hostname's certificate and alerts you before expiry or when the names change unexpectedly.

An illustrative example

A hypothetical Calgary florist moved to a new host. The home page worked, but customers clicking an old printed flyer URL, www.calgaryblooms.ca, saw "Your connection is not private". The certificate listed only calgaryblooms.ca. The host's panel had a separate "include www" option that hadn't been ticked during setup. After reissuing the certificate with both names and adding a redirect from www to the bare domain, the warning disappeared. The florist also found a leftover AAAA record pointing at the old host and removed it.

FAQ

Can customers just click through the warning?

Some can, but most won't, and they shouldn't be trained to. Fix the certificate.

Do I need to pay for a certificate with several names?

Free certificate authorities support multiple names. Paid options may suit specific needs.

Why does it work for me but not my customers?

You may have cached DNS, a different network path or a browser that remembered your earlier visit. Test from another network.

Is this a sign I've been hacked?

Rarely. It's almost always configuration.

If visitors are seeing certificate name warnings on your site, send us the exact address that fails.

Sources

WhatsAppBook a call