As an answer to my own initial question (see
http://www.howtoforge.com/forums/showthread.php?t=12705), I decided to try to create a custom
suPHP package to ease the installation of
suPHP for use with ISPConfig. This is what I did:
- Compiled suPHP as described by Hans in his article How To Set Up suPHP On A Debian Etch Based ISPConfig Server.
- Downloaded and unpacked the stable Debian libapache2-mod-suphp package.
- Replaced the original mod_suphp.so in the package with the customized version.
- Adjusted several directives in the package control file:
- Changed package name
- Added dependency apache2-prefork-dev
- Added conflict libapache2-mod-suphp
- Adjusted Installed-Size
- Added an additional README.
- Updated the md5 values.
- Created the package.
I now have a
package that installs with dpkg -i. Doing so with libapache2-mod-suphp already installed or without apache2-prefork-dev (or any of the other dependencies like suphp-common) available, aborts the installation with an appropriate message. In the latter case, apt-get -f install is enough to have the missing packages installed.
After installation, I made the appropriate modifications to /home/admispconfig/ispconfig/lib/config.inc.php and 'touched' a website to have my /etc/apache2/vhosts/Vhosts_ispconfig.conf updated (see
How To Set Up suPHP On A Debian Etch Based ISPConfig Server).
On the surface everything seems o.k. The only problem is that my php websites don't work. They all show the familiar "500 error - Internal Server Error!". Adding the neccessary Apache Directives for a site, makes it appear again.
Can anyone assist me in troubleshooting this problem? I have far too little experience to do that all by myself. Ofcourse the
package will be made available to the ISPConfig community as soon all the problems have been solved.
Recent comments
19 hours 3 min ago
1 day 8 min ago
1 day 4 hours ago
1 day 6 hours ago
1 day 20 hours ago
1 day 20 hours ago
2 days 1 hour ago
2 days 8 hours ago
2 days 9 hours ago
2 days 10 hours ago