Search results

Enterprise edition wont have this problem . free starter can be used for small server.

That's a bug with the standard edition. will be fixed in next build.

it wont work with .htaccess, but can be set at server or vhost level where the CA certs are configured.

correct.

You may look into cPanel cluster for configuration sync. LSWS does not provide a way to sync configuration. for LB, should use our WebADC if you use our cache solutions. you can use zeroconf API with cPanel nodes. https://www.litespeedtech.com/products/litespeed-web-adc/features/webadc-zero-conf

cat /usr/local/lsws/BUILD if it is not 3, do lsup.sh -f -v 5.4.3

Using cloudflare as front-end proxy make it much more difficult to really stop the botnet, as everything is going through CloudFlare, server cannot stop accepting requests from it, including those from botnet. My suggestion is to bypass cloudflare in such case, see if it can defeat the attack.

Please make sure to update to the latest build of 5.4.3, currently build 3. If problem persists, please turn on full debug logging while it is happening. https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:bug-reporting#submit_a_bug_report

Please check if lsphp is running as the site owner. it is likely a permission problem. You can also turn on full debug logging to get better idea what happened. https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:bug-reporting#submit_a_bug_report

the total number of DB connections is limited by mysql thread pool size, you need make sure it is high enough. if PHP uses persistent connections, and there are a lot more PHP worker processes started, it may hit the limit. check if Apache PHP is using persistent db connections or not, config...

What is the problem? Maybe try updating to the latest 5.4.3 release.

You can try a full stop/start . service lsws stop service lsws start the SO_REUSEPORT socket feature may require a fresh start. If with 2-CPU license, each lshttpd worker process was using more than 30% CPU, you could see performance improvement when upgrade to 4-CPU license. otherwise, you...

Yes, it is a bug fixed. please update to 5.4.2 build 5 /usr/local/lsws/admin/misc/lsup.sh -f -v 5.4.2

You can configure LiteSpeed to use SSL certificate from any vendor. as long as you have the key/cert combination. You just need to manually update it when the cert is expiring.

Glad you got it working.:)

In the first rewrite rule, you made a mistake %{HTTP:HTTP_CF_IPCOUNTRY} should be %{HTTP_CF_IPCOUNTRY} You can turn on rewrite log, or full debug logging to check if the rewrite rule get the correct value.

What you see is HTTP/1.1 "chunked" encoding. a HTTP/1.1 client should be able handle. If you script do not handle it, just send a HTTP/1.0 request instead.

Yeah, you can change httpd_config.xml directly if have to stay with the older version.

coming this afternoon.

the latest stable version is 5.4.1, should upgrade to 5.4.1 .