Cache crawler for Prestashop/thirtybees does not want to cache on new server

#1
I have this thirty bees installation since years and previously used it with the Prestashop cache module (including the latest version from github) and the cache crawler with no issue - 2 runs a day - always the cache worked.

Now I've migrated to A2 hosting and there the cache crawler is returning always 'No Need To Cache' for every single page - the warmup is not running.

When I visit the site I get 'hit' on second page load but never on the first page load after the cache warming was just completed.

The only change I did is to add Cloudflare - later I saw that it might not play nicely with litespeed crawler and cache and completely removed CF from my site (returned the original name servers) bot no luck with this too.

Another thing I noticed is that in cache/litespeedcache/ there are no files on the new host (never). On the old host I have few .data files there.

I feel something is different on the server configuration but I'm unable to saw what as it's shared hosting and I have no access.

Also on the new host I received 'unable to add product to cart' popup when I'm browsing the site with added product to the cart so I tried -c switch on the crawler and it appears to solve the issue. But what is the connection if the crawler is not working?!

Can you give me a hint?
 

Attachments

#2
I think I narrowed down the issues.

1. With -g switch the crawler is working normally, normal user experience in term of caching in FO. When I remove it the crawler stumbles again. What configuration option on the server could be causing this.

2. The popup is probably caused by disabled ESI hole punching on server level, as the switch is disabled in my module. Can this be configured also on the server?

I'm talking with their CS but I would appreciate any info. Thanks!
 
#4
Thank you @serpent_driver

1. Server is running, LS cache is available as second click returns 'hit' header. The issue with the crawler was that it was not enabled for the domain (very strange, I think this should be enabled by default).
2. It's made for PS but it works flawlessly on thirty bees also. I think Litespeed should advertise this.

The second issue with the ESI remains - can I control this by htaccess or it's strictly server side configuration? On my previous host the ESI switch in the module was active and I could select YES/NO. On this server currently it's greyed out and block cart of course misbehaves.

Regarding your KITT crawler - would you support thirty bees? I tried it yesterday and it says "No Prestashop install". The native crawler works for me fine because mine shops are not big but it might be useful for other merchants.

Thanks for your support!
 

serpent_driver

Well-Known Member
#5
1. Server is running, LS cache is available as second click returns 'hit' header. The issue with the crawler was that it was not enabled for the domain (very strange, I think this should be enabled by default).
I don't see any LiteSpeed cache header!?

header.png

Regarding your KITT crawler - would you support thirty bees? I tried it yesterday and it says "No Prestashop install". The native crawler works for me fine because mine shops are not big but it might be useful for other merchants.
Kitt for PrestaShop expects PrestaShop to be installed. thirty bees isn't supported.

The second issue with the ESI remains - can I control this by htaccess or it's strictly server side configuration? On my previous host the ESI switch in the module was active and I could select YES/NO. On this server currently it's greyed out and block cart of course misbehaves.
ESI must be enabled in LiteSpeed WebAdmin console.
 
Last edited:
#8
Thank you, I didn't know this is shown there. For my main domain I have:

Code:
$_SERVER['SERVER_SOFTWARE']    LiteSpeed
$_SERVER['REQUEST_METHOD']    GET
$_SERVER['X-LSCACHE']    on,crawler
But for my addon domains I only have:


Code:
$_SERVER['SERVER_SOFTWARE']    LiteSpeed
$_SERVER['REQUEST_METHOD']    GET
$_SERVER['X-LSCACHE']    on
So I assume ESI should be shown on this row. Currently I have no mention of it in the report.
 

serpent_driver

Well-Known Member
#9
The settings in WebAdmin are globally, so if lscache, the crawler and ESI are enabled, these settings should be available on all domains. You can check it by creating a custom test php file.

  1. Create a custom php file
  2. and enter
    Code:
    <?php echo $_SERVER['X-LSCACHE']
  3. upload this file where you use LiteSpeed
  4. and run this file in browser

Code:
on,crawler, esi
should be displayed
 
#10
The settings in WebAdmin are globally, so if lscache, the crawler and ESI are enabled, these settings should be available on all domains. You can check it by creating a custom test php file.

  1. Create a custom php file
  2. and enter
    Code:
    <?php echo $_SERVER['X-LSCACHE']
  3. upload this file where you use LiteSpeed
  4. and run this file in browser

Code:
on,crawler, esi
should be displayed
Thank you,

I get: "on,crawler" on one of the domains and only "on" on all other domains (the crawler does not work when called through the addon domains). So this should be some domain setting on their side?
 

serpent_driver

Well-Known Member
#11
If you have access to the LiteSpeed WebAdmin complete the settings, otherwise and if you are on Shared Hosting contact A2 support as the crawler must be enabled for every domain and sub-domain. On Shared Hosting the ESI function is enabled by default at A2.
 
#12
I'm on Turbo shared account and no, neither ESI, nor crawler are enabled by default. Yesterday they enabled crawler only on one of my domains and today I'm talking to new guy at their support for the rest and global ESI.

Could they do this on account level so I don't have to wait for support for every new domain I add?
 

serpent_driver

Well-Known Member
#13
A2 supports the crawler, but it must be enabled for every domain and sub-domain (on shared hosting plan), so if you have the crawler support requested wait for confirmation.

btw. The Kitt cache crawler isn't limited by any restrictions!
 
#16
Yes, I get exactly 1 response in 24 hours from them but obviously the 2 dudes up until now have not heard for those settings on their side and the communication continues with 1 response a day. :)
 

serpent_driver

Well-Known Member
#17
If you want the crawler to be enabled you must notify the A2 support on which domain or sub-domain you need the crawler. A2 support is good, but not every (first level) supporter is a specialist for LiteSpeed, so you should give as much information as possible to redirect your need to a LiteSpeed supporter.
 
Top