# ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete

**Code:** `ALB listener` · **Category:** SSL / TLS · **Seen on:** AWS, SSL

An Application Load Balancer HTTPS listener can't be created or serves the wrong certificate.

## 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

1. Attach an ISSUED same-region certificate as default
2. Add extra certificates for other hostnames
3. Allow 443 in the load balancer security group

## Detailed fix by platform

### Shell

1. 

```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

1. **Certificate** — Issued, same region?
2. **Default** — Set?
3. **SG** — Allows 443?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/ssl/alb-https-listener-default-certificate-missing)
