Issues with LiteSpeed ​​Cache

  • Resolved sergialarconrecio

    (@sergialarconrecio)


    3 years, 3 months ago

    Hello, good.

    I am writing because I have problems with the LiteSpeed ​​Cache plugin that does not generate the “x-litespeed-cache” in the header and when I have the LiteSpeed ​​Cache Crawler activated and the process ends, the web is not displayed and what is displayed is the header code as unable to read cached web from “x-litespeed-cache”.

    I am waiting for a solution, as the technical support of the hosting I am contracted to told me to contact you. The only cache plugin on the web is “LiteSpeed ​​Cache”.

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • serpentdriver

    (@serpentdriver)

    3 years, 3 months ago

    x-litespeed-cache header exists, but if quic.cloud is used this headers name is x-qc-cache: https://i.postimg.cc/N0CtxLbM/cache.png

    Thread Starter sergialarconrecio

    (@sergialarconrecio)

    3 years, 3 months ago

    So if so, yes and I activate LiteSpeed ​​​​Cache Crawler, why does it not work properly and it makes me a Cache Miss cache and the web stops being displayed once the cron Crawler process is finished, showing the web header then being well displayed and cached successfully in LiteSpeed ​​Cache Crawler.

    serpentdriver

    (@serpentdriver)

    3 years, 3 months ago

    There is no real reason why the crawler shouldn’t work. The crawler only simulates URL requests, which is the same as a normal user would visit a page. Unfortunately, your information is not very meaningful, so that one can recognize from it what the problem is. It might help if you take a screenshot of the page after the crawler is finished.

    Thread Starter sergialarconrecio

    (@sergialarconrecio)

    3 years, 3 months ago

    I attach URL of the screenshot to better see the problem that I mentioned.
    https://drive.google.com/file/d/1ROZKxpeEPnDu0xXT8zlnhPo9JN9NFB41/view?usp=sharing

    serpentdriver

    (@serpentdriver)

    3 years, 3 months ago

    Did you install any Service-Worker plugin?

    Thread Starter sergialarconrecio

    (@sergialarconrecio)

    3 years, 3 months ago

    Not to my knowledge, but I don’t know if it could be the next plugin that affects the cache, the “Progressive Web App”.

    I have the Offline browsing function of Progressive Web App disabled because there is no incompatibility with LITESPEED.

    serpentdriver

    (@serpentdriver)

    3 years, 3 months ago

    I have the Offline browsing function of Progressive Web App disabled because there is no incompatibility with LITESPEED.

    Who did that say?

    Anyway, lscache plugin works. If it doesn’t the reason for malfunctions is mostly caused by users they don’t really know what they are doing. I respect it when users make an effort to optimize their page, but you have to be careful with it. Any changes involve the risk of malfunctions. This applies equally and especially to plugins. In any case, your problem is self-inflicted. Therefore, it’s your job to find out which setting or plugin is causing this problem.

    Your page uses server worker and this could be the reason for your issue!

    Thread Starter sergialarconrecio

    (@sergialarconrecio)

    3 years, 3 months ago

    Could it be that PWA v0.7.1 is causing the problem when using “wp_front_service_worker” from the “wp.serviceworker” file

    serpentdriver

    (@serpentdriver)

    3 years, 3 months ago

    Could it be that PWA v0.7.1 is causing the problem when using “wp_front_service_worker” from the “wp.serviceworker” file

    Disable this functions and see what happens. I am very sure that this is the cause.

    • This reply was modified 3 years, 3 months ago by serpentdriver.
    Thread Starter sergialarconrecio

    (@sergialarconrecio)

    3 years, 3 months ago

    Deactivate the PWA v0.7.1 as you can see on the web, but the same thing happens with the web, once the process in LiteSpeed ​​Cache Crawler is finished and forced to cache those non-cached webs, the web continues to look the same and has not been solved the problem.

    Thread Starter sergialarconrecio

    (@sergialarconrecio)

    3 years, 3 months ago

    I close as a result because with the support technician I solved the problem

    The support technician is: Ruikai Wang at LiteSpeed ​​(@qtwrk)

    The solution was to disable multiPHP compression and disable zlib.output_compression, as LiteSpeed ​​server has its own compression enabled by default, and also remove from wp-config.php the parameters I added for compression.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Issues with LiteSpeed ​​Cache’ is closed to new replies.