Title: webmasterfsd's Replies | WordPress.org --- # webmasterfsd [ ](https://wordpress.org/support/users/webmasterfsd/) * [Profile](https://wordpress.org/support/users/webmasterfsd/) * [Topics Started](https://wordpress.org/support/users/webmasterfsd/topics/) * [Replies Created](https://wordpress.org/support/users/webmasterfsd/replies/) * [Reviews Written](https://wordpress.org/support/users/webmasterfsd/reviews/) * [Topics Replied To](https://wordpress.org/support/users/webmasterfsd/replied-to/) * [Engagements](https://wordpress.org/support/users/webmasterfsd/engagements/) * [Favorites](https://wordpress.org/support/users/webmasterfsd/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 21 total) 1 [2](https://wordpress.org/support/users/webmasterfsd/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/webmasterfsd/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Major Caching Bug in LiteSpeed Crawler – Version 7.1](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 1 month ago](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/#post-18470520) * Thank you, you’ve understood the issue correctly. * I updated the hosts file as suggested, and it resolved the problem on my end. I’ll continue using this workaround and will wait for the official fix in the next release. In the meantime, could you please keep this ticket open so I can continue to track the progress? * Thanks again for your assistance. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Major Caching Bug in LiteSpeed Crawler – Version 7.1](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 1 month ago](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/#post-18467277) * Okay, Thanks I’m waiting for the update. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Major Caching Bug in LiteSpeed Crawler – Version 7.1](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 1 month ago](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/#post-18466219) * Hello , * Thank you for pointing me to `crawler.cls.php` line 945 and suggesting I log the `$resolved` value. What I’ve tried 1. **Standard PHP `error_log()`** `error_log( '[LSCache Crawler] Domain resolved to: ' . $resolved );` 2. **Type-3 `error_log()` to a custom file** `error_log( '[LSCache Crawler] Domain resolved to: ' . $resolved . PHP_EOL, 3, WP_CONTENT_DIR . '/litespeed/debug/ custom.log' );` 3. **`$this->log()` (plugin’s internal logger)** `$this->log( '[Helper] Domain resolved to: ' . $resolved );` * Results - **`public_html/error_log`** – No entries. - **`wp-content/litespeed/debug/custom.log`** – File created but remains empty. - **`/wp-content/litespeed/debug`**/**`crawler\*.log` (UI “Crawler Log”)** – Still blank after several crawler runs. * **Despite that, none of the three logging methods record anything. ** * Could you please take a look from your side? Here’s what I’m seeing on the latest LSCache: - After a full **Purge All** and several manual crawler runs, the blue/green hit-miss counts stay exactly the same every time. - No new log entries appear in any log (Crawler Log, debug/crawler*.log, or PHP error_log). - It feels like the crawler is running but i think acutally isn’t running at all, or is stuck somewhere or not resolving the correct IP. * If you can trigger the crawler on your end and let me know what you observe ( and any steps you take to check resolving IP), I’ll replicate them here to compare results. * Thanks in advance for your help! * Best regards, * Thank you for your assistance. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Major Caching Bug in LiteSpeed Crawler – Version 7.1](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 1 month ago](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/#post-18464219) * Note: Server IP is correctly configured at quic.cloud * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Major Caching Bug in LiteSpeed Crawler – Version 7.1](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 1 month ago](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/#post-18464215) * Hello, * I’ve done some debugging and identified that the plugin behaves differently when a CDN is active on the frontend. To test this, I temporarily pointed the site back to the origin server, and the plugin cralwer started working as expected. * It seems the plugin is not using the server/origin IP defined in the General Settings. Although the correct IP is already configured, the crawler appears to be hitting the CDN instead, which is likely causing the issue. * Is there a fix or recommended solution to ensure the plugin uses the origin IP as intended, even when a CDN is active? * Thank you. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Major Caching Bug in LiteSpeed Crawler – Version 7.1](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 1 month ago](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/#post-18464184) * Yes, you got it, the 2nd , 3rd time returning all exact same number as 1st run and showing same blue/green marks numbers. screenshot here: [https://prnt.sc/7ctziCUvGNLN](https://prnt.sc/7ctziCUvGNLN) no matter how many times I rerun it I got the same numbers and To confirm this, I visited several pages manually in an incognito browser session after the second crawler, 3rd cralwer…, and almost all page still showing a cache miss status. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Major Caching Bug in LiteSpeed Crawler – Version 7.1](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 1 month ago](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/#post-18464129) * If you refer to my initial message in this ticket, I clearly mentioned that I tested the issue by manually running the crawler twice. Later, I ran additional tests by manually triggering the crawler more than two times, but the issue still persists. I’ve confirmed this behavior across multiple sites. However, when I revert to the older plugin version (as noted in my first message), the issue no longer occurs — all pages are properly cached on the second run and appear under green status. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Major Caching Bug in LiteSpeed Crawler – Version 7.1](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 1 month ago](https://wordpress.org/support/topic/major-caching-bug-in-litespeed-crawler-version-7-1/#post-18459962) * Okay, I sent the report, please review it and here is Last Report Number: **LITYPGAD** and Last Report Date: **05/11/2025 05:15:40** note: when respond me, please don’t mention my site or domain name here. Thanks for understanding. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Critical Issue: LiteSpeed Crawler Adding All Posts to Blocklist After Update](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 2 months ago](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/#post-18389926) * here is screenshot on latest plugin v7: [https://prnt.sc/9qXPQWscrmLS](https://prnt.sc/9qXPQWscrmLS) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Critical Issue: LiteSpeed Crawler Adding All Posts to Blocklist After Update](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 2 months ago](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/#post-18389910) * Yes, I cleared the blocklist after all running crawlers completed their jobs. Then, after cleaning, I reran the crawlers—but the results were the same: all ended up in the blocklist across all sites. * I reverted all sites back to the older version and tried upgrading again, but the issue still persists. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Critical Issue: LiteSpeed Crawler Adding All Posts to Blocklist After Update](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 2 months ago](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/#post-18389904) * Yes, I’ve already cleared the blocklist before each crawler run. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Critical Issue: LiteSpeed Crawler Adding All Posts to Blocklist After Update](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 2 months ago](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/#post-18389901) * Yes, this is happening on the latest version (v7). * The server/domain IP and all other settings are correctly configured, but nothing seems to resolve the issue. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Critical Issue: LiteSpeed Crawler Adding All Posts to Blocklist After Update](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 2 months ago](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/#post-18389886) * I’ve tried it a couple of times and encountered the same issue across multiple sites—not just a single one. * However, there’s another site with the exact same settings where this issue doesn’t occur. I didn’t encounter any issues after reverting to the older version.I must say, something seems to have gone wrong with the recent updates. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Critical Issue: LiteSpeed Crawler Adding All Posts to Blocklist After Update](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [1 year, 2 months ago](https://wordpress.org/support/topic/critical-issue-litespeed-crawler-adding-all-posts-to-blocklist-after-update/#post-18389881) * The log shows that every URL the crawler processes is immediately being marked as “Blacklisted” even though the HTTP response code is 200. This is unusual because a 200 status normally means the page loaded successfully. Here are some potential issues to investigate: 1. **Misconfiguration in the Crawler Settings:** The crawler appears to be interpreting every successful page load as a condition to blacklist it. Check your LiteSpeed Cache crawler settings to see if any rules or conditions are set too aggressively— perhaps a misconfigured exclusion or “uncacheable” condition is causing the crawler to block all pages. 2. **Plugin or Software Bug:** The repeated “Update map reason [code] 200” suggests the plugin might be misinterpreting the normal page responses. It’s worth checking if you’re running the latest version of LiteSpeed Cache and reviewing known issues or patches related to crawler behavior. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[LiteSpeed Cache] Failed to communicate with QUIC.cloud server: Your application is waiting for ap](https://wordpress.org/support/topic/failed-to-communicate-with-quic-cloud-server-your-application-is-waiting-for-ap/) * Thread Starter [webmasterfsd](https://wordpress.org/support/users/webmasterfsd/) * (@webmasterfsd) * [5 years ago](https://wordpress.org/support/topic/failed-to-communicate-with-quic-cloud-server-your-application-is-waiting-for-ap/#post-14533483) * Here is my Report number: YAIINGIN * Report date: 06/08/2021 15:01:57 Viewing 15 replies - 1 through 15 (of 21 total) 1 [2](https://wordpress.org/support/users/webmasterfsd/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/webmasterfsd/replies/page/2/?output_format=md)