Search results

Our package are universal, it should work pretty well in CentOS 7.

tested it, the header was added but truncated due to a bug, you can work around it with it will be fixed in next release.

Need to rebuild PHP with configuration "--with-mysql=...", make sure the correct mysql client library devel package has been installed.

Create a phpinfo() page under the site having problem, switch between Apache and LiteSpeed compare phpinfo() output. I think LiteSpeed PHP is missing mysql modules, so cannot connect to MySQL. usually can be fixed by updating php.ini used by lsphp, assuming the mysql modules has been built in...

It should work by adding to "Extra Headers", please let us know the version of LSWS, type of resources pointed by the URL. static? dynamic? php?

$VH_ROOT is the user's home directory. You can use something like $VH_ROOT/public_html or $VH_ROOT/php However, each account can only have one php.ini, so it wont work if you want per subdomain php.ini.

You should remove the double quote. You must enable PHP suEXEC under "Server->general->Apache configuration" Check phpinfo() page see if the PHPRC environment has been set to the correct value or not.

looks like you need to strace to find out what happened in the php process. at the beginning of the PHP script add something like "sleep(30)", to give you some time to locate the PHP process. ps -ef | grep lsphp5 locate the PHP process running the script from the command. strace -tt -T -p...

The modules added through /etc/php.d may not be built properly for the lsphp5 binary, so it will crash lsphp5 process. The problem is the combination of lsphp5 binary + old module binary + bad php.ini . The easiest fix is to compile required modules into the lsphp5 binary statically, so it...

Please check error.log and stderr.log under /usr/local/lsws/logs/, I think it is likely due to problem with PHP binary. You may need to rebuild PHP binary and/or change php.ini. you can try remove "/etc/php.d" from the "Scan this dir for addditional .ini files", see if it helps.

which version of LSWS are you using? Upgrade to the latest 4.2.12, if the problem persists, may need to turn on full debug logging to figure something out.

Please check error_log, if need, you need to turn on full debug logging to find out what happened.

http://www.wordfence.com/blog/2014/05/wordfence-5-0-6-beta-1-released/

Is it possible to let us login to trouble shoot the problem. Need temp root login and WordPress admin to perform the scan.

You need to raise per client throttling connection hard/soft limit http://www.litespeedtech.com/docs/webserver/config/security#perClientConnLimit

/usr/local/lsws/autoupdate/release may have wrong data in it. please do restart LSWS. upgrade again.

You should force reinstall 4.2.12, this issue should have been addressed a while ago when we update the package.

If you uses litespeed native configuration, you may have to copy/paste the rules to the rule list under "Request Filter" tab. Later we may add the feature to allow user to include modsec rule config files.

You should write to openlitespeed developer email list https://groups.google.com/forum/#!forum/openlitespeed-development

In addition to the reply on github, you should force reinstall 4.2.12 see if the problem still exists on the latest build. /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.12