Webflow users occasionally report SSL-related issues causing site downtime, but these are not widespread or consistent across all users.
- Expired SSL certificates: Occasionally, a project's SSL certificate may not renew correctly after DNS updates or custom domain changes.
- Improper DNS setup: If your custom domain isn’t configured with the correct A records or CNAME, the SSL certificate can fail to provision.
- SSL provisioning delay: In some cases, after enabling SSL or connecting a custom domain, it can take a few hours for Webflow’s system to issue a valid SSL certificate.
2. Webflow SSL Configuration Checks
- Go to Project Settings > Hosting tab
- Ensure SSL is toggled ON.
- Re-publish your site after toggling SSL.
- Check your DNS settings
- A Records should point to (a) 75.2.70.75 and (b) 99.83.190.102.
- If you're using a subdomain like www, make sure the CNAME points to proxy-ssl.webflow.com.
3. Webflow System Status and Support
- Check Webflow’s Status Page for active incidents involving SSL or hosting.
- If your SSL issue persists more than 24 hours after correct setup:
- Contact Webflow Support with your domain details.
- Use any error messages received (e.g., ERR_CERT_COMMON_NAME_INVALID) to help them troubleshoot.
4. Other Users Reporting Issues?
- While isolated SSL problems occur, there is no current widespread outage or pattern affecting all add-on users.
- If you notice increased community reports, check the Webflow Forum (https://discourse.webflow.com) and Reddit (/r/webflow) to compare similar cases.
Summary
SSL issues in Webflow typically stem from DNS misconfiguration or delays in SSL provisioning, not a broader platform-wide problem for add-on users. Always verify your DNS setup, ensure SSL is enabled, and check Webflow's system status or forums if issues persist.