ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete
An Application Load Balancer HTTPS listener can't be created or serves the wrong certificate.
CertificateNotFound: Certificate not foundAn error occurred (CertificateNotFound) when calling the CreateListener operationALB HTTPS listener requires a default SSL certificateCertificate 'arn:aws:acm' not found ALBALB default certificate missing Meaning
A listener needs a default certificate from ACM/IAM in the same region and ISSUED. Add additional certificates for other domains (SNI list), pick a modern security policy (ELBSecurityPolicy-TLS13-1-2-2021-06), and allow port 443 in the security group.
Common causes
- Certificate in a different region or still pending
- Default certificate not set
- SNI certs missing for other domains
- Security group blocks 443
- Deleted/expired ACM certificate
⚡ Quick fix
- Attach an ISSUED same-region certificate as default
- Add extra certificates for other hostnames
- Allow 443 in the load balancer security group
Detailed fix by platform
Shell
- bash
aws elbv2 add-listener-certificates --listener-arn LISTENER_ARN --certificates CertificateArn=ARN aws elbv2 describe-listener-certificates --listener-arn LISTENER_ARN
How to diagnose
- Certificate — Issued, same region?
- Default — Set?
- SG — Allows 443?
🔧 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 SSL / TLS
- HTTPSConnectionPool: Max retries exceeded (SSLError) Python requests: HTTPSConnectionPool(host='api.example.com', port=443): Max retries exceeded with url: /v1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] ...')))
- Keystore was tampered with, or password was incorrect Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
- 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
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 18 Nov 2026