Wordpress LScache Plugin: Issue With Domain Key & QUIC.cloud Tasks
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, so Ive been pulling my hair over this issue for the past week. Please bear with me while I describe the situation in detail. There are two sites: syllabi.in (HOST-A running on LiteSpeed) & picstreak.com (HOST-B on OpenLiteSpeed). Except for the hosting, everything is the same. Both are proxied on Cloudflare, similar DNS records, no firewall rules, no mod-security nothing extra. Even same theme and codes in functions.php, and same plugins. Both sites also throw 401 errors when you try to access the LiteSpeed token (/wp-json/litespeed/v1/token). In fact, picstreak was hosted on HOST-A till a month ago, then we migrated it to the new host, so we only changed the A record in DNS. Heres the strange part: syllabi.in has no issues fetching the domain key in LS Cache plugin, despite the Rest API token being seemingly forbidden/401. Happy story till here. Cloud operations like image optimization work fine too. Cloudflare is enabled and proxy is ON. picstreak.com, on the other hand, can not get the domain key provisioned and cloud tasks have stopped working. When we pause site on Cloudflare though, it is able to get a domain key, and Im guessing QUIC-related things work normally. Tried adding a Cloudflare firewall rule to allow all QUIC.cloud IPs, but no luck. Toggled Development Mode on Cloudflare, no luck. The only thing that works is pausing Cloudflare. We can not disable Cloudflare, but whats more important is, how is syllabi.in managing to work just fine with QUIC.cloud in similar setup? Can it have something to do with OpenLiteSpeed? If there is some filter or code snippet I can use or some setting to keep Cloudflare enabled while allowing the site to work gracefully with QUIC.cloud, it would be really helpful. The only thing I have not tried is logging into HOST-Bs OpenLiteSpeed WebAdmin panel and enabling showing Client IP in the header instead of showing Cloudflares IPs. Ill be doing that now, but I dont think this will fix it. Will post an update if it does. Meanwhile, if you can figure whats causing this strange issue, Ill be grateful. had the same issue add https://openlitespeed.org/kb/show-real-visitor-ip-instead-of-cloudflare-ips/ the ips to ur openlitespeed server aswell. then restart ls and it should work. Thanks @bramokki. I was on the way here to post an update. There were two issues: 1. The glitch in OpenLiteSpeed 1.7.13 (which I was on, and which introduced automatic fetching and inclusion of QUIC.cloud IPs, we didnt have to do a thing extra). Updated to OLS 1.7.14 which claims to have fixed it. But for some reason, it didnt work for me even after upgrading to 1.7.14 (so the glitch is still there? or maybe another bug?). So, 2. Showing visitor IPs in the header instead of Cloudflares IPs. This is what youve also suggested and this is what I ran to do after opening this support topic. Added the IPs and restarted OLS, then requested domain key, and voila! It worked! So for any of you facing the same issues, 1. Update OpenLiteSpeed to 1.7.14. Check if it was fixed after updating. If not, 2. Hop into LS WebAdmin Console and follow this guide: https://openlitespeed.org/kb/show-real-visitor-ip-instead-of-cloudflare-ips/ Thanks, cheers!
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference