Fix LSCache showing disabled in LiteSpeed Cache for WordPress

LiteSpeed Cache for WordPress (LSCWP) reports "disabled" in its dashboard for one of four reasons: the wrong advanced-cache.php is in place, WP_CACHE is missing from wp-config.php, the server-level cache module is off, or another caching plugin is fighting for the same drop-in. Work through them in that order — they're listed by frequency, not difficulty.

The single most useful diagnostic is a curl -I against a cacheable URL. If the response carries X-LiteSpeed-Cache: hit or miss, the cache is working and the dashboard label is lying. If the header is missing entirely, the server isn't seeing LSCache directives at all.

curl -sI https://example.com/ | grep -i x-litespeed

1. Wrong advanced-cache.php drop-in

LSCWP installs wp-content/advanced-cache.php on activation. If WP Rocket, W3 Total Cache, or WP Super Cache were ever installed, their drop-in often persists and LSCWP refuses to overwrite it. Check the file header:

head -5 /home/user/public_html/wp-content/advanced-cache.php

A LiteSpeed drop-in starts with // LiteSpeed Cache. Anything else — WP Rocket, W3TC — and LSCWP marks itself disabled. Delete the foreign drop-in, deactivate and reactivate LSCWP, and confirm a new file appears with the correct header.

2. WP_CACHE missing from wp-config.php

LSCWP's drop-in only runs when WP_CACHE is true. Some hardening scripts and managed-host wrappers strip it. Grep for it:

grep WP_CACHE /home/user/public_html/wp-config.php

If absent, add it above the /* That's all, stop editing! */ line:

define( 'WP_CACHE', true );

LSCWP normally writes this on activation. If it can't (file is read-only, owned by root, or immutable), fix the permissions before reactivating.

3. Server-level LSCache is off

The plugin is a client for the server's cache module. If the module is off, the plugin reports disabled even when everything in WordPress is correct.

On LSWS (Enterprise): the cache module ships enabled but per-vhost caching needs cache enable 1 in the vhost or context. The WebAdmin path is Virtual Hosts → example.com → Cache → Enable Cache. The same setting works from .htaccess at the docroot:

<IfModule LiteSpeed>
CacheLookup on
</IfModule>

On OpenLiteSpeed: the cache module is a separate install. From WebAdmin, Server Configuration → Modules → cache must be present and enableCache set to 1 in the parameters. Without it, OLS strips LSCache headers entirely. Restart OLS after the change.

If you haven't run through the initial wiring, the full sequence is in enable LSCache for WordPress on cPanel.

4. Plugin conflicts

Any other full-page caching plugin will compete for the drop-in and the WordPress hooks. Common offenders:

• WP Rocket
• W3 Total Cache
• WP Super Cache
• WP Fastest Cache
• Hummingbird (page caching module)
• Autoptimize (only when its "Cache" minify module is misconfigured against LSCache)

Pick one. LSCWP handles minification, image optimisation, and object cache itself — running it alongside WP Rocket halves the value of both.

Verify with the response header

After each change, hit a public URL and look for the header:

curl -sI https://example.com/ | grep -i -E 'x-litespeed|cache-control'

A working setup returns X-LiteSpeed-Cache: miss on the first request and hit on the second. If you see pass, the request matched a non-cacheable rule (logged-in cookie, query string, admin URL). If the header is absent entirely, you're back to step 3 — the server isn't processing LSCache directives.

For sites without HTTP/3 enabled yet, this is also a good moment to turn it on — see enable HTTP/3 QUIC on LiteSpeed with cPanel. And if the plugin disable message coincides with an Enterprise licence problem, check your key is still valid against a paid LiteSpeed licence.

Next steps

• Wire LSCache from scratch with enable LSCache for WordPress on cPanel.
• Push protocol gains further by enabling HTTP/3 QUIC on LiteSpeed.
• If the disabled state coincides with licence errors, renew or order at LiteSpeed licence.