Search results

Do you mean that you failed to download the LSCache plugin?

You might want to set the rewrite at the virtual host level.

For such a warning, better raise a ticket to support@litespeedtech.com for further check.

Hi, No need to touch the web admin, just adding the conf file to the apache should work. For cPanel, please follow https://docs.litespeedtech.com/lsws/cp/cpanel/ocsp-stapling/#enable-ocsp For Plesk, please follow https://docs.litespeedtech.com/lsws/cp/plesk/configuration/

It might be due to the second domain's WP site URL config, .htaccess redirect, or rewrite settings in the LSWS. Please check the response header and see which service redirects you.

For anyone who is interested. It was a configuration issue and has been resolved. For different virtual hosts, please use different config files.

Hi, check https://www.litespeedtech.com/support/forum/threads/recommended-method-for-blocking-useragents-globally.13667/

For license issue, please contact your license seller, if you bought it from LiteSpeed, please raise a ticket from https://store.litespeedtech.com/store/clientarea.php

Please share the configs, or screenshot of the configs so we can check for you.

Hi, please check this, https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

May I know if you have added those bot's user-agent to the Bot White List?

@Michael Broad LSWS provides both brotli and gzip compression, by default, the brotli will be used. Since pingdom does not support brotli from day one, you can either ignore the warning, or try other tools, e.g. GTMetrix.

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/ Please post the issue on the LSCache for WordPress support forum! Thanks.

HTTP/3 is enabled by default, no need to update any web server configuration. If HTTP/3 is not working, it is usually due to the firewall settings on your server, please see https://docs.litespeedtech.com/lsws/cp/cpanel/quic-http3/#open-udp-port-443-at-the-firewall for more information.

Same question on Reddit

For LSWS header validation, that's a minor tweak to request header validation. For the "CloudFlare CDN setting vulnerability patch ", here's the reason "The "Domain" input field under CDN > Cloudflare API lacks proper input validation." And here is the code in case you might be interested.

Looks good. And if the traffic is low, you can also upgrade/downgrade the license manually in the future with no downtime.

Because there's no image was found? For WordPress cache plugin-related issues, please move to the LSCache for WordPress support forum!

It seems you have OWASP enabled, and LSWS just loads those rules, it's not an issue.

@av_admin Please try using the version after v6.0.12 build 11, which has suEXEC for PHP 8.2 support.