What made you say that? My server has litespeed – https://prnt.sc/7EfBGt7GPhj8
I am on Cloudflare; you can use Cloudflare along with Litespeed. One more thing: when I deactivate the Cloudflare proxy, the Lightspeed plugin still cannot cache the pages. There is something wrong with this plugin.
That’s what I mean; even without Cloudflare, the http headers still don’t show HIT for LiteSpeed, but the LiteSpeed server is there. If not, how come the website can run. Litespeed is the web server.
Update: Temporarily, I uninstalled this plugin and used another caching plugin to test. And the other caching plugin works flawlessly. I don’t know why this plugin is not working.
Yes, that’s the other plugin I mentioned above.
When you replied about another layer of cache, I had already installed Flypress to replace the LiteSpeed plugin. The Litespeed plugin cannot even do the caching. The response headers showed that LiteSpeed is not working (this is before I installed Flypress, and cloudflare has been deactivated)
Now the website is back with Cloudflare and FlyingPress.
Did you read what I wrote properly?
I said the plugin was not even working before I used the flying press. When I posted this thread, I had not installed Flypress yet. This is what I faced chronologically:
Litespeed plugin+cloudflare = not working
Litespeed plugin without cloudflare = not working
Remove LiteSpeed, install Flypress, and it works now (this is the current)
I hope you understand that. I never use two caching plugins at the same time.
Of course you see that, because I have removed litespeed plugin because its not working, even without flyingpress and cloudflare. The caching is not even started with litespeed plugin.
I need to remove the LiteSpeed plugin because this is a client website. I cannot let it slow without caching for too long. Right now, flyingpress do the job.
If you want to see the problem that I faced earlier, can I do it on the staging site?
Plugin Support
qtwrk
(@qtwrk)
the LSCache requires LiteSpeed WebServer, OpenLiteSpeed, LiteSpeed ADC or QUIC cloud CDN to work , since your site/server doesn’t have any of it , that’s why it won’t work there.
@qtwrk
Ok I don’t mind if the LSCache Check detector is not working, my concern was more why the plugin cannot start the caching.
Plugin Support
qtwrk
(@qtwrk)
emmm? that’s exactly what I am trying to say , the caching function , requires aforementioned software to work with
the plugin itself does NOT cache any page by its own , instead , it sends out some cache-directive-headers , where our webserver software will follow
