Search results

does abc.php file exists? and the file need to be processed as a script. LiteSpeed ignore mod_sec for static files.

Will a restart fix it? Please send us the section of error log starting to show this issue to bug@litespeed...

upcoming 4.1.12 release will support AddType 'text/css; charset=UTF-8' .css and AddDefaultCharset UTF-8 will work for context type starting with "text/", so, it can cover .css, but not .js.

Our lab has the same version WHM, and PHP suEXEC works properly with 4.1.11. We need to find what is the difference in somewhere causing this issue.

Are you using cPanel? which version? Please send the httpd.conf or a vhost configuration sample to bug@litespeed...

It is unexpected, and the latest build of 4.1.11 may have addressed this. just try a force reinstall of 4.1.11

Please try a force reinstall of 4.1.11, see if the problem is still there. Also, check if lsphp5 processes are running as each account owner, or all as nobody.

http://www.litespeedtech.com/support/forum/showthread.php?t=5545 please contact Eleven2 about this.

sorry, I probably mistake you with another client. I will PM you the link.

you should convert to CageFS. We made some change in lscgid for latest CageFS, it may affect people still using secureLVE.

Are you using "SecureLVE" or "CageFS"? If you configured LiteSpeed to use SecureLVE, but you did not actually setup account using CageFS, you may get problem with 4.1.11. You just change LiteSpeed configuration to use regular "LVE". Revert back to previous release should fix it.

If AIO is not involved, it could be something else. Please contact bug@litespeed... if you would like to have our staff to take a look at your server.

That configuration is ignored by LiteSpeed for the sake of performance. you can block access to those files with a rewrite rule or security rule. if it is a security threaten, just disable PHP error logging to that file, everything should be Apache log file and user can access those errors...

Or, you forgot to renew your monthly license?

Then, you need to check if "litespeed" process is actually running with "ps". and check error log for any hint why it stops. Another possibility is some anti-hacking script killed litespeed processes as they do not know litespeed replaces Apache. Recall any change you have made to the server...

It is likely that you uncheked "httpd" service under "Service control" section of WHM. Please pay attention to the warning at the end of the guide. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:apache:ezcpanel

There is a known kernel bottle neck trigger by LiteSpeed when CPU/core count is very high. We are working on a solution now. In the mean time, you should turn off "AIO" under server->"tuning" tab from LSWS console see if it help or not.

I think changing silverstripe cms code is the correct way to fix this problem. Please post your fix to the PHP code or contribute the change back to silverstripe project if you do not mind, it will benefit to others.

It is a PHP internal bug regarding open_basedir, has nothing to do with LiteSpeed, remember that Apache suphp does not enforce open_basedir at all. You should report this bug to bug.php.net Also, should upgrade to the latest PHP 5.3.x release or downgrade to PHP 5.2.17 see if it helps or not...

Please check the ticket reply about 4.1.12.