WebGee DocsDocs
WordPress

Prevent LSCache from auto-installing

Flag a WordPress installation so WebGee's automated process does not install LiteSpeed Cache on it, and set the same exclusion for every new account.

WebGee automatically enables LSCache across WordPress installations on its servers, to improve site performance and reduce server load. Flagging an installation opts it out. Applies to all shared and reseller hosting.

To turn off a cache that is already running, see Disable LSCache. Most people need both.

Flag an installation

  1. Log in to cPanel and open LiteSpeed Web Cache Manager.
  2. Select WordPress Cache.
  3. Select Scan to find the WordPress installations on the account.
  4. Select Flag beside each domain you want excluded.

This writes a .litespeed_flag file into the site's document root. The server reads that file and leaves the installation alone.

Because the exclusion is a file in the document root, it travels with the site. Restoring a backup taken before you flagged the site removes the file and the exclusion with it. Check after any restore or migration.

Exclude every new account

Resellers can have the flag applied to accounts automatically by placing a .litespeed_flag file in the skeleton directory. cPanel copies the skeleton directory's contents into every new account it creates, so every site starts flagged.

Skeleton directories are a cPanel feature; see cPanel's own documentation for how to create one.

When you should not do this

LSCache is the main reason WordPress is fast on LiteSpeed hosting. Opting out means every page is generated by PHP on every request.

Flag a site when you are running a different page cache, or when the application genuinely cannot be cached. Do not flag it because a single page showed stale content — exclude that page in the plugin instead.

Verify

Confirm .litespeed_flag exists in the site's document root using cPanel's File Manager with hidden files shown, or over SSH:

ls -la ~/public_html/.litespeed_flag

On this page