Search results

http://www.litespeedtech.com/docs/webserver/config/general/#useIpInProxyHeader

You can set "PATH=...." in lsphp5 "Environment" configuration.

not possible with xml. you can let LSWS read apache configuration though.

this issue should have been fixed with our latest 4.2 update. please give it try. /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2

you can put DisableCgiOverride Off in httpd.conf . It is default to "On" with 4.2 release.

It is a unix domain socket associated with the PHP suEXEC daemon created when LSWS starts. You must have some kind of cron job removing /tmp/lshttpd/lsphp5.sock. it should not be touched. Or running out of space on /tmp partition.

Please check error.log and stderr.log see if anything pop up. Also, enable "Debug Logging" to find out what happened, you can track related log entries by search your IP address.

It is not a bug. normal as 4.2 was not announced in our autoupdate system yet.

You can try suEXEC daemon + LVE, see if any performance issue. We need to narrow down the issue is caused by CageFS or suEXEC daemon.

can you make Ramaze work with cPanel + Apache? To support Ramaze, the lsws/fcgi-bin/RailsRunner.rb must be updated, or need a dedicated RackRunner.rb, Ramaze need to use rack interface.

lsapi 6 has been updated to address this issue, rebuild your PHP with lsapi 6 again.

please PM a temp root access for us to take a look.

could be cagefs if you use it. the php.ini inside the cage and out of the cage is different.

LSAPI 6.0 code has been updated to address this. you need to rebuild PHP with latest php-lsapi-6.0 code. Make sure to update /etc/group inside the cage.

You need to set both user/group for external app, only set group wont work.

set http://www.litespeedtech.com/docs/webserver/config/extapps/#extUser http://www.litespeedtech.com/docs/webserver/config/extapps/#extGroup for lsphp external app, it will be the user/group that all PHP running as.

Are you using CageFS or just regular LVE? Could be a system resource limit being hit. have you checked stderr.log? You can PM me a temp root access if you want, I can take a look.

there are some bug fixes made to 4.2, you can do a force reinstall of 4.2 from LSWS web console or, do /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2 from command line. If the problem persist, please install GDB, and send us the bug report in your email.

A easy solution is to skip sapi/litespeed/Makefile.frag and config.m4 when overwrite sapi/litespeed directory. buildconf should pass.

with PHP 5.3 and above, including PHP 5.4, you do not need to run buildconf, just overwrite sapi/litespeed directory with code from LSAPI 6.0. "--with-litespeed" is supported by default.