Apache: [ssl:warn] AH01909: example.com:443:0 server certificate does NOT include an ID which matches the server name
Apache's SSL virtual host name does not match any name inside the certificate it loads.
AH01909: server certificate does NOT include an ID which matches the server nameserver certificate does NOT include an ID which matches the server name[ssl:warn] AH01909AH01909 RSA certificate configured for example.com:443 does NOT include an ID which matches the server name Meaning
Warning only, but it means browsers will show a name mismatch for that vhost. Fix the ServerName/ServerAlias to a name in the certificate, load the correct certificate for the vhost, or reissue the certificate to include the name. Often a default *:443 vhost is serving the wrong cert.
Common causes
- ServerName not present in certificate SAN
- Wrong certificate file for this vhost
- Default SSL vhost catching requests
- Certificate for example.com used with www host
- Copied vhost not updated
⚡ Quick fix
- Align
ServerNamewith the certificate name - Point
SSLCertificateFileto the right certificate - Run
apachectl -Sto review vhost mapping
Detailed fix by platform
Linux
apachectl -Sandopenssl x509 -in cert.pem -noout -ext subjectAltName
How to diagnose
- ServerName — In SAN?
- Cert — Right file per vhost?
- Default — Catch-all vhost?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- AH00558 Apache: AH00558: apache2: Could not reliably determine the server's fully qualified domain name
- CAA record forbids issuance Let's Encrypt/CA: CAA record for example.com prevents issuance
- certificate does not have a private key (IIS) Windows/IIS: A specified logon session does not exist / The certificate does not have a private key associated with it
Most viewed in SSL / TLS
- NET::ERR_CERT_COMMON_NAME_INVALID NET::ERR_CERT_COMMON_NAME_INVALID: Your connection is not private (certificate is for a different domain)
- Challenge failed for domain Let’s Encrypt / Certbot: Challenge failed for domain example.com — Invalid response from http://example.com/.well-known/acme-challenge/x: 404
- no start line OpenSSL: unable to load certificate / PEM routines:get_name:no start line (key values mismatch)
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026