LSCache not supported – LiteSpeed not caching my website

I’d suggest to contact Hostinger support on this case

Hello again,

When I check the source code of a web page, it shows “– Page cached by LiteSpeed Cache 6.1 on 2024-03-25 11:38:18 –“ at the end. Does this confirm that the LiteSpeed Cache is working properly even if X LiteSpeed cache isn’t mentioned in the headers?

no , that will appear in source code regardless the cache status

This is the response I have got from the Hostinger Support: “There is really not compatibility issue; website caching can only use 1, it cannot be both. You can still activate LiteSpeed, it does still improve overall however it will first serve through the Hostinger CDN.”

Is is possible that the Hostinger CDN is serving a cache page created by the LiteSpeed Cache while the headers are not displaying LiteSpeed? I mean to say that Hostinger CDN is masking LiteSpeed Cache but LiteSpeed is working fine in the background. Is it possible? Thanks for your continued support.

I don’t know the detail about Hostinger plan or what is your plan on them , but they are our partners and their server should have LiteSpeed WebServer, where it doesn’t require the Hostinger CDN to cache anything

Yes, it is on LiteSpeed WebServer. So do you mean that I should disable Hostinger CDN if I want to use LiteSpeed Cache? I actually want CDN to delivery the web pages faster to my visitors around the world. And for caching purpose, I need your LiteSpeed Cache plugin.

In further communication with Hostinger Support, I got this reponse from them:

Litespeed is a WordPress caching plugin that can work together with your CDN. Both Litespeed and CDN will cache your resources. CDN purpose is to server the cached resources of your website from Edge servers and it is commonly advantageous for visitors that are away from your origin server.

However, both are caching and improving your website’s performance. CDN caches your website’s content on it’s Edge server to server it faster while Litespeed plugin is caching your website’s content as well before it reached the CDN. It’s related to your WordPress website’s cache instead.

As mentioned, the headers do not indicate that Litespeed is not enabled. You will see Litespeed headers once CDN is disabled as we are using Litespeed web servers technology. That is not related to the plugin.

• This reply was modified 1 year ago by mevivekch.

the Hostinger CDN is not related to your original post ,

the issue you don’t get the x-litespeed-cache header

That’s what I am trying to understand. x-litespeed-cache isn’t showing in headers because of Hostinger CDN. Does this mean that LiteSpeed is caching my web pages fine? Or is it not working?

no no , it’s not because Hostinger CDN , it will show up with or without HCDN , there must be something else is off , that’s the thing I wanted to ask you to check with Hostinger support.

It’s their final reply. They are repeatedly saying that both LiteSpeed Cache and Hostinger CDN is working fine together. I want you to know that if I enable Development mode on Hostinger CDN, then x-litespeed-cache starts to show up in the headers.

Since Hostinger and LiteSpeed are partners together, these two must be compatible with each other. How I am supposed tp fix this issue if neither end is providing any solution.

anyway, you should keep HCDN off, some option from our plugin is not compatible with that

Then how I am supposed to serve my website via CDN?

LiteSpeed Cache and Hostinger have partnered with each other and they are supposed to work together. How came there be a compatiblility issue between them?

Do you have any other sample website where a website is hosted on Hostinger and LiteSpeed Cache is working fine with Hostinger CDN?

I am not sure if HCDN has configuration , but ideally , you should use it to ONLY serve/cache static resources, but not the page itself

I am having the exact same issue with Litespeed and Hostinger. This issue is set to Resolved, but in reading through it, I’m not seeing the resolution.

I have been in contact with Hostinger support, but have gotten very little from first level support. They are now elevating the issue.

If there is a solution, I would love to hear it.