WP Rocket Not Working? 10 Fixes (From Common to Obscure)

By /
Affiliate Disclosure: Some links on this page are affiliate links. If you purchase through these links, I may earn a commission at no extra cost to you. Learn more.

WP Rocket is the gold standard for WordPress caching. But when it stops working, your site can feel slower than before you installed it. At Rocket.net, I troubleshoot WP Rocket issues weekly—usually finding the fix is one toggle away from the obvious.

Here are 10 fixes ordered from most common to most obscure. Start at the top.

1. Is Caching Actually Enabled?

Check WP Rocket → Dashboard. The cache toggle should be ON (blue). Sounds obvious, but I have seen cache disabled after:

  • Plugin updates that reset settings
  • Staging syncs that copied dev configuration
  • Security plugins that auto-disable caching

Also verify: WP Rocket → Cache → Enable caching for mobile devices. If unchecked, mobile visitors get uncached pages—often 50%+ of your traffic.

2. Check Your Exclude Rules

WP Rocket → Advanced Rules → Never Cache URL(s).

Common mistake: Excluding /checkout/ also excludes /checkout/thank-you/ and /checkout/* if you used wildcards wrong. Overly broad exclusions kill caching.

Fix: Use specific URLs. Instead of /account, use /account/ (trailing slash matters).

3. Cloudflare Conflicts

If you use Cloudflare with WP Rocket, they can fight:

  • Both caching HTML: WP Rocket generates static files, Cloudflare caches HTML at edge. This is fine—but purge them together.
  • Auto Minify conflicts: Cloudflare’s minification + WP Rocket’s file optimization = broken CSS/JS.

Fix: Cloudflare → Speed → Auto Minify → OFF. Let WP Rocket handle minification.

Also sync purges: WP Rocket → Add-ons → Cloudflare → Add API credentials. Then cache clears sync.

4. File Optimization Breaking the Site

WP Rocket → File Optimization. These settings commonly break sites:

  • JavaScript defer/delay: Inline scripts break
  • Remove unused CSS: Aggressive removal affects dynamic content
  • Combine CSS/JS: Can break HTTP/2 optimization

Diagnostic: Disable File Optimization entirely → test site → re-enable one by one.

5. File Permissions Issues

WP Rocket writes to /wp-content/cache/. If permissions are wrong:

  • Cache files fail to generate
  • Preload stalls
  • Settings do not save

Fix: Check that /wp-content/cache/ is writable (755 or 775). WP Rocket has a built-in permissions check: Tools → Site Health.

6. Server-Level Caching Conflicts

Some hosts have their own caching that conflicts:

  • SiteGround: SuperCacher can double-cache
  • WP Engine: Proprietary caching layer
  • Cloudways: Varnish + Redis

Fix: Choose ONE caching layer. On Rocket.net, disable WP Rocket page caching and use server caching + WP Rocket for file optimization only. Server-level caching is faster.

7. Membership/E-commerce Cache Issues

WooCommerce and membership sites have dynamic content that cannot be cached:

  • Cart contents
  • User-specific pricing
  • Logged-in user dashboards

Fix: WP Rocket → Advanced Rules → Never Cache Cookies:

woocommerce_items_in_cartwordpress_logged_in

Also exclude /cart/, /checkout/, /my-account/ from caching.

8. CDN URL Mismatch

If using WP Rocket’s CDN feature with the wrong URL:

  • Assets 404
  • Mixed content warnings
  • SSL errors

Fix: WP Rocket → CDN → verify URL matches your CDN exactly. Include scheme: https://cdn.yoursite.com

9. License Issues on Multisite

WP Rocket licenses are per-site. On Multisite:

  • Network activation requires per-site license
  • Or use WP Rocket Multisite add-on

Fix: Check WP Rocket → Account → License status on each subsite.

10. Fatal Errors Reporting False

WP Rocket → Tools → Log. Check for:

  • Memory exhausted during preload
  • Timeouts on slow pages
  • Plugin conflicts (last plugin activated before issues started)

Fix: Increase PHP memory limit: wp-config.php → define('WP_MEMORY_LIMIT', '512M');

When to Try Alternatives

WP Rocket is excellent but not the only option:

  • LiteSpeed Cache: Free, feature-rich, but requires LiteSpeed server
  • W3 Total Cache: Free, complex configuration, powerful when tuned
  • Server caching: Rocket.net, Kinsta, Cloudways have built-in layers

If WP Rocket consistently conflicts with your stack, try LiteSpeed Cache (if on LiteSpeed) or rely on server-level caching with Perfmatters for optimization.

Getting Real Help

WP Rocket support: Excellent documentation and responsive tickets. Include your system report (WP Rocket → Tools → Export).

Your host: Caching conflicts are often host-specific. Rocket.net can tell you exactly why WP Rocket settings conflict with server configuration.

Bottom Line

WP Rocket not working is usually a configuration conflict, not a plugin failure. Work through these 10 fixes systematically—most issues resolve at steps 1-3.

If you are spending more time fixing WP Rocket than it saves, consider whether your host’s built-in caching is sufficient. Sometimes simpler is faster.

Need help diagnosing conflicts? My speed diagnostic includes full caching stack analysis and recommendations for your specific hosting setup.

Related Posts

Scroll to Top