Search results

1) suggest just change back "Connection Timeout" to default and watch/monitor "Server error: No response" issue 2) if the issue disappear or improved a lot, revert back other 2 parameters as well and watch again 3) if this issue not occur again or at least no worse/no better, keep all the 3...

it looks other 2 is less significant than "Connection Timeout" I suggest just change this one and watch.

you can install a fresh lsws on another test box and check with /usr/local/lsws/conf/httpd_config.xml (may need get a trial license) or download a latest package, extract the .tar.gz, check conf/httpd_config.xml.in

yes, please revert to 300 and monitor again. please get a list of all such changes which is different to default value --- most default value is not recommended to change unless it's very clear which need to change it.

have you read or followed this wiki page ? https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cpanel:easyapache4-config#configuration_steps

now let's back to the original issue. https://support.google.com/webmasters/answer/35120?hl=en "Use Fetch as Google to check if Googlebot can currently crawl your site. If Fetch as Google returns the content of your homepage without problems, you can assume that Googlebot is generally able to...

then can you create a new post under Magento (https://www.litespeedtech.com/support/forum/forums/magento.40/) ? you can get professional answer and help there. since our Magento experts may not look or follow this thread under installation. can you shed some light here how you've resolved the...

so 785 ms vs 616 ms (litespeed vs apache) for homepage(?). there is not much difference for a single php page, since the bottle neck is php engine, not web server. litespeed is better than apache when there are many concurrent access, litespeed consume less CPU, memory, and average(or most)...

for this particular error, need rebuild lsphp, by adding --enable-libxml or just delete '--disable-all' will do.

just now I checked, if /usr/local/lsws/autoupdate/release=5.1.9-ent /usr/local/lsws/autoupdate/platform=x86_64-linux yes, latest build(or last build) is 4. by reading /usr/local/lsws/admin/lsup.sh, #curl http://www.litespeedtech.com/packages/5.0/lsws-5.1.9-ent-x86_64-linux.tar.gz.lastbuild can...

no, reinstall has same result, either via command line or WHM. what's the build version ? the info is in /usr/local/lsws/autoupdate/build

command line should be fine. this is weird, since you already logged in as root. it looks to be a linux permission issue, not because of any special of lsup.sh. maybe relate to selinux enabled ? I have never experienced such behavior -- run script as root user, but asking for root permission.

please force update 5.1.9 to latest build, there are a few new minor updates. #/usr/local/lsws/admin/misc/lsup.sh -f -v 5.1.9 see if the issue persist. even roll back, 5.0.19 is recommended.

unresponsive may due to https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:nf-conntrack-table-full check if your server has this problem.

you can set it much lower, like 1 during attack, to see if any good effects. to measure its effects: 1)CPU load lower 2)normal user may feel the website slower, but acceptable, not too slow. 3)watch WaitQ, see if it keeps increasing or not

Hi, is regarded as 1 domain in litespeed, maybe from the beginning. so can't define 2 virtual hosts for same domain. what's your use case you've to define 2 virtual hosts ? the workaround is to combine 2 virtual hosts into 1.

I did local tests, can partially reproduce the issue. however following code works: $file= $_GET["path"]; header("Content-Type: application/octet-stream"); header("Content-Disposition: attachment; filename=\"../media/$file\""); i.e., just don't use X-LiteSpeed-Location header. by my quick...

LS works with EA 4 well. please follow https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cpanel:easyapache4-config to see if you've missed anything.

/home3 is full: /dev/sdc1 459G 435G 237M 100% /home3 only 237M available /var/share/optimumcache/DiskDescriptor.xml is full, 15G 15G 0 100% /var/cache/optimumcache 0 byte available. maybe you can disable cloudlinux's optimumcache to see if any difference.

looks like shortage of some critical resources. please check with #df -h #df -hi #top -c when litespeed can't restart