The LiteSpeed WHM plugin contains a section for managing LiteSpeed Cache for WordPress. This wiki entry will guide you through the different operations and management actions you can take when using our plugin.
If you do not see the LiteSpeed Cache For WordPress Management section on your LiteSpeed WHM plugin screen, please upgrade LiteSpeed Web Server to 5.1.x at the minimum.
You must have a license with LSCache enabled to use these features. How To Get LSCache
Note: Before using these features, please set the necessary Server Configurations.
From the initial plugin screen you should be presented with 4 different options under the LiteSpeed Cache For WordPress Management section.
The first option is Manage Cache Installations which you can use to manage LiteSpeed Cache for WordPress on your individual WordPress installations.
The second and third options are Mass Enable Cache & Mass Disable Cache, which can be used to enable/disable LiteSpeed Cache for WordPress on all discovered WordPress installations with are not flagged (more on flags later).
The last option is the Version Manager which displays the currently active LSCache for WordPress version (more on the Active Version later). It also allows you to adjust this active LSCache for WordPress version and to upgrade and downgrade LSCache for WordPress installations based on their current version.
The manage view is where most of the magic happens. Here you can manage LiteSpeed Cache for WordPress for your WordPress installations individually or in small groups. (There is nothing wrong with big groups, but that is what Mass Enable Cache and Mass Disable Cache are for)
Starting from the actual table we have the following fields:
Looking at the top row of buttons, we have Scan/Re-scan, Discover New, and Refresh Status.
public_htmlfolder. These discovered installations will then be saved to a data file and displayed in the manager screen. If this data file is removed or corrupted, simply scan again to repopulate the list.
Moving on we have the the bottom row of buttons which are used to perform group operations. These buttons work in tandem with the check-boxes found next to each discovered installation to allow you to perform some basic operations for only the selected group.
Both of these selections behave in a very similar way by allowing you to enable/disable LiteSpeed Cache for WordPress en masse.
When Mass Enabling/Disabling LiteSpeed Cache for WordPress, all WordPress installations that are not currently flagged in the Manage screen will have LiteSpeed Cache for WordPress installed/removed. If a WordPress installation is detected as manually disabled, the WHM plugin will flag it and skip it. During this operation, you should see the following output screen.
After this operation is complete you will get a short summary message letting you know how many installations had LiteSpeed Cache for WordPress enabled/disabled successfully and how many failed, as well as how many flagged installations were detected and skipped over. You will also be provided with both an error log and a success log shown under these results listing the installations that were enabled and those that failed along with the related error messages.
Note: If you have not performed a scan before clicking on Mass Enable/Disable Cache buttons, or your previous scan data is unable to be read by the plugin, you will be asked to scan again.
This screen searches for Server level cache root definitions in either the
/usr/local/apache/conf/includes/pre_main_global.conf file or in the LiteSpeed Web Server Web Admin under
Server > Cache > Cache Storage Settings > Storage Path setting.
If it is defined in
pre_main_global.conf it should look something like this:
<IfModule LiteSpeed> CacheRoot /home/lscache/ </IfModule>
/home/lscache/ is the CacheRoot path. In this case, the Server level cache root will be set to
This screen searches for VHost level cache root definitions in the
If it is defined in
lscache_vhosts.conf it should look something like this:
<IfModule LiteSpeed> CacheRoot lscache </IfModule>
lscache is the CacheRoot path. In this case, the VHost level cache root will be set to
Set Missing Cache Roots - Sets Server level and VHost level Cache Root definitions if they are detected as not set.
Note: The Set Missing Cache Roots button will only appear if at least one of the two cache roots (Sever level and VHost level) is detected as not set.
Test your domains, you should see “X-LiteSpeed-Cache: hit” in the response header. Check here for detailed verification steps.
If “X-LiteSpeed-Cache: hit” can not be seen, you may need to do more troubleshooting, for example: check if LScache feature has been enabled in your license, if other cache plugins have been disabled, or if cache root and cache policy have been set, etc.