Wordpress LScache Plugin: Automatic image optimization not working for new images
Last Updated on: Wed, 15 Apr 2026 00:00:02 When new images are uploaded to my site, Litespeed does not automatically optimize them. So I go to the image optimization panel and click Send Optimization Request and I get this error: Previous requests that optimized but not pulled: 7 . ^It hangs on a variety of numbers It helps by clicking on Clear Up Unfinished Data and then Send Optimization Request. All images are optimized (so cron works fine), but when new ones are uploaded, I have this problem again. It is quite annoying that I have to check it every day and manually clear this data and send the optimization request again. It didnt happen a while ago. Maybe its the fault of the latest WordPress or PHP 7.4? Report number: JQPKQGNQ This topic was modified 2 years, 8 months ago by Rafal Calka. Hi, From report , the image optimization server failed to fetch the image , and therefore cause it stuck there and stopped. Please add our IPs into CF firewall whitelist then clean up unfinished data , then try again. Best regards, Hi @CacheCrawler Thanks for reply. I have added your IP addresses to the white list. Now it works, thanks! @CacheCrawler Unfortunately, the problem returned Hi, https://img.YOUR_______DOMAIN.com.pl/images/user-images/czujny/2016/10/50%-taniej_mytaxi-960?517.jpg please check your CDN the link gives 400 bad request error , thats why it failed. Best regards, Hi @CacheCrawler I deleted this image because it was broken. Automated optimization worked for one day and the problem returned again. Where can I check the full list of images that cause problems? Hi, Currently you cant , it only shows on image server side , which is not accessible by end-user. Perhaps you could try v3.0 preview , which re-worked the image optimization workflow. but its not ready for production site. you can also try clean up unfinished data and re-send the request, see how it goes. Best regards, Hi @CacheCrawler Thanks for response. After clearing the unfinished data several times, it works for now. When will production version of 3.0 be released? @CacheCrawler The problem keeps coming back
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference