When Chrome shows "Your connection is not private" with the code NET::ERR_CERT_COMMON_NAME_INVALID, the certificate itself is valid but was not issued for the address you opened. On every HTTPS connection the browser compares the list of names inside the certificate with the domain in the address bar. If that exact name is missing, the browser stops the connection even though encryption works, because it cannot confirm you reached the right site. Firefox reports the same situation as SSL_ERROR_BAD_CERT_DOMAIN.
Which names a certificate covers
The error is named after the old Common Name (CN) field, but modern browsers ignore CN and read the Subject Alternative Name (SAN) extension instead. SAN can hold several names, for example example.uz and www.example.uz. Only names in that list are accepted, so a certificate for example.uz does not protect shop.example.uz. A wildcard *.example.uz covers one level of subdomains only: it works for blog.example.uz but not for test.blog.example.uz or the bare example.uz, which is why the apex is usually added to SAN separately.
The usual causes
- The www or non-www variant is missing from the certificate.
- A new subdomain was added but the certificate was never reissued.
- DNS points elsewhere, so an old or unrelated server answers with its own default certificate.
- The domain is not added to the hosting account. On shared servers many sites share one IP, and an unknown name gets the default certificate.
- The site is opened by IP address, which a domain certificate never matches.
Checking what the certificate actually says
Click the padlock in the browser and look at "Subject Alternative Name" in the certificate details, or use openssl for a precise answer showing both names and issuer:
openssl s_client -connect example.uz:443 -servername example.uz </dev/null 2>/dev/null \
| openssl x509 -noout -subject -issuer -ext subjectAltName
You will see something like DNS:example.uz, DNS:www.example.uz. If a completely different domain or a server hostname appears, the request is reaching the wrong server or virtual host. Keep the -servername option: it sends SNI, and without it many servers return their default certificate, giving a misleading result. Then confirm where both names point:
dig +short example.uz A
dig +short www.example.uz A
Both should return your hosting server's IP. If www still points to an old IP, the error will appear only when visitors type www.
Example: a clinic adds a booking subdomain
A private clinic in Tashkent has run misol.uz for a year without issues. A developer deployed an online appointment system on navbat.misol.uz, added an A record and opened the page, only to get ERR_CERT_COMMON_NAME_INVALID. The openssl check showed SAN contained only misol.uz and www.misol.uz. The subdomain was added in the hosting panel as a site (or as an alias), the Let's Encrypt certificate was reissued with the new name, and within minutes all three names were listed. The DNS record must point to the right server before reissuing, otherwise Let's Encrypt cannot validate the domain.
A reliable fix order
- Note exactly which address fails: www, non-www or a subdomain.
- Use
digto confirm that name points to your hosting IP. - Make sure the domain or subdomain is added to your hosting account.
- Reissue the certificate with every required name selected.
- Reopen in a private window and confirm with
openssl.
On sayt.uz hosting, Let's Encrypt certificates are free and renew automatically, and you can issue one from the hosting panel with the names you need. DNS and nameservers are managed in the sayt.uz cabinet, so the A record is checked and fixed there as well.
Why "Proceed anyway" is not a fix
The "Advanced" and "Proceed to site" link only bypasses the warning in your own browser. Your customers still see it, and many will leave. A name mismatch can also signal a real problem, such as traffic being intercepted on public Wi-Fi, so it is worth fixing the certificate and DNS once rather than ignoring the warning.