Skip to content

Troubleshooting Guide

We do our best to document and provide solutions for any situation you may encounter with LiteSpeed Cache plugins. If you don't see your issue listed here, there are additional support options available.

See Also: General LSCache Troubleshooting


Before contacting the support team, please verify that you have upgraded to the most recent version of the plugin.

Common Issues and Solutions

Here is a list of common problems that people report with the LiteSpeed Cache plugin for WordPress and/or the services. If you have one of these issues, click the link and learn how to solve it.

If you don't find your issue in this list, you can check out the rest of our LSCWP Documentation or the Knowledgebase.

If you need to request assistance, please post a WordPress Support Forum topic or open a support ticket. Be sure to share your Report Number so we may assist you more quickly.


This guide covers General LSCWP Troubleshooting. If you don't find what you need here, try one of these more specific guides: - CSS/JS Issues - Media Issues - Crawler Issues - CDN Support Issues

First Steps

Verify it's an LSCache Issue

  1. LSCache plugin should be activated
  2. LSCache should be enabled
  3. Navigate to LiteSpeed Cache > Toolbox > Debug Settings and set Disable All Features to ON

Are you still having a problem? Then it is probably not an LSCache plugin issue.

Is the issue gone? Then the issue is probably related to the LSCache plugin.

Check your LSCWP Version

Our LSCWP plugin is developed at a fast pace. Some issues may have already been fixed in the latest version. You should always upgrade to the latest version before spending resources on any issue.

Pinpoint the Problem

Using the default settings, LiteSpeed Cache does not apply any optimizations, and does not alter any page content. So, it is likely that one of the settings you have enabled has caused the issue. In order to pinpoint that setting, the first thing you'll need to do is go back to the defaults:

  1. Export your current settings as a backup
  2. Reset LSCache to its default settings

If the site is still broken with the default settings, please contact our support team. However, if the site works fine with the default settings, that confirms that an option you had enabled is causing the issue.

In order to find the problematic setting, you must re-enable each of your previous settings one-by-one until you find the one that breaks your site.

With each new setting you enable, be sure to Purge All, and refresh the browser. When the issue comes back, you know you've found the problematic setting.


Purge All does not purge Critical CSS, Unique CSS, or Low-Quality Image Previews. If you are testing features related to CCSS, UCSS, or LQIP you will also need to Purge All - Critical CSS, Purge All - Unique CSS, or Purge All - LQIP Cache, respectively. Just keep in mind that CCSS, UCSS, and LQIP are services that may cost money to regenerate after purging.

When you begin re-enabling settings, the following rules of thumb can help you decide the best place to start:

  • If certain functionality or buttons have stopped working, it's likely an issue with JavaScript Optimization.
  • If pages are rendering badly, then it's likely an issue with CSS Optimization.
  • If images aren't loading properly, then it's likely an issue with Media Optimization.

Get a Report Number

If you have been through this Troubleshooting Guide, and you still require support, we may ask to see your Environment Report. The Environment Report tells us what settings you have enabled, what other plugins you have installed, and the contents of your .htaccess file, among other useful things.

To generate and share your Environment Report, navigate to LiteSpeed Cache > Toolbox > Report, scroll down and press the Send to LiteSpeed button. Make note of the Report Number that is generated, and include it in your support request so that we may look it up on our end.

Turn On the Debug Log


See a video demonstration of Debug LSCWP with the Debug Log here.

In some situations, it may be helpful to see the WordPress debug log. Because it has the potential to take up a lot of disk space, debug logging is disabled by default. To enable it, navigate to Toolbox > Debug Settings and set Debug Log to ON or to Admin IP Only. Set Debug Level to Advanced and press the Save Changes button.

You can check the generated log by navigating to the Log View tab, and pressing the Debug Log button.

If you prefer to enable and monitor the debug log from the command line, you can modify wp-config.php under WordPress' root directory as follows:

  1. Set WP_DEBUG to true: define('WP_DEBUG',true);
  2. Add the following: define('WP_DEBUG_LOG',true);

A debug.log file will be generated under the wp-content directory, and will log information whenever WordPress hits the backend.

You can monitor this log during debugging using the following command:

tail -f wp-content/debug.log

Be sure to disable logging when you no longer need it.

LiteSpeed Cache is Disabled

If you see a warning that indicates LiteSpeed Cache is disabled, the warning itself may give a clue as to the source of the problem.

Disabled at Server Level

