Purge LSCache not clearing the files

amjtn

Hi OLSPanel Team @admin

One bug. Currently cache files not purged/removed if Purge Cache performed from LiteSpeed Cache extension in WordPress

In order to clear cache we need to ssh to storagePath and manually remove. If this fixed then good else can you make New storagePath like LiteSpeed Enterprise with Necessary permissions to this directory so cache files purge from Official LiteSpeed cache WordPress plugin will work

Current:

module cache {
storagePath /usr/local/lsws/cachedata/$VH_NAME
}

Expected:

module cache {
storagePath $VH_ROOT/lscache/$VH_NAME
}

Thanks

Serg

amjtn

Hi,

You don’t need to purge cache manually over SSH. Just adjust the cache storage path in your vhost configuration so the LiteSpeed Cache plugin in WordPress has the right permissions.

Steps:

Open your vhost config file (usually in /usr/local/lsws/conf/vhosts/<domain>/vhconf.conf).
In the module cache { ... } section, replace:
storagePath /usr/local/lsws/cachedata/$VH_NAME
with:
storagePath $VHROOT/lscache/$VHNAME
Create the lscache directory inside your vhost root:

mkdir /home/<user>/<domain>/lscache

Set correct ownership and permissions so WordPress can access it:

chown -R <user>:<group> /home/<user>/<domain>/lscache
chmod 755 /home/<user>/<domain>/lscache

Restart LiteSpeed:
/usr/local/lsws/bin/lswsctrl restart

After this, the WordPress LiteSpeed Cache plugin will be able to purge cache files directly, without manual SSH cleanup.

amjtn

Hi @Serg

Thanks for your response

I already tried this but not worked. May be permissions not applied properly

cd /home/accountusername/
mkdir lscache
chmod -R 755 lscache
chown -R accountusername:nobody /home/accountusername/lscache/
systemctl restart lsws

Cache files are created in /home/accountusername/lscache/domain.com/priv/ | But not cleared on Purge All from Wordpress LiteSpeed cache plugin

Can i have the right ownership to be set for the lscache directory

Thanks

Serg

amjtn
Hi,

The issue is with ownership and group permissions. WordPress runs as your account user, but LiteSpeed runs as another system user (often nobody or lsws). If the cache directory is owned by accountusername:nobody, WordPress can create files but LiteSpeed cannot remove them.

Try the following:

Make the lscache directory owned by your site user

chown -R accountusername:accountusername /home/accountusername/lscache

Give group write permissions

chmod -R 775 /home/accountusername/lscache

Add the LiteSpeed system user (usually 'nobody') to your account group

usermod -a -G accountusername nobody

Then restart LiteSpeed:
systemctl restart lsws

This way both WordPress (running as accountusername) and LiteSpeed (running as nobody) have permission to read and delete cache files. Also double‑check that your vhost config points to the same path:
module cache {
storagePath $VH_ROOT/lscache/$VH_NAME
}

After these changes, the “Purge All” action in the LiteSpeed Cache plugin should work correctly.

Serg

If purge still doesn’t work after fixing ownership, it’s useful to check the logs to see what’s happening.

LiteSpeed error log
Look in /usr/local/lsws/logs/error.log right after you click “Purge All” in WordPress. If LiteSpeed cannot delete cache files, you’ll see permission errors there.
WordPress debug log
If you enable WPDEBUG and WPDEBUG_LOG in wp-config.php, the LiteSpeed Cache plugin will write messages to /wp-content/debug.log. This can show plugin‑side issues.
Plugin debug log
In WordPress admin → LiteSpeed Cache → Toolbox → Log View, you can enable “Debug Log.” That will display what the plugin is trying to do when purging.
Access log
Purge requests are sent as PURGE requests. You can see them in /usr/local/lsws/logs/access.log.

So, check both the LiteSpeed error.log and the plugin’s debug log. If you see “permission denied” messages, it confirms the cache directory ownership/group needs to be adjusted as described earlier (owned by your account user, group writable, and LiteSpeed’s system user added to the group).

This should help pinpoint why purge is failing.