Cloudflare proxy no longer works with new Webflow publishing rules — how to keep worker-based functionality?

Publishing help Hosting
1

Hi everyone,
I manage many Webflow projects that rely on Cloudflare Workers to provide functionality Webflow doesn’t support natively. Previously, I could simply point my DNS to cdn.webflow.com with Cloudflare proxy enabled and everything worked.

With the new publishing rules, Cloudflare proxy can no longer be used, which breaks all our worker-based logic and removes the ability to extend Webflow through Cloudflare.

Has anyone faced the same issue?
How are you handling this change, and is there any workaround to keep Cloudflare Workers in the flow?

Thanks!

3

All of my sites are reverse proxied and Webflow makes this easy.
You want the O2O configuration.

https://help.webflow.com/hc/en-us/articles/45039458051347-Using-Cloudflare-Orange-to-Orange-O2O-with-Webflow

4

Hi Vadim, did you find an answer to this?

I have the same problem? I am running a Link-In-Bio type service so it is crucial to control the url so it looks like this : domain. com/username

Would this work with O20 ? Apparently they now force you to an enterprise plan for this, I don´t think thats worth it

5

Where did you get that idea?

I use the O2O configuration on all of my sites, it works beautifully.

https://help.webflow.com/hc/en-us/articles/45039458051347-Using-Cloudflare-Orange-to-Orange-O2O-with-Webflow#h_01K60AQGVXX3DSZP5WVBAERWRM