The LSCache Module is disabled at the server level

This indicates that cache is turned off at the highest level. You will need to configure your server, or have your hosting provider do it for you.

Disabled in Plugin Settings

LiteSpeed Cache is disabled in the plugin settings

This indicates that you haven't turned on caching in the plugin settings. Do so, and the problem should be solved.

Just Plain Disabled

LiteSpeed Cache is disabled

This is a generic error that doesn't indicate any cause. Navigate to LiteSpeed Cache > Toolbox > Report and look at the Report Summary. The Server Variables section right at the top can give you some helpful information. Check the value of LITESPEED_ON. It should be true.

If this value is NULL, it means that you are not running with LiteSpeed Web Server. This is allowed, but it limits the functions that you are able to use. Learn more.

LiteSpeed Returns no-cache

If a page that should be cached is repeatedly returning no-cache, first check whether it's been explicitly excluded: Navigate to Cache > Excludes and check all of the settings. Is your page listed in Do Not Cache URIs? Or maybe it's in a category or tag that has been excluded?

If you don't see anything in the Exclude settings that should affect your page, check the dubug log. When a page is excluded from cache, you should be able to find the reason in the log. This is an example of a line from a debug log for the page, which was returning no-cache:

10/26/22 19:28:01.748 [ 1 lCD] [Ctrl] X Cache_control off - Admin configured URI Do not cache: scone

The log indicates that the page was not cached because the Do Not Cache URIs setting included the string scone. That setting prevents any page with the word scone in the URL from being cached.

WordPress Lacks Permissions

If WordPress doesn't have access to create tables in your database, please run these SQL queries manually after installation:

CREATE TABLE IF NOT EXISTS wp_litespeed_optimizer (
hash_name varchar(60) NOT NULL COMMENT hash.filetype,
src text NOT NULL COMMENT full url array set,
dateline int(11) NOT NULL,
refer varchar(255) NOT NULL COMMENT The container page url,
UNIQUE KEY hash_name (hash_name),
KEY dateline (dateline)


CREATE TABLE IF NOT EXISTS `wp_litespeed_img_optm` (
  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,
  `post_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  `optm_status` varchar(64) NOT NULL DEFAULT '',
  `src` varchar(1000) NOT NULL DEFAULT '',
  `srcpath_md5` varchar(128) NOT NULL DEFAULT '',
  `src_md5` varchar(128) NOT NULL DEFAULT '',
  `server` varchar(255) NOT NULL DEFAULT '',
  `root_id` int(11) NOT NULL DEFAULT '0',
  `src_filesize` int(11) NOT NULL DEFAULT '0',
  `target_filesize` int(11) NOT NULL DEFAULT '0',
  `target_saved` int(11) NOT NULL DEFAULT '0',
  `webp_filesize` int(11) NOT NULL DEFAULT '0',
  `webp_saved` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  UNIQUE KEY `post_id_2` (`post_id`,`srcpath_md5`),
  KEY `post_id` (`post_id`),
  KEY `optm_status` (`optm_status`),
  KEY `root_id` (`root_id`),
  KEY `src_md5` (`src_md5`),
  KEY `srcpath_md5` (`srcpath_md5`)


If your site uses a table prefix other than wp_, please replace the wp_ in wp_litespeed_optimizer and wp_litespeed_img_optm with your site's prefix.

Unable to Save Changes in WP-Admin

If you are unable to save your settings in WP-Admin, or the options are reset to their previous state after refreshing the page, there are a few possible explanations.

Accidental Caching

WP-Admin may be cached by LiteSpeed Cache or by browser cache. To see if this is the case, check the response headers, like so:

Page is not cached

  1. From a non-logged-in browser, navigate to the page, open the Network tab in the developer tools, refresh the page, and click the first listed resource. This should be the URI of the page, as described above.
  2. Look for the X-LiteSpeed-Cache-Control: no-cache header. If you find it, then the page has successfully not been served via LSCache. If the header is set to miss or hit, then LiteSpeed Cache is caching the admin page. Please check with your system administrator to be sure that Enable Public Cache is not set to Yes in the LiteSpeed WebAdmin Console.
  3. Look for two headings:
    • cache-control: no-cache, must-revalidate, max-age=0
    • expires: Wed, 11 Jan 1984 05:00:00 GMT (the value may be set to any date prior to today) If either of those headers is not present, or has a different value, the browser is likely caching your page. Typically, browser caching is accidentally enabled via bad optimization rules that add the cache control header to dynamic requests. Check your .htaccess file to fix this.
  4. If you have opcache enabled, please disable it and see if that helps. You can use the phpinfo page to verify.
  5. If you have an additional cache layer, particularly object cache with Redis or Memcached, please try disabling that.

Database Corruption

If the LiteSpeed Cache plugin's database structure is corrupted or damaged, it could cause this behavior. It's rare that this will happen, but if it does, you may repair it with the following steps:

  1. Back up your current database.
  2. Disable the LiteSpeed Cache plugin.
  3. Create a PHP file named repair.php in same directory as your wp-config.php. Copy the following contents into repair.php:
    define( 'WP_USE_THEMES', false );
    require( './wp-load.php' );
    global $wpdb;
    $table_name = $wpdb->prefix . 'options';
    $table_name = "{$wpdb->prefix}options";
    $wpdb->query( $wpdb->prepare( "DELETE FROM `$table_name` WHERE `option_name` like '%litespeed.%' " ) );
    if ( defined( 'LSCWP_V' ) ) {
    do_action( 'litespeed_purge_all' );
    echo "done";
  4. Visit, replacing with your actual domain. It should output "done."
  5. Delete repair.php, and re-enable the LiteSpeed Cache plugin. The database will be freshly created, and should work fine now.

Admin Bar is Missing

The Admin Bar at the top of the page should display on the frontend for logged in users.

Immediately after logging in, if the admin bar does not display until you manually refresh the page, this could be due to the Instant Click setting.

Here's why: When you enable Instant Click via LiteSpeed Cache > Cache > Advanced, some themes (e.g., dService, Blocksy, and more) will prefetch the home page content before logging you in. As a result, the prefetched version from browser cache does not include the admin bar.

To verify that this is what is happening, turn on the browser developer tools, check the HTTP response header for the login page request. Make sure the Disable Cache option in the tool is not selected. The HTTP response header should show the status code 200 with (from Prefetch Cache) appended. If you see this, it confirms that Instant Click is the problem.

Solution: Turn off Instant Click when using an incompatible theme.


This behavior occurs with Chrome and Microsoft Edge, but not Firefox.

Caching Issues

Forced Caching

Sometimes, in an effort to make sure that certain pages are always cached, you erroneously force the entire site to be cached. This is not a good idea, because you never know when there will be individual exceptions to caching.

Navigate to LiteSpeed Cache > Cache > Cache and look in the Force Cache URIs box. If you see / or * there, then you will need to remove it. Save, and then Purge All LSCache.

Logged-in Users Appearing as Logged-out

This problem is caused when using multiple web applications under a single domain. You can find more information on this issue and how to resolve it in our Handling Logged-in Cookie Conflicts documentation.

Cache Always Misses

If you always see X-LiteSpeed-Cache: miss in the headers, then something is wrong. Disable and then re-enable LSCache. Does that help? If not, take a look at the following scenarios and see if they apply to your site.

  • Disable and then re-enable LSCache.
  • Verify that the cache directory has the proper permissions (0755). If you don't know your cache root directory, your hosting provider can help.
  • Some CDNs have cache settings that can break LSCache and cause X-LiteSpeed-Cache: miss to appear at all times. However, accessing the backend server directly achieves X-LiteSpeed-Cache: hit. If this happens, turn off the CDN's cache functions.
  • If your domain path and your file path are different, (for example, your site is at but the files for your site are stored in a /wordpress/ subdirectory) then LSCache will be looking in the wrong place for your .htacess file. Add the following line to wp-config.php, replacing /domain_path/ with the actual path where your site's .htacess is located:
    define("LITESPEED_CFG_HTACCESS", "/domain_path/.htaccess");

Browser Displays Stale Content

Older cached versions of updated pages are being served. We've checked the response headers for the X-LiteSpeed-Cache line, and it is not found. This indicates that the page is not coming from LiteSpeed's cache, even though it should be.


The page is being served from the browser cache due to cache rules present in .htaccess (most likely in the WordPress root directory).

If .htaccess contains an ExpiresDefault cache rule, or an ExpiresByType text/html cache rule that is not set to 0 seconds, the copy stored by the browser cache will be served. The page will never be requested from LiteSpeed. Because the browser cache lacks the advanced purging rules that are the backbone of LiteSpeed's accuracy, this can result in stale content being served.


If you have no other cache plugins installed, and you have no interest in using a browser cache, then you can safely remove any of the ExpiresDefault or ExpiresByType lines.

If you want to leave the existing browser caching functionality in place, you'll need to specifically exclude the pages that are handled by LiteSpeed Cache. Add the following line above the ExpiresDefault line:

    ExpiresByType text/html "access plus 0 seconds"

If the ExpiresByType text/html rule already exists, edit it so that it matches the line above.

This rule will make it so that the pages that are cached by LSCWP are not included in the browser cache, but any other browser-cache behavior will remain unchanged.

PHP Session Issues

Some plugins, such as WHMpress, that use PHP Session to store values (currency, language...etc) don't work with LiteSpeed Cache. Once LiteSpeed Cache is enabled, user-dependent values like currency do not work or display correctly.


Pages whose content depends on PHP Session are not cache-friendly. Once the cached page is generated, it will not vary on session data.

Why? LiteSpeed Cache is designed to avoid hitting the PHP backend. Therefore, there is no way for the cache module to know what value is stored in PHP Session for any visitor other than the first one to load the page.


To make this to work, a code change to the third party plugin is required. The developer can change the plugin to store the value in a cookie and then LiteSpeed Cache can be set to vary on that cookie.

Cache Purges Too Frequently

Cache is getting purged quite often, inconsistent with the TTL settings. Some actions may unintentionally trigger a purge, and it may be necessary to do some investigation to find the culprit.

Possible Explanations

  1. LiteSpeed Cache > Cache > Purge: Have you enabled All pages, and you post frequently?
  2. LiteSpeed Cache > Cache > Purge: Have you manually added any hooks to Purge All Hooks?
  3. Do you have any plugins that are automatically enabled or disabled when a page loads?

All of these things will cause a Purge All action. If you can disable any of them, that should solve the problem.

Diagnosing the Problem

If the cause is not obvious, you'll need to do a little digging. Enable the debug log, repeat the steps that cause a purge, disable logging, and then check the log to find the cause of any Purge All actions.

Enable LSCWP Debug Log

Enable the Debug Log, chosing Admin IP only, add your IP under Admin IPs, and set Debug Level to Advanced.

Reproduce the Issue

Execute the following steps:

  • Purge All - LSCache
  • Access any page twice
  • Make sure the cache header is showing hit
  • Reproduce the steps that are suspected of triggering a purge.

In this example, let's assume you have noticed unusual purging activity when you edit a WooCommerce product's inventory. The steps your would reproduce in this case are: visit home page, edit product, visit home page again.

Check the Debug Log

LiteSpeed Cache is a tag-based caching system, so in order to figure out what is happening, you should search for the appropriate tags in the debug log. First, we look for X-LiteSpeed-Tag to find the pages that are impacted. We find the following lines, which correspond to home page, edit product, home page:

X-LiteSpeed-Tag: 87f1_URL.6666cd76f96956469e7be39d750cc7d9,87f1_F,87f1_Po.24,87f1_PGS,87f1_
X-LiteSpeed-Tag: 87f1_tag_priv,public:87f1_ESI,public:87f1_ESI.admin-bar,public:87f1_
X-LiteSpeed-Tag: 87f1_URL.6666cd76f96956469e7be39d750cc7d9,87f1_F,87f1_Po.24,87f1_PGS,87f1_

Then we search for X-LiteSpeed-Purge to find the purge action. We find the following lines:

X-LiteSpeed-Purge: public,87f1_WC_T.18
X-LiteSpeed-Purge: public,87f1_WC_T.18,87f1_Po.37,87f1_URL.c5058f4b6fbb3ed974efbe319a954e61,87f1_W.recent-posts-2,87f1_T.2,87f1_T.9,87f1_T.18,87f1_A.1,87f1_PT.product,87f1_F,87f1_H,87f1_PGS,87f1_PGSRP,87f1_D.201806
X-LiteSpeed-Purge: public,87f1_WC_T.18,87f1_Po.37,87f1_URL.c5058f4b6fbb3ed974efbe319a954e61,87f1_W.recent-posts-2,87f1_T.2,87f1_T.9,87f1_T.18,87f1_A.1,87f1_PT.product,87f1_F,87f1_H,87f1_PGS,87f1_PGSRP,87f1_D.201806,87f1_REST
X-LiteSpeed-Purge: public,stale,87f1_WC_T.18,87f1_Po.37,87f1_URL.c5058f4b6fbb3ed974efbe319a954e61,87f1_W.recent-posts-2,87f1_T.2,87f1_T.9,87f1_T.18,87f1_A.1,87f1_PT.product,87f1_F,87f1_H,87f1_PGS,87f1_PGSRP,87f1_D.201806,87f1_REST,87f1_WC_T.9
X-LiteSpeed-Purge: public,stale,87f1_WC_T.18,87f1_Po.37,87f1_URL.c5058f4b6fbb3ed974efbe319a954e61,87f1_W.recent-posts-2,87f1_T.2,87f1_T.9,87f1_T.18,87f1_A.1,87f1_PT.product,87f1_F,87f1_H,87f1_PGS,87f1_PGSRP,87f1_D.201806,87f1_REST,87f1_WC_T.9

Here's how it works: if the tag(s) in X-LiteSpeed-Purge is/are contained in the X-LiteSpeed-Tag of other pages, then those other pages will be purged during the action.

Now let's check the above tags. We will see:

87f1_F and 87f1_PGS are contained by the homepage, so it gets purged. 87f1 is the prefix. F stands for Front Page, and PGS stands for Pages. You can see a full list of tag classes in the code, if you wish.


F and PGS are triggered by the setting Auto Purge Rules For Publish/Update. If you do not want the Front page or Pages to be purged every time you update a WooCommerce item, then you need to uncheck those options.


If you see the PGSRP tag, that is for the Recent Posts Widget. You can uncheck the all pages with Recent Posts Widget setting in the auto purge rules, to keep it from purging every page on your site. If you still want to keep the widget itself updated, enable ESI for the site, enable ESI for the Recent Posts Widget, and set it to Public. That will keep the widget updated for new posts, but won't require every page it is on to be purged.

Page Content Not Updating Correctly

If your site uses a plugin that updates the content of a page without editing/saving that page, such as a "like" button that updates a counter when pressed using ajax, LSCache will not be made aware that the page should be purged from cache. As long as the now outdated copy of the page is still in cache and being served, it will appear like these changes never happened.


Add our litespeed_purge_post($pid) API call to the offending plugin to have it notify LSCache that the page should be purged.


  1. Purge the cache and with the inspector open (right click page > Inspect) access the page as a guest/non-logged in user.
  2. In the inspector, click into the Network tab and select the page request - this is usually the first entry. With this selected, click the Header tab and check that the Response Header does not contain X-LiteSpeed-Cache: hit.
  3. (If your plugin updates on each visit, skip this step) Refresh the page. You should now see X-LiteSpeed-Cache: hit in your response header. This indicates that the page was served from cache.
  4. Trigger your plugin and make sure that the page is updated as expected.
  5. Refresh the page one last time. X-LiteSpeed-Cache: hit should once again be gone from the Response Header and the page should still contain the updated information.

WP-Cron Issues

A Scheduled Event has Failed

The following notice may appear in the Health Check plugin: The scheduled event, litespeed_xxxx[image or ccss]_trigger, failed to run, Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended

For example:

The scheduled event, litespeed_imgoptm_trigger, failed to run.

Technically, this is not a LiteSpeed issue, but is due to WordPress itself. This usually happens when WP does a version update. It will usually clear up on its own in a day or so, once the WP-Cron is back to normal.

If you don't want to wait, you can disable WP-Cron and use a 3rd party cron like cPanel cron.

Scheduled Posts Not Publishing On Time

Scheduled Posts are published in WordPress through a WP-Cron job. Normally, WordPress triggers the cron job each time a request hits the backend. The backend is rarely hit, however, when using a cache, and this causes scheduled posts to publish late.

LSCWP will correctly purge the cache when a scheduled post is published in the cron job. All you need to do is make sure that you can reliably hit the backend. This can be done by scheduling a cron job to hit wp-cron.php at your ideal interval.

For Example, to update scheduled posts every 15 minutes:

    */15 * * * * wget http://your_wp_site/wp-cron.php

When using a server level cron job, WordPress suggests defining DISABLE_WP_CRON in your wp-config.php file to disable checking WP-Cron on a backend hit.

    define('DISABLE_WP_CRON', true);

This may be useful in reducing the number of calls made to WP-Cron if that is desired.

For a more in-depth discussion of this issue, see our blog.

WP-Cron PHP Timing Out

Some WordPress plugins or operations may need to run very long PHP proceses, but they may be killed by LiteSpeed Web Server with error 500 after 120 seconds. With that in mind, we have additional environment variables that will resolve that issue.


You can use the noconntimeout variable in the htaccess file. Exlude WP-Cron with this rule:

    <IfModule Litespeed> 
    RewriteEngine On
    RewriteRule (wp-cron).php - [E=noconntimeout:1]


You can use the SetEnv/SetEnvIf variable too, but we recommend using it only in a vhost file.

    <IfModule Litespeed> 
    SetEnv Request_URI "(wp-cron).php" noabort noconntimeout

For additional examples and information on how to configure the server, you can see this wiki.

Both of these variables will allow you to run PHP processes with no limits for the web pages affected by this .htaccess file. Queue Issues

Access to services is achieved through request queues. As visitors access pages on your site, if those pages need to be sent to for processing, the URLs are added to the appropriate request queues.


You have a new blog post, which has never had Low-Quality Image Replacements (LQIP) generated. When the first visitor accesses the new post, the post's image URLs will be added to the LSCWP queue.

An example of the LQIP Queue

Requests in the queue are sent to for processing on a schedule that is controlled by the cron. You may override this schedule and send requests for processing at any time by pressing the Force Cron buttons on the Dashboard or any Run Queue Manually button, located below the queue display, as shown in the screenshot above.


When you force the queue to run manually, that only means that the requests in the queue will be sent to immediately. still must process the requests, and depending on server load, that may take as much as 24 hours, especially early in the month when activity is highest.

To diagnose issues with any of the request queues, you can turn on and monitor the Debug Log. Be sure to set Debug Level to Advanced.

Third Party Plugin Issues

Google Analytics Issue

The Guest Mode incompatibility with Google Analytics has been fixed. Please update your LiteSpeed plugin to the latest version.

Currency/Language Switcher Plugins

Because these plugins are mostly PHP session-based, there's often no way for LiteSpeed to make them cacheable. The plugin author needs to change the plugin code to be compatible with LSCache. See the API for more information on how to do that.

However, if the currency switcher or language switcher uses a predictable URL query string (for example, ?new-currency=USD) when it switches, you can use rewrite rules to create a cookie and set up a cookie-based vary.


If the plugin itself already sets a cookie, you can simply add the following to the top of .htacess:

<IfModule LiteSpeed>
RewriteEngine On
RewriteRule .* - [E=Cache-Vary:plugin_cookie]
Note that plugin_cookie is just an example. You would need to replace it with the actual name of the cookie that the plugin sets.

For plugins that don't set their own cookies, here's how you would set up a custom cookie-based vary. Let's say the currency is switched on your site via this URL:

We can use the new-currency string to create a cookie that we will call currency_cookie. We'll give currency_cookie a default value of EUR, and then instruct LiteSpeed to create cache varies based on the value of the new currency_cookie, like so:

<IfModule LiteSpeed>
RewriteEngine On
RewriteCond %{HTTP_COOKIE} !currency_cookie
RewriteRule .* - [CO=currency_cookie:EUR:%{HTTP_HOST}:0:/:true:true]
RewriteCond %{QUERY_STRING} new-currency=(.*)
RewriteRule .* - [CO=currency_cookie:%1:%{HTTP_HOST}:0:/:true:true]
RewriteRule .* - [E=Cache-Vary:currency_cookie]

This ruleset must be placed at the top of .htaccess. And of course, new-currency, EUR, and currency_cookie are all examples. You'll want to replace them with the actual query string used by the plugin, your site's own default currency, and whatever name you want to use for the custom cookie, respectively.

Here's what this ruleset actually does:

  • The first RewriteCond line checks whether currency_cookie exists. If it doesn't, it sets currency_cookie=EUR to create the cookie and give it EUR as the default currency.
  • The next RewriteCond detects when the currency is switched via the new-currency query string (like in our example, where changes the currency to USD). The next rewrite rule then assigns currency_cookie the same value that it detects in new-currency (in this case, USD).
  • The final rewrite rule instructs the LiteSpeed cache engine to vary on the value of the currency_cookie cookie.

This ruleset makes it possible to have a copy of the page stored in cache for visitors using the EUR currency, and another copy cached for visitors using the USD currency.

And if someone were to visit, another copy would be cached for visitors using the AUD currency.

If you have EU Cookie Consent on your site, you will need a cache vary. Varying on the cookie allows two versions of each page to be stored in cache - one for people who have consented to the cookie, and one for those who have not yet done so.

Add the following line to .htaccess:

RewriteRule .* - [E=Cache-Vary:%{ENV:LSCACHE_VARY_VALUE}+euCookie]

Some plugins, such as the YITH WooCommerce Wishlist plugin, are incompatible with LSCache for WordPress. The simplest way to avoid cache-related problems with them is to exclude their pages from cache entirely.


If a plugin is cookie-based, you need only add the plugin's specific cookie to LiteSpeed Cache's Exclude settings.

From the WordPress Dashboard, navigate to LiteSpeed Cache > Cache > Excludes. Scroll down to Do Not Cache Cookies and enter plugin_cookie in the box. Be sure to replace "plugin_cookie" with the actual name of the plugin's cookie, as shown in the image. If you are excluding multiple cookies in this setting, make sure each cookie has its own line.


We have some known incompatible plugins on our development to-do list. We intend to fix LSCache compatibility with these plugins eventually, but for now we have set up LSCache to automatically set them to Do Not Cache.

If you are using one of these plugins, you do not have to use the manual steps above! LSCache will automatically exclude them from cache.

  1. Woocommerce Wish List
  2. WP Poll

Additional Support

LSCWP provides comprehensive optimization functionality for your WordPress installation(s). With most typical WordPress installations, LSCWP works right out of the box.

However, as WordPress has many extensions/plugins/themes available, sometimes there may be conflicts. And sometimes you just want an expert to optimize the settings for you, in order to achieve the best results possible.

In the case that you need professional handling/troubleshooting of your problem, LiteSpeed Technologies offers a WordPress Cache(LSCWP) Support Service, provided by our experienced System Engineers and LSWCP Developers, to help our clients to optimize their settings or to troubleshoot conflicts. This service is for fixing single issues. We recommend you choose the Full LSCWP Tuning for Best Website Performance option most times, since multiple issues, tuning steps, and tasks may be required to address all of the issues and improve your metrics.


LSCWP paid support is worry free. If we find a bug, support is fully refundable!

Tier 1: Free Support

We provide free community support through the following areas:

Tier 2: LSCWP Ticket Support

$39/per task

LSCWP includes a lot of functions beyond enabling/disabling the cache feature. We can help you with troubleshooting such issues on a per task basis. This service includes but is not limited to:

  • CSS/JS Optimize settings: CSS/JS Minify, CSS/JS Combine or CSS/JS HTTP2 Push. (There are restrictions. Please see NOTE 2 below.)
  • Image optimization (Optimize all images for the site, convert to WebP format)
  • Using LSCWP object cache with Memcached or Redis
  • Crawler and other available functions in LSCWP


Please turn off CDN caching before engaging us. If a CDN cache is enabled, such as Amazon Cloud Front, or CloudFlare Cache etc, you should turn it off before we begin troubleshooting. We will be unable to ensure LSCache and the LSCache plugin are properly configured if a CDN is in the way. You can re-enable it at your own risk after we have completed our work, but we can't guarantee our cache solution will work with your CDN's cache.

NOTE 2 in regards to CSS/JS Optimization

Sometimes, especially if you have a big site or many plugins installed, we will start to work and discover you have a prohibitively large number of CSS/JS files to look at. In these cases, we will ask you to engage us via Tier 5 Hourly Support, because it is a big job. Additionally, while we will attempt to identify the reason for your site's problem and provide a solution recommendation, we will not provide a custom coding service to fix your JavaScript files, since they do not contain our code.

Tier 3: LSCWP - Woocommerce Support

$59/per task

LSWCP supports the WooCommerce platform and we can help you troubleshoot problems that occur when you use LSWCP with WooCommerce.

Tier 4: Full LSCWP tuning for Best Website Performance

This service is a full LSCWP tuning for the best website performance/fixing multi issues. We recommend you choose this option most of the time since multiple steps may be involved to fix the issues and achieve better performance.

Tier 5: Hourly Support

If you have an issue that is not with the LSCWP code, but with your WordPress site's other JS/themes/plugin code, you can engage us through hourly support services.

To Order WordPress Support

Visit our Client Area.

Locate the following and press the Order Now button:

Under Configure > Configurable Options > Support Scope, select either General Wordpress Site support, Woocommerce Site support, or Full LSCWP Tuning for Best Website Performance:

Last update: October 31, 2022