Use Cloudflare in front of WebVue Cloud
Proxy mode, SSL mode and the settings that break WordPress when they are wrong.
The platform already runs behind a Cloudflare Enterprise edge. You do not need your own Cloudflare account. If you keep one — for a domain shared with other systems, or for Workers — these settings matter.
SSL mode
Set encryption mode to Full (strict). Flexible mode makes Cloudflare talk to us over plain HTTP, which produces redirect loops and mixed-content warnings in WordPress.
Settings to avoid
| Setting | Problem |
|---|---|
| Rocket Loader | Defers scripts in a way that breaks admin screens and page builders. |
| Auto Minify on JavaScript | Occasionally corrupts third-party bundles with no error. |
| Caching everything at the edge | Caches logged-in pages and carts unless you write careful bypass rules. |
| Always Use HTTPS plus a WordPress redirect plugin | Two redirects fighting each other produce a loop. |
Bypass rules for WordPress
Bypass cache when URI path starts with:
/wp-admin
/wp-login.php
/cart
/checkout
/my-account
Bypass cache when cookie contains:
wordpress_logged_in_*
woocommerce_items_in_cart
Visitor IP addresses
With your own proxy in front, the origin sees Cloudflare's addresses. We restore the real client IP automatically for our edge; tell support if you add a second proxy layer, so rate limiting and logs stay accurate.