SSL certificate not valid (NET::ERR_CERT_COMMON_NAME_INVALID)
On this page
Every website gets a free certificate automatically as soon as its domain points to this server, and it is renewed 30 days before it expires. Until a website has its own certificate, https:// shows the server's own certificate, which is made for the server's name — so the browser reports a name error.
Symptoms
- "Your connection is not private", "Warning: Potential Security Risk Ahead" or
NET::ERR_CERT_COMMON_NAME_INVALID. NET::ERR_CERT_DATE_INVALID(expired) orNET::ERR_CERT_AUTHORITY_INVALID.https://www.example.comfails whilehttps://example.comworks (or the other way round).- On the SSL/TLS page the website shows Waiting for DNS, Failed or Not yet.
Causes
Most likely first:
- The domain does not point to this server yet, so no certificate could be issued (Waiting for DNS).
wwwor an alias did not point here when the certificate was made, so only some names are in it.- An AAAA (IPv6) record points to another server.
- The certificate authority refused the request — rate limit, a CAA record, or the check file could not be fetched.
- Your own installed certificate expired or does not match the name.
- You open the site through Cloudflare's proxy and Cloudflare's own settings are wrong: see Cloudflare 525 and 526.
Fix
See the status
- Open SSL/TLS (section Domains). Each domain shows its Status: Secured, Issuing…, Waiting for DNS, Failed or Not yet, with the Issuer and Expires date.
- For the reason of a failure, open Site Check (section Advanced), choose the website and click Check. The Certificate line shows the status and the last error.
1. Waiting for DNS
The domain must resolve to this server in public DNS. In Site Check, Address in DNS must say (this server). Fix the nameservers or A record first (DNS not updated yet), then click Check now on the SSL/TLS page. Otherwise AutoSSL checks again by itself every few hours.
2. www or an alias is missing
Only names that really point here are put in the certificate, so an unpointed www does not block the domain. Once www (or the alias) points here, the certificate is widened automatically. To do it now, click Renew now next to the domain.
3. AAAA record elsewhere
If the domain has an AAAA record, it must be this server's IPv6 address. Remove or correct it where your DNS is hosted, then click Check now.
4. The request was refused
The Certificate line in Site Check shows the authority's message:
- Rate limit of the certificate authority reached: too many certificates for the same names in a short time. Wait (usually a week at most) — do not keep clicking Renew now.
- A message about CAA: the domain has a CAA record that does not allow Let's Encrypt. Add
letsencrypt.orgto it in Zone Editor, or remove the CAA record. - A message about the challenge (404, timeout, unauthorized): the check file under
/.well-known/acme-challenge/could not be fetched overhttp://. Make sure no rule in.htaccessor in Redirects sends that path elsewhere and that the site is reachable on port 80.
A failed domain is retried by itself after 6 hours; Check now retries at once.
5. Your own certificate
If the SSL/TLS page shows own certificate, it replaces the free one until it expires. Install a renewed certificate under Install your own certificate, or click Use automatic to switch back to the free certificate.
Good to know
- A Wildcard certificate (
*.example.com, Add wildcard) needs the domain to use this server's nameservers. - If HTTPS enforced in browsers (HSTS) is on in Access Control, browsers refuse to open the site without a valid certificate and do not let visitors click through the warning.
- The control panel (
:2083), webmail and mail apps use the certificate of the server's name, not of your domain. Opening them by IP address always shows a warning.
Still not working?
If Secured shows but the browser still warns, check the exact name you open (www, subdomain) and reload without the cache. If your host has turned on the AI assistant, click Ask the AI assistant what is wrong on Site Check, or contact your host through Support with the Site Check result.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- Website not working after changing nameservers (DNS)
You changed nameservers or DNS records and the site still shows the old server or nothing. Check where the domain points, how long DNS takes and what to fix.
- Cloudflare error 525 or 526 on your website
Fix Cloudflare "Error 526: Invalid SSL certificate" and "Error 525: SSL handshake failed": get the certificate issued here, then use Full (strict).
- Too many redirects (ERR_TOO_MANY_REDIRECTS) on your website
Fix ERR_TOO_MANY_REDIRECTS ("redirected you too many times"): Cloudflare Flexible SSL, http/https or www rules, redirects and WordPress addresses.