Search results

You are right, but in this specific case private data is relative. Ultimately, it is your decision. CSF may be more effective, but CSF filters at a deep network layer. This allows you to filter IP addresses very well, but filtering specific IP addresses is like fighting windmills.

This is probably because you are using the standard filters provided by CF. These actually do not work as expected. However, with a little brainpower and without paid plan, you can set up custom filters that work 100%. I filter about 7500 requests every day.

Use CloudFlare WAF. It is always better to use any external service to filter unwanted traffic like bad bots.

Since the documentation does not provide any information about this, you should contact LiteSpeed Support directly. support@litespeedtech.com

Follow the steps for Toggle Debug Logging. The steps for WebADC and LSWS are the same. https://docs.litespeedtech.com/lsws/cp/cpanel/debug-log/

Try this: https://docs.litespeedtech.com/lsadc/zeroconf/#optional-debug-log

This seems to be an OpenLiteSpeed error, so you better should ask OLS support as this forum is for LiteSpeed Enterprise. https://forum.openlitespeed.org/

Yes, but you have wrong cache-control settings for browser cache for dynamic scources cache-control: public, max-age=172800 It must be private, no-cache, max-age=0, so check the .htaccess

Caching and using of the most important functions for page optimizations needs the LiteSpeed web server, but you don't have this web server installed.

FYI: There is no Googlebot User-Agent named "samrtphone bot" or "smartphone bot ". If you want to exclude the Googlebot just enter "Googlebot". This bot name is only used for crawling and not by the InspectionTool. If want to exclude the InspectionTool just enter "Google-InspectionTool". To...

Therefore, you do not have to use the browser version, but rather clear and unchangeable designations: "Googlebot" and nothing else.

There is nothing to fix. Settings to exclude certain User-Agents are correct and the x-litespeed-cache-control header is correct as well: "no-cache" and this is what you want to achieve.

User-Agent for Google Inspection Tool: Mozilla/5.0 (compatible; Google-InspectionTool/1.0;) https://developers.google.com/search/docs/crawling-indexing/google-common-crawlers

The inspection tool doesn't use Googlebot User-Agent. If you want to check if it works use any browser extension or plugin to change the User-Agent of your browser. There is no need to use any external services. User-Agent for Googlebot (Desktop): Mozilla/5.0 (compatible; Googlebot/2.1...

It works.

This forum is for LiteSpeed Enterprise only. For OLS please use OLS support forum. https://forum.openlitespeed.org/

FPM is not supported by cPanel, so disable it.

Then this can't be an issue that is caused by LiteSpeed and you should ask XenForo support for help.

The server cache doesn't matter for static sources, but the browser cache, so if you use a different browser always purge the browser cache and press Strg + F5 keys if you want to check it.

@craigward The issue could be caused by the loading="lazy" HTML attribut im <img> tag. Safari browser only supports this feature since version 16.4, or since 2023. This means that users with an older browser will not see any images. https://caniuse.com/?search=loading%3D%22lazy%22