rusty0101
May 10th, 2010, 07:33 AM
So you migrated your primary webserver to 10.04 LTS and suddenly your users are complaining that their userdir php pages are not working. They keep being asked to download their php pages or phtml, or whatever. Their user blogs are not working. You have unhappy users, and by this time you are probably one as well.
This may have come up in an earlier upgrade, but whether it is 9.10-10.04 or 8.04lts-10.04lts only is pretty irrelevant. You're feeling the pain.
You have two choices. Tell your users to move to a dedicated hosting environment of their own, or re-enable php scripting in the apache web server.
sudo nano /etc/apache2/mods-available/php5.conf
Look for the lines that look like:
<IfModule mod_userdir.c>
<Directory /home/*/public_html>
php_admin_value engine Off
</Directory>
</IfModule>
and change em to look like:
# <IfModule mod_userdir.c>
# <Directory /home/*/public_html>
# php_admin_value engine Off
# </Directory>
# </IfModule>
then restart apache.
sudo service apache2 restart
or
sudo /etc/init.d/apache2 restart
whichever you are more comfortable with.
And tell your users that they may need to restart their browsers. (or if they can figure out how, clear their web cache.)
I'll grant that there very likely are very good reasons not to allow users to do scripting in their home directories over the web. But you were not disallowing it before, were staying up to date on security issues, and had this solution shoved down your throat without any notice that it was going to happen. It might be a good time to review the decision and perhaps tell those script running freeloaders on your server, aka customers, to take a hike. But that should be your decision.
-Rusty
This may have come up in an earlier upgrade, but whether it is 9.10-10.04 or 8.04lts-10.04lts only is pretty irrelevant. You're feeling the pain.
You have two choices. Tell your users to move to a dedicated hosting environment of their own, or re-enable php scripting in the apache web server.
sudo nano /etc/apache2/mods-available/php5.conf
Look for the lines that look like:
<IfModule mod_userdir.c>
<Directory /home/*/public_html>
php_admin_value engine Off
</Directory>
</IfModule>
and change em to look like:
# <IfModule mod_userdir.c>
# <Directory /home/*/public_html>
# php_admin_value engine Off
# </Directory>
# </IfModule>
then restart apache.
sudo service apache2 restart
or
sudo /etc/init.d/apache2 restart
whichever you are more comfortable with.
And tell your users that they may need to restart their browsers. (or if they can figure out how, clear their web cache.)
I'll grant that there very likely are very good reasons not to allow users to do scripting in their home directories over the web. But you were not disallowing it before, were staying up to date on security issues, and had this solution shoved down your throat without any notice that it was going to happen. It might be a good time to review the decision and perhaps tell those script running freeloaders on your server, aka customers, to take a hike. But that should be your decision.
-Rusty