Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames
The server’s certificate doesn’t cover the hostname you connected to.
does not match certificate's altnames Meaning
Connecting by IP, to an internal alias, or to a different subdomain than the certificate lists (SAN). Wildcards cover one level only.
Common causes
- Connecting by IP address instead of hostname
- Certificate for a different domain/subdomain
- Wildcard not covering nested subdomains
- SNI not sent
⚡ Quick fix
- Use the hostname on the certificate
- Issue a certificate including the needed names
- Set servername for SNI when connecting by IP
Detailed fix by platform
Node.js
tls.connect({ host: ip, servername: 'api.example.com', port: 443 })
How to diagnose
- Names — Certificate SANs vs requested host
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 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
Most viewed in Node.js
Other ways to find it
Where this error sits
Origin: Application & API. 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 12 Oct 2026