What is the plan for companies that use a reverse proxy (e.g., proxy.webflow.com, proxy-ssl.webflow.com) with the recent Cloudflare migration announcement? I even tested using cdn.webflow.com instead, but it seems it wasn’t intended for this use (it doesn’t work).
I could not find anything about this. Any help will be appreciated!
Hi there,
When using a reverse proxy, you might continue seeing the “Update needed” message in Site settings > Publishing > Production even after updating your proxy origin to Webflow’s new DNS records. This message can be safely ignored, and you can continue publishing your site.
To clear any errors in your reverse proxy setup, you’ll need to temporarily add these DNS records:
Once the error message clears, update your DNS records according to Webflow’s new DNS configuration by following the How do I manually migrate my DNS records? guide.
Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.
If you’re using Cloudflare workers as your reverse proxy, use the O2O configuration for your DNS.
For other RP’s, I’m not certain. Check with support and share your findings.