Site health page shows no cache plugin.

this is known issue because it doesn’t check our header despite the page caching is actually there.

we will address it in next release.

I think you’re right, when the website don’t have ssl, i don’t get this error.
It’s something with the SSL.

Now another thing i want to ask…

When you say: we will address it in next release.

It’s mean in the plugin level or the open litespeed server level?

If it is in the plugin level, it’s ok.

But if this is in a server level, it’s demand a new deployment on GCP?

in your screenshot , you see it checks some pre-defined headers for page cache , in which ours , the x-litespeed-cache , x-qc-cache and x-lsadc-cache headers are not in default list , there is a plugin filter we can use , to add our headers into the list

Still didn’t get you.
And from what i see it’s a problem in a server level (your image/deployment on Google Cloud marketplace)

I pretty sure your plugin cant fix it, the issue is the headers is in HTTP
but not apply to HTTPs

I notice to other panel (port 7080)
and the problem start from there…

This image you have on Google Cloud is not a full solution.
And have a lot of issues here.

Don’t know if you can fix it with a WordPress plugin.
this isiue is little bigger from what you think.

if you think it’s not plugin related issue but server-side issue , please create a ticket by mail to support at litespeedtech.com

best regards,

You need to pay for Enterprise, you don’t actually have support for this product (it’s an open source)

The funny thing, you told on your first message is a common issue…
I think you need to be worry much more than me, this is your company selling
this images/deployment on Google cloud (maybe this is the reason for the common issue)

I will try to submit them a ticket but from my experience is only “Enterprise” license.

Hi,

the first post you have published , was about the health tool , that was the case where I have explained in first reply

the health tools check for http response header , the ones in your screenshot https://imgbb.com/ZM8HYkH , but our header x-litespeed-cache is not among them , that’s why you get that information , despite you actually have the page cache in place

I am not exactly sure or understand what is your second post about , but if you think it’s server-related issue , please use the ticket system

and we take OLS ticket as well , not only enterprise

best regards,