Wordpress LScache Plugin: Lots of images not optimized
Last Updated on: Wed, 15 Apr 2026 00:00:02 More than half of my sites have optimized all their images, but several are stuck, and quic.cloud shows this error in the Last Optimized Images list: Error: Fetched md5 mismatch One site is not behind Cloudflare, but the others are, and Ive put them in Development Mode. For all sites, Ive cleaned the Unfinished Data, Rescanned New Thumbnails, Destroyed All Optimization Data. What can I do to move on and either fix the md5 mismatch error, or just skip that file? The images in question are working on my site. Heres one such image: https://mwba.org/wp-content/uploads/2019/03/2019-MWBA-PB-Date.jpg Hi, Could you please provide the report number and also the md5sum mismatch , it should provide a md5sum , please also provide that string. Best regards, Thanks! Report # is DLPIRJTS Error: Fetched md5 mismatch: [latest] d41d8cd98f00b204e9800998ecf8427e [ori] 1bb77ae71072aba57dff94633e602ecc https://mwba.org/wp-content/uploads/2019/03/2019-MWBA-PB-Date.jpg Heres my theory: The three domains with these errors are on Cloudflare paid plans, which include image optimization (Polish and Mirage). Im going to turn those features off overnight and see if that works. If that is the problem, then why? Is QUIC fetching images from my site, rather than the plugin pushing them directly to QUIC? Update: No joy. After disabling Polish and Mirage, then purging Cloudflare cache and waiting overnight, the error persists. These are the ONLY domains on Cloudflare paid plans. All the free plan domains arent having this issue. Now I see that in every failure, every domain, every image, has the same Latest md5 checksum: d41d8cd98f00b204e9800998ecf8427e This leads me to believe that whatever is trying to pull the image is getting the same response. Probably some Forbidden message. How can I find out whats making the request, and/or the raw data of the request? Looking through Cloudflare logs, I cant find any warnings. Server logs also arent providing any insight. Go figure?a case of bad timing. I didnt configure my VPN firewall to allow direct connections from the server to itself. Since this process connects to its own IP address, and not through the IP address of the Clouflare proxy, it was getting blocked by the firewall at my VPN. Case Closed.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference