BugWP logo BugWP
Back to Community
Home / Community / Plugin → Litespeed cache

Why Your LiteSpeed Cache Isn't Working: A Troubleshooting Guide

31 threads Sep 16, 2025 Plugin → Litespeed cache

Content

Is LiteSpeed Cache Causing Issues on Your Site? Here's How to Find Out and Fix It

Many WordPress users rely on LiteSpeed Cache for its powerful optimization features. However, like any complex plugin, it can sometimes conflict with other elements of your site, causing unexpected behavior. Based on common issues reported by users, this guide will help you diagnose and resolve the most frequent problems.

Common Symptoms of LiteSpeed Cache Issues

Users often report problems such as:

  • A blank "LSCache is not supported" message on the cache settings page.
  • Specific site features breaking (e.g., booking calendars, 'Load More' buttons, comment forms pre-filled with another user's data).
  • Site styles appearing broken or incorrect.
  • The cache not clearing properly, even after disabling the plugin.
  • New scripts or code changes from a child theme's functions.php not appearing on cached pages.

Step 1: Confirm LiteSpeed Cache is the Source

Before making complex changes, your first step should always be to confirm that LiteSpeed Cache is actually the source of the problem. The official LiteSpeed Cache documentation provides a simple method for this:

  1. Navigate to LiteSpeed Cache > Toolbox > Debug Settings.
  2. Set Disable All Features to ON.
  3. Visit the page where you are experiencing the issue.

Is the problem gone? Then the issue is likely related to the LiteSpeed Cache plugin's configuration.
Are you still having the problem? Then the issue is probably not caused by LiteSpeed Cache, and you should investigate other plugins or your theme.

Step 2: Basic Troubleshooting Steps

If you've confirmed LiteSpeed Cache is involved, try these common fixes:

1. Purge All Caches Thoroughly

Sometimes, a simple purge isn't enough. Go to LiteSpeed Cache > Toolbox and use the Purge All function. If you are using a Content Delivery Network (CDN) like Ezoic, remember you must purge its cache separately for changes to take effect.

2. Check for Server-Level Support

The plugin requires a LiteSpeed web server to function fully. If you see a message like "LSCache is not supported," you must verify your hosting environment. Use a tool like check.lscache.io or contact your hosting provider to confirm that LiteSpeed Enterprise or OpenLiteSpeed is running on your server.

3. Identify and Isolate Conflicts

Conflicts with other plugins or your theme (like Divi Builder) are a very common cause of issues.

  • Disable other plugins: Temporarily deactivate all other plugins except LiteSpeed Cache. If the problem resolves, reactivate your plugins one by one to identify the culprit.
  • Switch to a default theme: Temporarily switch to a WordPress default theme (like Twenty Twenty-Four) to see if the problem is caused by your current theme.

4. Manage Cache TTL for Dynamic Elements

Features that rely on AJAX, like 'Load More' buttons or post like counts, can break if the cache doesn't expire quickly enough. If a nonce (a security token) is disappearing after cache is generated, try reducing the Time-To-Live (TTL) for the specific page or post type to a shorter period (e.g., less than 8 hours) to ensure dynamic elements update properly.

Step 3: Advanced Configuration Checks

If basic steps don't work, delve into these specific settings:

Object Cache Groups

If you are using Object Caching (e.g., with Redis) and a plugin like FacetWP stops updating, you may need to exclude certain WordPress object cache groups. Identifying the correct groups often requires consulting the documentation of the plugin that is malfunctioning.

ESI and User-Specific Caching

For sites with logged-in users, ensure settings like Cache Logged-in Users or ESI are configured correctly. Note that ESI is not available on OpenLiteSpeed (OLS), only on LiteSpeed Enterprise Server (LSWS).

Exclusions

Use the Do Not Cache rules in the plugin's settings to exclude specific pages, cookies, or user agents that are causing problems. This is often the best solution for pages containing highly dynamic elements like booking calendars.

When All Else Fails: Generate a Report

For deeper, more technical issues, the LiteSpeed Cache team often requests a report number to investigate. You can generate this by:

  1. Going to LiteSpeed Cache > Toolbox > Report.
  2. Clicking Send to LiteSpeed.
  3. Providing the generated 8-character code (e.g., HTJJDPMZ) when seeking help from the community.

By methodically working through these steps, you can usually identify and resolve the conflict causing LiteSpeed Cache to misbehave on your WordPress site.

Related Support Threads Support