How can I fix the frequent error page issue after switching my Webflow site to SSL?
TL;DR
If you're experiencing frequent error pages after enabling SSL (HTTPS) on your Webflow site, the issue is often related to incorrect domain settings or caching conflicts. Follow these steps to troubleshoot and fix the problem.
1. Verify Webflow’s SSL Settings
- Go to Project Settings > Hosting.
- Ensure Enable SSL is turned on (this may take a few minutes to apply).
- Republish your site after making changes.
2. Check Your Custom Domain Setup
- Go to Project Settings > Custom Domains.
- Ensure your root domain (e.g.,
example.com) and subdomain (www.example.com) are set up correctly. - Webflow recommends using the www version as the default domain.
- If you've recently updated domain settings, it may take up to 48 hours for DNS propagation.
3. Verify DNS Records with Your Registrar
- Enable SSL in Webflow before updating DNS settings.
- Use the correct records Webflow provides:
- A Records: (a)
75.2.70.75, (b)99.83.190.102 - CNAME Record:
www→proxy-ssl.webflow.com - If using Cloudflare, disable proxying (orange cloud) for Webflow-related DNS entries.
4. Clear Cache and Test with an Incognito Window
- Try opening your website in an incognito/private browser window.
- Clear browser cache and flush DNS on your computer:
- Windows: Run
ipconfig /flushdnsin Command Prompt. - Mac: Run
sudo killall -HUP mDNSResponderin Terminal.
5. Investigate Redirect and Mixed Content Issues
- Use Webflow’s built-in redirects instead of third-party redirects (check Hosting > 301 Redirects).
- Ensure all external resources (images, scripts, fonts) load over HTTPS to prevent mixed content errors.
6. Wait for SSL Propagation (If Recently Changed)
- SSL updates can take up to 24 hours to fully apply.
- If your site still has problems after this period, try removing and re-adding the domain in Webflow.
Summary
Ensure SSL is enabled, Webflow’s recommended DNS records are correct, and there are no cache or mixed content issues. Publishing changes and waiting for DNS propagation can also resolve the issue. If problems persist after 24 hours, consider contacting Webflow support.