Netlify SSL Certificate Pending or Not Provisioning

Share
Workaround available Web, CLI Updated November 13, 2026Based on 3 user reportsHow we research

Quick answer

Netlify issues certificates through Let's Encrypt only after DNS points to Netlify. Fix DNS, CAA records and proxies, then use Renew certificate under Domain management > HTTPS.

Most likely fix: Check status

How to fix it

Try these in order — the most common fix is first.

  1. 1. Check status

    1. Open Domain management > HTTPS
    Did this fix it?
  2. 2. Fix DNS first

    1. Point apex and www at Netlify and wait for propagation
    Did this fix it?
  3. 3. Fix CAA records

    1. Allow letsencrypt.org with the Netlify account URI, or remove restrictive CAA records
    Did this fix it?
  4. 4. Disable proxy

    1. Turn off Cloudflare proxying until issued
    Did this fix it?
  5. 5. Renew the certificate

    1. Domain management > HTTPS > Renew certificate
    Did this fix it?
  6. 6. Subdomain limits

    1. Use Netlify DNS for wildcard certificates or contact support before adding many aliases
    Did this fix it?

Symptoms

HTTPS shows 'Certificate provisioning failed', stays pending, or the browser warns the certificate does not match.

Why it happens

  • DNS not yet pointing to Netlify
  • CAA record excludes Let's Encrypt
  • Cloudflare proxy intercepts validation
  • More than 5 subdomain aliases hit rate limits
  • Custom certificate does not cover the domain
  • Inactive Netlify DNS zone

This guide also covers

  • netlify ssl certificate pending
  • netlify certificate provisioning failed
  • netlify https not working
  • netlify let's encrypt

Still not working?

If Netlify keeps failing, you're not alone. See every Netlify 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 us
Fixed it? Share this guide

Other Netlify errors

All 10 Netlify errors and fixes →