suPHP Problems

spork

Verified User
Joined
Mar 30, 2007
Messages
7
I am in the process of deploying two new servers, both running CentOS 5.2 x86_64 and DirectAdmin.

I used CustomBuild 1.1 to build Apache 2.2 and PHP 5.2.8 as a CGI w/ suPHP 0.6.3 but it does not seem to be working correctly on either box. I am unable to view a webpage unless I give apache ownership or grant read/execute permissions to the world, otherwise I get a 403 Permissions error (as opposed to the 5xx errors I am used to with suPHP).

I have tried recompiling as 'owner' instead of 'paranoid' (following this guide and rebuilding php outright. /var/log/suphp is completely empty, even after several attempted pageviews. I have verified that the suPHP module is being included in the httpd.conf and that the configuration directives are included in the user httpd.conf files.

Any suggestions?
 
jdlitson, no, you are not right :) suPHP has Apache 2.2 compatibility from its 0.6.2 version.
 
I am in the process of deploying two new servers, both running CentOS 5.2 x86_64 and DirectAdmin.

I used CustomBuild 1.1 to build Apache 2.2 and PHP 5.2.8 as a CGI w/ suPHP 0.6.3 but it does not seem to be working correctly on either box. I am unable to view a webpage unless I give apache ownership or grant read/execute permissions to the world, otherwise I get a 403 Permissions error (as opposed to the 5xx errors I am used to with suPHP).

I have tried recompiling as 'owner' instead of 'paranoid' (following this guide and rebuilding php outright. /var/log/suphp is completely empty, even after several attempted pageviews. I have verified that the suPHP module is being included in the httpd.conf and that the configuration directives are included in the user httpd.conf files.

Any suggestions?

Check if public_html is owned by user, and all files in it too. P.S. if you want to use the owner mode (http://help.directadmin.com/item.php?id=176), make sure you apply the following steps (in this way configuration directives won't be included into apache configuration files):
Code:
cd /usr/local/directadmin/data/templates/custom
cp -f ../virtual_host* .
perl -pi -e 's/suPHP_UserGroup/#suPHP_UserGroup/' virtual_host*.conf
perl -pi -e 's/suPHP_UserGroup/#suPHP_UserGroup/' /etc/httpd/conf/httpd.conf
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
 
Check if public_html is owned by user, and all files in it too. P.S. if you want to use the owner mode (http://help.directadmin.com/item.php?id=176), make sure you apply the following steps (in this way configuration directives won't be included into apache configuration files):
Code:
cd /usr/local/directadmin/data/templates/custom
cp -f ../virtual_host* .
perl -pi -e 's/suPHP_UserGroup/#suPHP_UserGroup/' virtual_host*.conf
perl -pi -e 's/suPHP_UserGroup/#suPHP_UserGroup/' /etc/httpd/conf/httpd.conf
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue

Yep, public_html is owned by the correct user and I did follow the guide to the letter - The #suPHP_UserGroup directives are indeed commented out yet suPHP still refuses to do much of anything on either of the boxes I am working on.

From past experience I would at least be expecting HTTP/500 errors and tons of log messages in /var/log/suphp. As mentioned previously I am getting neither. :(
 
Never mind - stupid error on my part. Apache has to be able to look at stuff in order to work. suPHP just works for the actual scripts themselves, not the entire Apache process.

Thanks for the help. :)
 
Back
Top