Webflow Custom Domain or SSL Error

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

Quick answer

Custom domain and SSL errors in Webflow almost always come from DNS records that do not match the dashboard, a Cloudflare proxy blocking certificate validation (error 525), or certificate provisioning still pending. Fix DNS, pause the proxy, republish and wait.

Most likely fix: Match DNS records to the dashboard

How to fix it

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

  1. 1. Match DNS records to the dashboard

    1. Open Site settings > Publishing (Hosting) and read the records Webflow shows for your domain
    2. In your DNS provider, make the root A record and the www CNAME match exactly
    3. Delete old A, AAAA or CNAME records pointing elsewhere
    Did this fix it?
  2. 2. Pause the Cloudflare proxy

    1. In Cloudflare DNS, set the Webflow records to 'DNS only' (grey cloud)
    2. Wait for Webflow to show the domain as connected and SSL as active
    3. Turn the proxy back on only if you need it, using Full SSL mode
    Did this fix it?
  3. 3. Republish to regenerate the certificate

    1. Open Site settings > Publishing
    2. Click Publish to all domains
    3. Wait a few minutes and reload in a private window
    Did this fix it?
  4. 4. Wait for propagation and check status

    1. Allow 15-30 minutes, longer for some DNS hosts
    2. Use a DNS lookup tool to confirm your records
    3. Check status.webflow.com for SSL validation incidents
    Did this fix it?
  5. 5. Contact support with specifics

    1. Send the exact error text, domain and DNS records
    2. Include whether a proxy or CDN sits in front of the site
    Did this fix it?

Symptoms

Your custom domain shows 'This site can't provide a secure connection', ERR_SSL_PROTOCOL_ERROR, SSL_ERROR_INTERNAL_ERROR_ALERT, NXDOMAIN or Cloudflare error 525.

Why it happens

  • DNS A or CNAME records missing or different from the ones shown in Hosting settings
  • DNS changes not propagated yet (can take 15-30 minutes or longer)
  • Cloudflare proxy (orange cloud) blocks Let's Encrypt validation, causing 525
  • Old conflicting records for the same domain, e.g. leftover AAAA or A records
  • SSL certificate not issued because the site was not republished
  • Temporary Webflow incidents delaying SSL validation

This guide also covers

  • webflow custom domain not working
  • webflow ssl error
  • webflow error 525
  • webflow ERR_SSL_PROTOCOL_ERROR

Still not working?

If Webflow keeps failing, you're not alone. See every Webflow problem users report or the alternatives people switch to.

Done fighting Webflow? Our small team builds your own Webflow alternative, or any software you need: web, mobile, games, desktop. Price agreed together.

Talk to us
Fixed it? Share this guide

The same problem in other apps

All not loading, error messages & connection guides →

Other Webflow errors