If it works on the hostname you could forward all requests to http://server-hostname/whatever
I havent gotten around to doing it yet.
Got mine working again. Only solution was to downgrade the entire system.
That fixed it!!!!
Downgraded to Custombuild 1.2 running Apache 2.2.x and 5.3 sup.
That it!
I was getting suexec errors other weird errors under Apache 2.4.x since the suexec patch really only works for Apache 2.2 by the looks of things.
Running Cloudlinux, its much happier under 2.2. 2.4 is a bloody disaster.
BTW i download a fresh install of custombuild 1.2 and that has issues too like;
./build: line 8452: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8453: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8454: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8455: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8456: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8457: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8458: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8459: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8460: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8461: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8462: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8463: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8478: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8480: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8481: /usr/local/suphp/etc/suphp.conf: No such file or directory
./build: line 8482: /usr/local/suphp/etc/suphp.conf: No such file or directory
Writing data to /etc/httpd/conf/extra/httpd-suphp.conf
and it failed to compile mailman, what a joke!!!!!!!!!!!!!!!!!!
***** Distutils is not available or is incomplete for /usr/bin/python
***** If you installed Python from RPM (or other package manager)
***** be sure to install the -devel package, or install Python
***** from source. See sec. 15.1 of the Installation Manual for
***** details
*** There was an error while trying to configure mailman.
and other issues i had to compile separately
Who knows what it was supposed to compile after Mailman as it completely exited the build.
But least my frigging /phpmyadmin /roundcube /squirrelmail /pma and others work now.
Shame on DA for letting this fester. Unreal in fact!
That's no solution, that's just a workaround. I only want php 5.4, and no custombuild 1.2.
By the way, you could have this working with Custombuild 2.0 just by compiling su-php instead of fastcgi, fyi.
I want this working in php in fastcgi mode.
cd /usr/local/directadmin/custombuild
./build update
./build apache
suexec -V
-D AP_SAFE_DIRECTORY="/usr/local/safe-bin"
perl -pi -e 's#/var/www/fcgid/#/usr/local/safe-bin/#' /etc/httpd/conf/extra/httpd-hostname.conf
service httpd restart
This is my solution. Its my solution because Cloudlinux doesnt seem to support Apache 2.4 and i could not complile Apache 2.2 under CB2.0 otherwise i would have stayed with CB 2.0.
So i was forced to go back because i was getting suexec errors from CL under Apache 2.4.
All of you seem to be running an old unpatched version of apache. Please run:
Code:cd /usr/local/directadmin/custombuild ./build update ./build apache
Then run:
Code:suexec -V
If you see:
Code:-D AP_SAFE_DIRECTORY="/usr/local/safe-bin"
Then everything is fine with it. Another cause of it could be wrong path to sh scripts specified (they were changed some time ago), a fix for that would be:
Code:perl -pi -e 's#/var/www/fcgid/#/usr/local/safe-bin/#' /etc/httpd/conf/extra/httpd-hostname.conf service httpd restart
When posting issues, it would be nice if you may include the options.conf file too. Thank you for the reports.
No input file specified.
root@raynor:/var/www/html/roundcube# cat /usr/local/directadmin/custombuild/options.conf
#PHP settings.
#Default version of PHP is always php1_release. Possible values for php1/php2_release: 5.3, 5.4, 5.5, no. php1/php2_mode: mod_php, fastcgi, php-fpm or suphp)
php1_release=5.4
php2_release=no
php1_mode=fastcgi
php2_mode=php-fpm
php_ini=no
php_timezone=CEST
#Possible values - production or development
php_ini_type=production
ioncube=no
zend=no
#HTTP server. Possible values: apache, nginx
webserver=apache
#Apache settings
#Possible value: 2.4
apache_ver=2.4
mod_ruid2=no
secure_htaccess=no
harden-symlinks-patch=yes
use_hostname_for_alias=no
redirect_host=raynor.s4nder.nl
redirect_host_https=no
All of you seem to be running an old unpatched version of apache. Please run:
Code:cd /usr/local/directadmin/custombuild ./build update ./build apache
Then run:
Code:suexec -V
If you see:
Code:-D AP_SAFE_DIRECTORY="/usr/local/safe-bin"
Then everything is fine with it. Another cause of it could be wrong path to sh scripts specified (they were changed some time ago), a fix for that would be:
Code:perl -pi -e 's#/var/www/fcgid/#/usr/local/safe-bin/#' /etc/httpd/conf/extra/httpd-hostname.conf service httpd restart
When posting issues, it would be nice if you may include the options.conf file too. Thank you for the reports.
I am running a patched version of Apache. Also, did replace the line in hostname.conf though. After restarting, I don't get an error 500 anymore, but this:
No errors are logged in error_log, domain's error_log or the suexec_log.
chmod 551 /var/www
suexec policy violation: see suexec log for more details
I was logged in to this server and the problem was incorrect permissions on /var/www (550), the following fixed it:
Code:chmod 551 /var/www
The error that was logged in error_log:
Code:suexec policy violation: see suexec log for more details
Another cause of it could be wrong path to sh scripts specified (they were changed some time ago), a fix for that would be:
Code:perl -pi -e 's#/var/www/fcgid/#/usr/local/safe-bin/#' /etc/httpd/conf/extra/httpd-hostname.conf service httpd restart
When posting issues, it would be nice if you may include the options.conf file too. Thank you for the reports.