Compiling phpSuExec with Easyapache throws Internal Server Error

[Lucas]

For some odd reason I recently started getting on ALL php scripts Internal Server Error after compiling phpSuExec. I don't understand why. Before it worked just fine and now everything throws internal server error. Any ideas? PSM does my admin work but lately they let me down so I'm trying to see if I can solve this on my own.

Regards

[_Sam_]

PHPSuExec wont run with 777 chmoded folders. you will have to chmod all folders back to 755

[Lucas]

I don't have any folders on 777. That's the weird thing. Plus ALL my clients are affected.

[_Sam_]

do they have anything to controll php in .htaccess files? if so they will have to be put in a php.ini file insread of htaccess

[Lucas]

What does that have to do? It used to work just fine. But now it doesn't anymore. And all we've moved is compilation through easyapache.

[Spiral]

phpSuExec gives you the advantage of being able to track script executions better
because all scripts are run as the account owner name instead of nobody.

There are some things to note though:

1. Php_flag and php_admin commands in .htaccess will not work under PhpSuExec
and you will throw an error 500 if you have any in your .htaccess file.

2. Php overrides can be put into a custom php.ini for the account. This is actually
a downside and security vulnerability for phpSuExec and the one drawback for
having phpSuExec but the advantages usually outweigh the disadvantages.

3. Under phpSuExec, no folder can be globally writable so don't set anything to 777.
You will need to set all folders under your /public_html to 755 or you will throw
an access error from your web server.

4. There is a minor performance degradation switching to phpSuExec.


Now for those using Apache 2, you can use SuPHP instead of phpSuExec which
gives you all the benefits of phpSuExec without the downsides and doesn't have
any of the vulnerabilities or weaknesses of phpSuExec.