If you're seeing frequent error pages after enabling SSL on a Webflow site, it’s often related to domain misconfiguration or caching issues. Here's how to fix it.
1. Confirm SSL Is Enabled in Webflow
- Go to Project Settings > Hosting tab.
- Make sure the SSL checkbox is turned ON.
- After enabling, Webflow may temporarily disable publishing until DNS is correctly configured.
2. Correct DNS Settings
Go to your domain registrar (e.g., GoDaddy, Namecheap, Cloudflare).
Ensure the domain points to the correct Webflow IP addresses:
A records:
- (a) 75.2.70.75
- (b) 99.83.190.102
CNAME record:
- For the www subdomain, set a CNAME to proxy-ssl.webflow.com
Important: Remove any old or conflicting A/CNAME records that don’t match the above.
3. Set the Correct Default Domain
- In Webflow's Hosting tab, scroll to Custom Domains.
- Set the www version of your domain (e.g., www.example.com) as the default.
- Webflow requires the www version to function correctly with SSL.
4. Wait for DNS Propagation
- After updating DNS records, it may take up to 48 hours for full propagation, but typically it completes much sooner.
- During this time, occasional error pages may occur.
5. Clear Browser and DNS Cache
- Clear your browser cache or test in Incognito mode.
- You may also flush your local DNS cache (command varies by OS).
6. Force HTTPS Redirect in Webflow
- While in the Hosting tab, make sure "Force SSL" or "Enable SSL Redirect" is turned ON. This ensures all traffic loads securely via HTTPS.
7. Check for External Conflicts
- If you're using external tools like Cloudflare, make sure:
- SSL is set to Full or Full (Strict).
- There’s no page rule interfering with redirects or certificates.
- Avoid enabling both Webflow and Cloudflare redirects at the same time (can cause loops/errors).
Summary
To fix frequent error pages after enabling SSL in Webflow, verify correct DNS settings (A and CNAME records), ensure SSL and Force Redirect are enabled, set the www domain as default, and allow DNS changes to propagate. Always remove conflicting records and clear your cache after updates.