Search results

Sorry, give up. I am unable to teach you why it is not possible using LScache or/and reCapchta at the origin host with CloudFlare HTML cache at the same time. Try Gemini, ChatGPT or any other KI. But Note: Hostinger CDN cache is not the same as LiteSpeed Lscache on origin host.

Furthermore, bypassing html cache doesn't disable the CF cache. Define cache rules only for static sources!

If you are using the LiteSpeed cache, you must disable the dynamic source (or HTML) cache in the CDN (Hostinger, Cloudflare, etc.), regardless of whether reCAPTCHA is used or not. This is not a LiteSpeed-specific limitation, but a general rule. 1 cache + 1 cache ≠ 2 caches If a dynamic source...

As long as you're using a second cache layer in the CDN, reCAPTCHA simply won't work. A CDN cache doesn't recognize reCAPTCHA at the origin host and therefore caches it as well. The image shown should make this perfectly clear!

Note: 1 cache + 1 cache != 2 caches and causes conflicts, so disable Hostinger cache.

Documentation is your friend... https://docs.litespeedtech.com/

An account can have multiple domains, so you cannot disable reCaptcha in 1 single .htaccess to address all domains in a account. It must be specified in and for each document_root

Disable Hostinger CDN cache and try again.

This forum is about LiteSpeed web server related issues. For issues that are related to the LiteSpeed cache plugin for WP you better should use the LiteSpeed plugin support in WP support forum or contact quic.cloud support. This forum doesn't support the LScache plugin for WP any longer...

If you have cPanel/WHM OCSP Stapling is controlled by WHM. The OCSP Stapling configuration in LS WebAdmin is for native use if no server control panel is installed. https://docs.litespeedtech.com/lsws/cp/cpanel/ocsp-stapling/#enable-ocsp...

I didn't suggest this: RewriteCond %1 !=%{REMOTE_ADDR}

Server variables (%{REMOTE_ADDR}) cannot be used for "CondPattern" as Apache and LiteSpeed expect an expression for the CondPattern. For example, this would work: RewriteCond %{REMOTE_ADDR} !^127\.0\.0\.1$ If you really need to compare a cookie with the client’s IP, use the newer expression...

Try this code and use CIDR from googlebot.json but aware that Google changes this list almost daily. allow 66.249.0.0/16; allow 64.233.160.0/19; ... # more CIDRs deny all;

Your code has a serious errors.... RewriteCond %{REMOTE_ADDR} !^173\.245\. RewriteCond %{REMOTE_ADDR} !^103\.21\. RewriteCond %{REMOTE_ADDR} !^103\.22\. # Add more IPs RewriteRule .* - [F,L] Such IPs are not Google bot, but Google Cloud related, mostly bad bots RewriteCond %{REMOTE_ADDR} ^34\.

If you're only focused on PageSpeed, you don't need any training. Once the LiteSpeed web server is installed, install the LScache plugin for WordPress and select a preset. That's it. The presets work very well 9 out of 10 times. The cache function is set automatically by the cache plugin, so no...

Please post the code.

@LSWSEv634Noob You should not "abuse" the .htaccess if you want to block a huge list of IPs. Blocking by htaccess is not free and costs load. Better use WAF/Proxy or CDN. Blocking IPs by ranges (173.245.48.0/20) doesn't work in .htaccess, neither in LiteSpeed nor in Apache. Define a simple...

https://docs.litespeedtech.com/lsws/cp/cpanel/recaptcha/

reCaptcha cannot be controlled cPanel account, but by WordPress installation or document_root. Documentation is your friend. ;) https://docs.litespeedtech.com/lsws/cp/cpanel/wp-protect/ https://docs.litespeedtech.com/lsws/cp/cpanel/recaptcha/