Wordpress LScache Plugin: Litespeed Cache Errors
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, At present, Im using a premium cache plugin, which is giving really decent speeds over GTMetrix, Pingdom et al, but my host is insisting that as theyre running Litespeed servers, then Litespeed Cache is the way to go. The problem is, that in my hosting panel, Im getting flagged that I cannot obtain a domain key due to: /home/midland6/one-of-my-websites-thats-not-even-live ? Detected WordPress version as . Version 4.0 . required at minimum. /home/midland6/public_html ? [LOG][3] Install is flagged /home/midland6/public_html/another-none-existant-website ? [LOG][3] Install is flagged My host has been on there most of the day trying to prove that its a better plugin, but LSC has even uninstalled itself twice now due to these errors, which doesnt bode well for a reliable plugin. Sure its giving some decent-ish results, but all in all, its pretty diabolical in that weve needed to dactivate WordFence, my AntiSpam plugin, and probably a couple of others now that have internal caches to make LSC work properly, but even so with no QuicCloud account. Is there no way to stop jumping through hoops to get a QuicCloud account and use LSC as it was intended, viz-a-viz to optimise my cache, images and scripts? Hi, Is that cPanel plugin ? please dont use cPanel plugin to manage LiteSpeed Cache , its not compatible with v3 at this moment. and please try use wp-admin to install and activate the cache plugin no , you dont have to deactivate them , just make whitelist QC IPs in these plugins so it wont block the communications between plugin and node. Best regards, The plugin was already installed on my initial install, but I got rid of it in favour of my premium cache plugin Those errors above show in cpanel>> Litespeed Web Cache Manager, and each new website needss to have the LSC plugin installed to allow LSC to work. The latest error message reads (from WP Admin): Notice: There is a problem receiving your domain key. Please click the Waiting for Approval button to retry. There are two reasons why we might not be able to communicate with your domain:: 1) The POST callback to https://my-website/wp-json/litespeed/v1/token failed. 2) Our Current Online Server IPs was not whitelisted. Please verify that your other plugins are not blocking REST API calls, whitelist our server IPs, or contact your server admin for assistance.: Just below that message, there is another one about QuicCloud online services, which reads: A domain key is required for QUIC.cloud online services. For online services to work correctly, you must whitelist all online server IPs. Before generating key, please verify all IPs on this list are whitelisted: Current Online Server IPs ?and then in the online server ips link, there are around 50 (FIFTY) yes, really FIFTY, ips that need to be whitelisted, and thats not including WordFence, my antispam plugin, and all the others that arent re-activated yet. Back to my original question then, how to you activate LSC without needing to jump through hoops? Im not interested in the slightest on uploading half a plugin with half the functionality, so until then, Ill go back to my premium plugin. Hi, how to you activate LSC without needing to jump through hoops? I am sorry , English is not my native language , I am not sure what do you mean by jump through hoops ? Best regards, Jumping though hoops means ? how do you activate Litespeed Cache without having to disable all the other plugins? Hi, You dont. you only have to add IPs into whitelist if there is any issue happens , like our request being blocked , otherwise you dont even need to do whitelisting. Best regards, Well thats not what the LSC plugin was telling me, when it said that ALL ips must be whitelisted before I could use the online services. Also my host seemed to have no answer when it was pointed out that on a warning message in the web manager, it declared that LS Cache is enabled but is not caching. Also, I was unable to get a domain key to use all of the services due to the reasons listed above. At present, we cannot possibly trust LSC to optimise our websites when its giving off so many errors and trying to force us to use half or less of the resources available on live websites. Hi, Yes, you MUST whitelist the IPs if your configuration is blocking it. But depends on security level you set, some peoples site doesnt need to, some does. no answer when it was pointed out that on a warning message in the web manager Please provide report number , you can get it in toolbox -> report, then click send to LiteSpeed It will provide some basic information for us to check. I was unable to get a domain key to use all of the services due to the reasons listed above If your firewall or security plugin is blocking communications between plugin and node, and you dont or you cant whitelist IPs, then Im sorry to say there is no other way around. Without domain key, some basic features like caching should still work, but some advanced features that requires node communication will not work. its giving off so many errors and trying to force us to use half or less of the resources available on live websites As for now, the only error I am seeing is domain key, due to no whitelisted IPs I am not sure what do you mean by resources part? After re-read the whole topic, top to bottom, I see your point is that you feel really annoying and troublesome to whitelist 50 IPs across multiple security plugins? If that is the case, then I am sorry to say there is no solution to this case besides whitelist IPs Security , or more restricted security measures , comes with more inconvenience. And with all due respect, this is kind of like you want a barber to do your haircut but you cuffed his hands and dont give him the scissor? Best regards, Not really a case of giving the barber a pair of scissors though, is it? LSC refuses to do anything unless a QuicCloud domain key is obtained, which Ive already mentioned above, cannot be obtained. Even though Im on a Litespeed server, it still insists on a QuicCloud domain key, which is a little daft as I thought that was the reason my host recommended LSC? Itll work straight out of the box for basic caching? But it doesnt, as LSCache is enabled but is not caching. And you yourself already said that the webserver is not compatible with v3? Whats all that about then? Rather than giving my barber a pair of scissors, please make sure that theyre sharpened and fit for purpose before using them. Hi, Not really a case of giving the barber a pair of scissors though, is it? Well, depends on hairdo you want, it can be done by one scissor, or more scissors are required, at least each time I got haircut, the barber uses at least 3 different scissors and one electric machine I dont know how to say in English. LSC refuses to do anything unless a QuicCloud domain key is obtained, Then there must be something wrong, either server side or plugin side, because all the feature that doesnt need domain key will work, like caching, CSS combine, CSS Mindy, JS combine, minify? etc And you yourself already said that the webserver is not compatible with v3? No, what I said is cPanel plugin is not compatible with LSCWP v3.x, not the web server. And please provide the report number I asked ,I will check some basic info first. Best regards. Regarding resources between my premium cache plugin and LSC: HTTP requests on LSC ? 72, premium cache ? 27 Speed LSC 4.8 secs, premium cache ? 1.4 secs Page size LSC ? 3.80mb, premium cache ? 1.2mb Though trying out the core web vitals performance, LSC was indeed better. So there is definitely something in this LSC plugin, if only we didnt have to jump through so many hoops to get it working. Thought Id do a final press with this, and I added the 50-odd ip addresses to the whitelist in Wordfence. Still no change as far as quic-cloud was concerned, my domain key is probably lost in outer space somewhere. So then onto the page optimisation, where as it was mentioned that LSC could still optimise this resource without the aid of a quic-cloud key. On seeing that my page speed had now swelled up to 7.8 seconds, I finally decided to pull the plug on it. Horrendous results from a plugin that was initially recommended by my host but failed miserably on-site, means that theyll all need to visit the barbers and have their heads shaved. Id personally recommend that QuicCloud gets dumped in the bin along with the head shavings. Hi, Could you please provide the report number I asked ? I can check why cache not working or what happens to domain key request. You have problem with plugin , I get it , I am trying to help you out, but in order to do so, I would need the information I request. Best regards, Sorry no, I did mention in the last post that Id pulled the plug on it. Hi, Sorry to hear this. Wish you all the best Best regards, Im sorry as well, as it did at least show promise on the core web vitals aspect, but the user-unfriendliness of Litespeed and QuicCloud (with each other) trying to force their own aspects on security plugins, plus even my own Litespeed host provider not being able to figure it out, and still failing to pull through suggests theres something wrong with LSC in its present form.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference