Search results

please try following(example only, you can adjust it) : Dynamic Requests/second: 1 Connection Soft Limit:15 Connection Hard Limit:20 to see if it can mitigate the attack effectively(of course need restart lsws after change made) in Real-Time Stats, check "Anti-DDoS Blocked IP"

it is possible the website is being (D)Dos suddenly. what's your Server->Security->Per Client Throttling ?

please try: 1. rm -rf /dev/shm/lsws 2. /usr/local/lsws/admin/misc/lsup.sh -f -v 5.2.5 to see if the issue will be gone

is /forum/index.php a normal URL ? or normal URL should be /forum/ only ? if so, you can try put following rule on top of .htaccess: RewriteEngine On RewriteRule forum/index.php - [F,L] see if it's effective to mitigate the attack.

this issue is new to me, I haven't compared command line php script with accessing from browser before so have no such experience. but looks interesting of your test result. however, since running from web browser is much faster, I'd suggest you to use "curl the-url-of-the-script.php" in your...

the function is on demand. while it's included, it will do nothing unless you manually submit the optimization request. the optimization is on a remote server.

how about a simple phpinfo.php ? any time difference ?

can you try this simplest upload php script with progress bar: see if you can upload 1.4 G file with success how many RAM on your server ? uploading a big file shouldn't consume big RAM. it'll upload to upload_tmp_dir (set in php.ini) first, if not set, usually /tmp, so need check /tmp to...

please refer https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:run-without-timeouts see if it can help you to resolve the issue.

virtual host level or context level to be short, rewrite rules still support, just move them to virtual host or context (with slight grammar difference)

http://open.litespeedtech.com/mediawiki/index.php/Help:FAQ_OLS

5.2.4 just out yesterday : https://www.litespeedtech.com/products/litespeed-web-server/release-log please upgrade 1 of your problem servers by to see if the issue still there. also please check if wswatch.sh is running before and after you upgrade to 5.2.4 regarding wswatch.sh, please refer...

a simple and effective way is to watch litespeed web admin console -> Actions -> Real-Time Stats regarding php 7.0 / 7.1 / 7.2 difference, lsapi is same, so difference is php version themselves, which you can find the details in php.net

it doesn't look like a litespeed error. since litespeed don't use mod_fcgid

yes. it's latest 5.2.3 build 7. another possibility is firewall settings. please check if UDP 443 port in/out is accepted for all IPs

please confirm the lsws version if it's latest version, looks like a bug and we need fix it.

please check the lsws version / build on the 2 servers. lsws 5.2.3 build 7 is latest.

ALL is required. cloudflare IP with an trailing "T", this is the difference. T means trusted IP, it will not be blocked by web server even if it's established many connections which has exceed the limit. the limit is defined in "Per Client Throttling" --...

just now I checked. it's running apache, and http / 2.

http://php.net/manual/en/ini.core.php post_max_size PHP_INI_PERDIR upload_max_filesize PHP_INI_PERDIR so you can add following in .htaccess <IfModule Litespeed> php_value post_max_size 10M php_value upload_max_filesize 50M </IfModule>