Apache and DA messed up, could someone help me?

[Canglan]

Hi folks,

I am running Fedora Core 1 and Direct Admin on a VPS server. I accidentally upgraded Apache to 2.0.50, after that I reinstalled Apache 1.3.33. However, it seems DA doesn't recognize the newly installed Apache.

What happening on my server is that, all IP addresses or domains binded on these IPs directed to the default Apache page ('Hey, it worked !'... etc).

Is there anyway to fix it? Your help will be greatly appreciated! Thanks in advance! :)

[toml]

When you reinstalled Apache 1.3 your /etc/httpd/conf/httpd.conf file was replaced with a 1.3 version, and all your domain modifications were lost. You need to add an "Include path_to_user_httpd.conf" line at the bottom of that file for each domainuser. You can see the list of files you need to include by doing a:
ls /usr/local/directadmin/data/users/*/httpd.conf

[louie55]

If you run the DA customapache script for Apache 2.0, it might rebuild your configuration????

Do this:


cd /usr/local/directadmin/customapache
./build update
./build clean
./build update_data_ap2
./build convert
./build apache_2
./build php_ap2
./build mod_frontpage_ap2
./build mod_perl_ap2


Louie

[jmstacey]

Here are instructions on downgrading if you want to go back to Apache 1.x

http://help.directadmin.com/item.php?id=54


There are several things you must do to get Apache2 working with DirectAdmin. For example, updatethe directadmin.conf file, rewrite the httpd.conf files and ips.conf files and so on.