Help! Recurring Cloudflare Error 1014 with Weglot Subdirectories after Webflow Migration

Publishing help Hosting
1

Hi everyone,

I’m reaching out to the community because I’m stuck in a “support loop” between Webflow and Weglot, and I’m hoping someone here has found a permanent fix for this.

The Setup:

  • Multiple client sites hosted on Webflow.

  • Using Weglot with subdirectory integration (Reverse Proxy).

  • Everything was working perfectly until the Webflow infrastructure migration (Oct 30, 2025).

The Problem: Since the migration, we are getting recurring Cloudflare Error 1014 (Cross-User Banning). This seems to trigger specifically when Webflow attempts to renew or revalidate SSL certificates. The site goes completely black until we manually remove Weglot or ask Webflow support to “trigger a manual SSL refresh.”

What Support says:

  • Webflow Support confirms the error is due to their recent infrastructure upgrade combined with third-party proxies. They explained that since Webflow and Weglot both use Cloudflare, it creates a “cross-zone” conflict that Cloudflare blocks for security. However, they won’t provide a permanent fix because Weglot is a 3rd party tool.

  • Weglot Support points back to Cloudflare/Webflow settings.

The Question: Has anyone successfully resolved this 1014 Error without having to manually refresh SSL every time?

Is there a specific DNS configuration or a “Cloudflare bypass” that we should implement to allow these two Cloudflare zones to talk to each other without being flagged as unauthorized?

Any advice or workarounds from people using Weglot subdirectories on the new Webflow hosting would be life-saving!

Thanks in advance!

2

Hi Salome,

I do not use Weglot, but I work with reverse proxies a lot. This sounds like a special circumstance, but to my knowledge the burden would be on Weglot to correctly configure their reverse proxy so that it’s passing the correct headers etc for Cloudflare.

This could also be related to the Orange to Orange configuration- if your DNS is pointing to Weglot, then Weglot ends up in the chain during SSL renewals and might not be communicating properly. Webflow itself had this issue with reverse proxies until it released the Orange-to-Orange DNS configuration. Weglot might need the same.

Only direct recommendation I can give you is to-

  1. Switch to Webflow localization :laughing: depending on your feature set needs.
  2. Or, consider building your own reverse proxy. It’s unlikely Weglots RP is complex, it likely sits on top of their JS delivery solution. But you’d need a bit of knowledge regarding where the translated assets are stored so you can integrate them. Weglot might even have a repo you can download it from. If you can self-host it in your own cloudflare account, you can use O2O and resolve that renewal issue.

Before anything, run your problem through Chatgpt deep research. It’s good at finding obscure forum discussions and solutions you may not locate through Google.