Wordpress LScache Plugin: Watch shows 1970 date and no sitemap
Last Updated on: Wed, 15 Apr 2026 00:00:02 Using: LiteSpeed Cache Crawler v3.6.4 The cache seems to work fine. First page load is usually a miss, followed by a hit for subsequent reloads. However, trying to get the crawler to create the cache automatically is having a variety of issues. In the Watch Crawler Window I am seeing the default date of 1970: Start watching... 01 Jan 1970 01:00:00 Size: 0 Crawler: #2 Position: 1 Threads: 0 Status: end 01 Jan 1970 01:00:00 Size: 0 Crawler: #1 Position: 1 Threads: 0 Status: end ........................................ The top of the screen shows: `Current sitemap crawl started at: 3s ago The next complete sitemap crawl will start at: 08/13/2021 23:58:36 Last complete run time for all crawlers: 8 seconds Current crawler started at: 3s ago` May be unrelated, but regardless of what sitemap XML feed I put into the box on tab 6, tab 2 is blank and refresh attempts just show No valid sitemap parsed for crawler. (Same issue as 1970 topic here this post however the solution doesnt work) (Screenshot of Tab 1, if it helps) Report number: VTBNVAGB Report date: 08/10/2021 13:24:33 Hi, Please try set Drop Domain from Sitemap to OFF in Crawler > Sitemap Settings, then refresh the sitemap, see how it goes. Regards, Lehan No difference, still says No valid sitemap parsed for crawler. and displays zero entries in Tab 2. Tab 1 still shows 1970 in Watch Crawler Status please try enable debug log to check what has happened during fetching sitemap to build crawler URL list Hi, Im going to mark this topic Resolved , due to lack of activity. If you still need help, please feel free to re-open it. When re-open it, please also change the topic status to not solved Best regards, Hi @CacheCrawler ? sorry I didnt receive any emails saying there had been a response on here. I already had debug switched on but no actions I did (clear / rebuild crawl list, fetch sitemap etc) produced any errors in the logs. However, this issue was resolved as soon as I upgraded to Litespeed Cache v 4.2. Not sure if that contained a fix for the issue or if just the process of upgrading / refreshing files etc caused things to start working. All seems okay now Thanks for your supported.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference