What happens if non-www is set as the default in Webflow and Chrome shows a privacy warning while Safari immediately gives up?
TL;DR
- Chrome shows a privacy warning and Safari blocks access when SSL isn’t properly set for a non-www default domain in Webflow.
- To fix, enable SSL in Webflow’s Hosting settings and ensure DNS for both www and non-www versions correctly point to Webflow’s IPs.
If the non-www version is set as the default domain in Webflow but isn’t properly configured with an SSL certificate, browsers like Chrome and Safari will behave differently when encountering this security issue.
1. Chrome Shows Privacy Warning
- Chrome displays a full-page security warning when the SSL certificate is invalid or missing. This occurs when HTTPS fails due to a domain misconfiguration.
- Users may see messages like "Your connection is not private" (SSLERROR or NET::ERRCERTCOMMONNAME_INVALID).
- Advanced users can click through to proceed, but most will leave the page.
2. Safari Fails Immediately
- Safari often blocks untrusted SSL connections outright with a stronger UX focus on user protection.
- It may not show a bypass option, simply stating that the site “cannot be reached” or displaying a message like "Safari can't establish a secure connection".
- This makes the error appear more final than Chrome’s warning.
3. Cause: SSL Not Properly Set for Non-WWW
- When you set the non-www version (e.g., example.com) as the default domain in Webflow, you must update your domain DNS and ensure SSL is enabled for that version.
- Check that:
- DNS A records point to Webflow IPs: (a) 75.2.70.75, (b) 99.83.190.102
- CNAME (if using www) is still correctly set to proxy-ssl.webflow.com
- SSL is enabled in Project Settings > Hosting under the Custom Domains section.
- Domains with SSL misconfigured or lacking verification will trigger browser-level security blocks.
4. Fix the Domain Configuration
- Go to Project Settings > Hosting.
- Confirm the non-www version of the domain is:
- Properly verified (green check),
- Set as default (if desired),
- SSL-enabled (toggle should be on).
- In your domain registrar’s dashboard, ensure:
- Both www and non-www point to Webflow’s IPs or
- Use a redirect from non-www to www (or vice versa) as consistent routing is key.
Summary
The privacy warnings in Chrome and Safari occur because SSL is not properly configured for the non-www version set as default. To fix it, make sure SSL is active and DNS is correctly pointing to Webflow for your root domain.