Wordpress LScache Plugin: Cant purge cache
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, I recently updated the LiteSpeed plugin on a few sites, and immediately got the broken styling issue. I tried to disable the CSS minification and purge cache, but the site still loaded the cached pages (linking to non-existent combined and minified CSS file), then I tried purging the entire cache (with OpenLiteSpeed server notification, I use an OpenLiteSpeed server, 1-click installation via DigitalOcean), but it didnt work. I even tried to disable the plugin, but the site still loaded the cached pages (still linking to broken CSS). So I assume that the plugin lost connection to OpenLiteSpeed server, because Purge Entire Cache option simply doesnt work, the server still loads its own cache (even if the plugin is disabled). I had to manually remove the cached files from the server. Please let me know how to fix it, how does the plugin talks to the server and why this connection may be broken on upgrade? This seems to be a bug because its broken on 3 sites where I upgraded this plugin. Hi, Please check in Cache ?> Purge ?> Purge Stale , if this option is set to ON , please set it OFF. Then purge all and check agian. Best regards, Thanks, but that didnt work. When I click Empty entire cache , the cache files in /usr/local/lsws/cachedata are not removed and still loaded by LiteSpeed, it seems that the plugin lost the connection to the server. I have the same issue as here https://wordpress.org/support/topic/htaccess_lscachebak-files-2/ I deleted those files but my problem persists: When I access some of my webpages, such as https://bablingua.com/recursos/nivel-inicial/, they load well, but if I reload the page the old version of the site is back. , even when the plugin is disabled. How can I test the connection between the plugin and the OpenLitespeedCache server? Maybe theres some PHP snippet for this? Hi, even your clean cache or empty entire cache , that directorys file wont be removed. you can try this
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference