Wordpress LScache Plugin: Image Optimization
Last Updated on: Wed, 15 Apr 2026 00:00:02 Litespeed Image optimization limit stuck at 1. Here is what all things I tried 1)Destroyed the earlier optimization 2)Whitelisted quic.cloud ips In the quic.cloud dashboard I am getting error notifications as well 1) Failed to retrieve image for optimization Failed to retrieve image File not found from node File not found. 2) Failed to notify WP to pick up optimized images Unable to notify WordPress to pick up images. Check QUIC.cloud IPs are whitelisted at the firewall. Please help The page I need help with: https://www.knifeguides.com/ Your site blocks access, first of all, to download a bunch of images (returning a 403 forbidden ) when the images are being fetched. Notifying WordPress fails due to your WordPress site restricting access to the REST API: code : rest_authentication_error , message : Sorry, you do not have permission to make REST API requests. , data : status :401 The image optimization service will do a callback to the WordPress REST API under the /wp-json/litespeed namespace, so ideally youd want to whitelist that full namespace. If youre using a security plugin in WordPress that does this REST API protection, youll often have the possibility to whitelist specific namespaces or endpoints. If youre having manual code added to your theme, youll have to modify the code to not restrict REST API access for the /wp-json/litespeed namespace, or whitelist the quic.cloud IPs in the code. Hi Lucas, Thanks for your fast reply. I had a code in htaccess that would restrict hotlinking. It was copied from https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cpanel:enable_hotlink_protection For the REST API, I had the plugin perfmatters which disabled the API. But before I was making this thread I had it disabled, because I had seen your other replies asking the users to do the same. I can access it on /wp-json without any problems. I also have just flushed quic.cloud can also incase if the cached version was the culprit. And now it just started working again. No idea if it was the hotlinking protection that created the problem. Thank you for your help @ormonk I can see the hotlink protection used above would indeed cause the 403 errors for the images. Ill get that fixed today, the hotlink protection expects a trailing slash, which currently isnt being sent when trying to fetch the image, so Ill add the trailing slash.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference