Wordpress LScache Plugin: CSS frequently hitting 404 errors
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, We have an ongoing issue with quite a number of our sites now, whereby the CSS will often 404 and so the site looks awful. Weve tried tinkering with the settings across most of them, but it will randomly break and our customers will notify us that the site looks messed up. A quick look shows the CSS file(s) have hit a 404. A quick purge of the cache and everything goes back to normal. Example before purging the cache ? https://prnt.sc/1s1uylp What were really struggling to figure out why this keeps randomly happening? All of our sites have automatic updates turned off, and the majority of them have no admin access to the customer, so in theory once the site has had its cache purged, nothing should change after that so A) why does the cache need rebuilding if the site hasnt changed at all, and B) why is it failing? Any ideas what we should be looking for, or why the CSS wouldnt get refreshed correctly? Thank you This topic was modified 1 year, 2 months ago by jaythedesignhive. The page I need help with: https://wedmoreshepherdhuts.co.uk/ Hello @jaythedesignhive If you are not upgrading to lscwp v4.4 yet, please do that. Then please do a Purge All and Purge All ? CSS/JS Cache from the top bar menu button. After this, if it still happens, please create a ticket here: https://store.litespeedtech.com/store/submitticket.php. We may need to further check your site and server. Best regards, Abe Thank you, @usabe Weve updated all of our sites to v4.4 and will create a ticket should this happen again. Appreciate the support Hello @jaythedesignhive Please update to the latest dev instead. We found out v4.4 actually had another hidden bug which will also cause 404 error sometimes. Less often but it will happen for some sites. The latest dev version is v4.4.1-a2. Should be safe to upgrade to this one. Best regards, Abe @usabe Thanks. Ive just pulled in the latest version using the Use latest GitHub Dev commit button and its showing as 4.4.1-a4. Is this version safe to use? @jaythedesignhive Yes, it should be. We have kinda the same problem with many clients lately, including our own website. The only way to fix this seems to go to WordPress LS Cache plugin > Toolbox > Choose Empty all cache , not Purge all . This seems to help the issue of randomly 404 errors of .css files breaking the website. I dont get the difference. Im sure from a technical standpoint there is a reason for this, but from user perspective its confusing. Same goes for the solution mentioned above, what is the difference between: Purge All and Purge All ? CSS/JS Cache or Purge All ? When I want to Purge All Cache , I guess I would like to purge all cache, not Purge All Cache (except for the ultrasecret hidden for CIA CSS/JS) . Most WordPress users, I suspect +50%, are not very technical driven users and dont see the difference. It it hard to explain all the different options in purging. Ofcourse open to ideas!
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference