Fastly TLS Certificate Stuck Pending or Not Provisioning
Quick answer
A Fastly-managed certificate stuck on 'Checking domain DNS records' needs a correct ACME challenge record and no blocking CAA record. Fix DNS, then click Retry now.
Most likely fix: Fix the challenge DNS record
How to fix it
Try these in order — the most common fix is first.
1. Fix the challenge DNS record
- Check with dig _acme-challenge.www.example.com +short (DNS challenge) or dig www.example.com +short (HTTP challenge)
- Create the CNAME shown on the Complete DNS verification page and keep it in place after setup
- For the HTTP challenge, disable any forced HTTPS redirect first; it does not work for wildcards
Did this fix it?2. Allow the CA in your CAA records
- List your CAA records
- Add or allow certainly.com, letsencrypt.org or globalsign.com depending on the CA you chose
- Remove CAA entries that exclude it
Did this fix it?3. Retry or wait
- Provisioning should take up to about an hour; wait before acting
- Open the subscription and click Retry now (Fastly retries for 24 hours; a subscription is marked Failed after 7 days)
- If stuck at Certificate requested for over an hour, contact Fastly Support
Did this fix it?
Symptoms
TLS subscription stays at 'Checking domain DNS records' or 'Certificate requested', or ends as Failed.
Why it happens
- The _acme-challenge CNAME (DNS challenge) or the traffic CNAME/A record (HTTP challenge) is missing or wrong
- A CAA record blocks the certificate authority
- Recent DNS changes have not propagated (up to 72 hours)
- A forced HTTPS redirect blocks the HTTP challenge
- Temporary CA issue at the Certificate requested step
This guide also covers
- fastly tls certificate pending
- fastly certificate not provisioning
- fastly checking domain dns records
- fastly managed tls failed
Still not working?
If Fastly keeps failing, you're not alone. See every Fastly problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Fastly errors
- Fastly Error: Unknown Domain
- Fastly 503 Backend Read Error / Connection Timeout
- Fastly Purge Not Working (Old Content Still Served)
- Fastly Origin TLS Errors: Hostname Mismatch, Unable to Verify Certificate
- Fastly Not Caching: Always X-Cache MISS
- Fastly Serves Wrong Content or Denies Requests From Origin (Override Host)
- How to Cancel Fastly Account