Search results

Use a rewrite rule testing ${USER_AGENT} should do the job.

should be in "server"->"general" tab->"General Settings" table.

A bug introduced in 3.3.10 affects this, has been fixed in the 3.3.11 package, you can get it by changing the version number in the download link.

lsphp-5.2.5 should be the updated and lsphp5 should be a symbolic link to lsphp-5.2.5

in /usr/loca/lsws/fcgi-bin, /usr/bin/php is the CLI version of PHP.

Try this http://www.litespeedtech.com/docs/webserver/config/general/#useIpInProxyHeader This is not a enterprise only feature, the document is wrong.

You need to remove the "--prefix=/usr" configuration parameter, instead set it via "Install Path Prefix" configuration. if you want to use "/usr" just set it to "/usr".

If your DB file is larger than 2GB, it will pretty much invalidate the whole 2GB cache memory, 2GB cache memory can guarantee that server do not have a disk I/O problem. You need to find out what causes the high I/O wait. And if you think Apache does not have this problem, give it a try and see...

Are your server experiencing similar high load during the backup time, there are two spikes in your graph at night time. You need to check your server when the I/O wait is high, pay attention to "SWAP" memory being used, if for some reason the server start to use swap, you need to find out...

Maybe there was some I/O intensive tasks like backup DB or some other files. Please check your graph history see if it happen every day around the same time. LSWS itself alone will not cause high I/O wait. More lsphp4 processes is the result of high I/O wait, not the cause. You need to find...

OK, find a problem with handling "SecFilter" directive, the request URI has not been checked. Uploaded 3.3.11 release package, and it works properly now. If you find any other issue mod_security rules, please let us know.

checking it now.

You need to do the same thing to /usr/bin/ld as to /usr/bin/gcc

increase connection timeout to 120. If your server do not have enough bandwidth, you may have network problem. LiteSpeed delivers content much faster than Apache, which may make it looks worse. Better ask you DC about your bandwidth limit, and your usage. on 10Mb/s, 100Mb/s or 1Gb/s port, and...

Please send me an example URL along with the mod_security rule that should block it. However, it has not been blocked in your server environment, and we can reliably reproduce it on your server, then I will start investigate. Without those information, I don't know where to start.

You can find it out with command ps -ef | grep lsphp

No. it may cause too many lsphp processes being started if PHP has not been configured properly.

What is your OS?

We need more specific information to investigate this. The Request URL and security rule that should work but not. We can try it on your server with mod_security log enabled.

It is a network problem. shows that the request body has not been completely received yet. Are you using bandwidth throttling? You can try increasing the "Connection timeout" under "Server"->tuning tab.