A 403 Forbidden error with an "openresty" message on a custom domain in Webflow usually indicates an issue with domain setup or access restrictions. Follow these steps to resolve it:
1. Verify Domain Connection in Webflow
- Go to Webflow Project Settings > Hosting
- Check if your custom domain is showing as Connected
- If there are warnings, follow Webflow’s instructions to fix them
2. Check DNS Settings
- Ensure the A records and CNAME are correctly set up in your domain provider:
- A records:
- CNAME:
www
→ proxy-ssl.webflow.com
- If you've recently updated DNS settings, wait up to 48 hours for propagation
- Check for old A records or CNAME entries that might conflict with Webflow
- Remove non-Webflow-related DNS records that point to other IPs
4. Ensure the Correct Default Domain
- In Webflow hosting settings, set "www.yourdomain.com" as the default domain
- Avoid setting the root domain (
yourdomain.com
) as the default unless using specific DNS providers that support it
5. Check Site Status in Webflow
- Ensure the project is published to the custom domain
- Republish the site and test the domain again
6. Clear Cache & Test in Incognito Mode
- Clear browser cache or try visiting the site in incognito/private mode
- Flush your DNS cache (
ipconfig /flushdns
on Windows or sudo killall -HUP mDNSResponder
on macOS)
If the issue persists, submit a ticket to Webflow support with:
- Your Webflow project URL
- A screenshot of your DNS settings
- The error message you’re receiving
Summary:
The "403 Forbidden – OpenResty" error on a Webflow site usually stems from incorrect DNS settings or domain configuration. Double-check your A records, CNAME, default domain, and publishing status, then wait for DNS propagation. If the issue persists, contact Webflow support for assistance.