You can check the current version of apache by running

httpd -v

If you wish to update your 1.3 version of apache to the most recent, run the following:

cd /usr/local/directadmin/customapache
./build clean
./build update
./build apache_mod_ssl

If you’re using apache 2.x, use "./build apache_2" instead of apache_mod_ssl.
This should update both the configure options and the version of apache to the most recent version. Once the update has completed, you’ll need to restart apache:
RedHat:

/sbin/service httpd restart

FreeBSD:

/usr/local/etc/rc.d/httpd restart

What are Apache Handlers?

Apache handlers allow you to control what Apache will do with certain file types. When Apache sees a file, it has an action built in for that file type, and will perform that action. If you wish Apache to do a different action, you will need to make a handler to tell Apache to perform that action.

For example, if you use a file type that requires a special service to run it, such as a file with server side includes that is not named with a .shtml extension, you need to tell Apache to treat these files differently. More information on Apache’s Handlers can be found at http://httpd.apache.org/docs/1.3/handler.html or http://httpd.apache.org/docs/2.0/handler.html.

Creating An Apache Handler

Steps

1. Enter the handler you want to create in the first empty text box.
2. In the second empty text box, enter the extension the handler will use when being called.
3. Click on the Add button.

Overview

You can restart any of the available services on the web server at any time. You can restart the following services:

• Mail Server (Exim)
• DNS/Name Server (BIND)
• FTP Server (ProFTPd)
• SQL Server (MySQL)
• SSH Server (OpenSSH)
• HTTP/Web Server (Apache)
• POP3 Server (cppop)
• IMAP Server (uwimap)
• E-Commerce Server (interchange)
• Postgresql Server
• Servlet Server (tomcat)

Refer to the Service Manager if you need to start or stop a service.

To access the Restart Services Menu, click on Restart Services, on the main screen of your WebHost Manager interface.

Click on the required link in the Restart Services menu. This immediately attempts to restart the service and displays that service&#amp;s status.

Troubleshooting (advanced users only)

If a service will not restart, you may want to try and restart it from the command line. For this you can use:

/scripts/restartsrv service

Replace “service” with the name of the service: exim, named, proftpd, httpd, etc)

You can also restart a service through the system. This depends on the OS you are using as to where the files are located. For many distributions they are located in /etc/rc.d/init.d/

To restart this way instead, you can use:

/etc/rc.d/init.d/service

Replace “service” with the name of the service: exim, named, proftpd, httpd, etc)

You can use the following command to list all the services that can be restarted by the system:

cat /etc/rc.d/init.d/

If the service fails when restarting (or at all), you should check the error log. For example, to check apache’s error log, use:

tail /usr/local/apache/logs/error_log

The error log can be very useful for tracking down issues.

If you cannot determine the cause of the issue from the error log, you should contact your host or cPanel for support.

Incoming search terms:

If you need to go back to apache 1.3 after installing apache 2, you’ll need to do the following:
1) Restore the old httpd.conf file:

cp -f /etc/httpd/conf/httpd.conf.1.3.backup /etc/httpd/conf/httpd.conf

2) Get DirectAdmin to use the old httpd.conf files for the users. Edit the /usr/local/directadmin/conf/directadmin.conf file and change apache_ver=2.0 to apache_ver=1.3. Also, if you were using custombuild, and are going back to customapache, the apache_conf value needs to be reset to:

apacheconf=/etc/httpd/conf/httpd.conf

Then type

echo "action=rewrite&value=ips" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
echo "action=directadmin&value=restart" >> /usr/local/directadmin/data/task.queue

3) Now you can recompile apache 1.3

rm -f /usr/lib/apache/*
cd /usr/local/directadmin/customapache
./build clean
./build all

4) Fix the modules link:

cd /etc/httpd
rm -f modules
ln -s /usr/lib/apache modules

5) Restore the old boot script:
FreeBSD:

cp -f /usr/local/directadmin/customapache/httpd_freebsd /usr/local/etc/rc.d/httpd
chmod 755 /usr/local/etc/rc.d/httpd
/usr/local/etc/rc.d/httpd restart

RedHat:

cp -f /usr/local/directadmin/customapache/httpd /etc/init.d/httpd
chmod 755 /etc/init.d/httpd
/etc/init.d/httpd restart

Incoming search terms:

If you’d like to setup your domain to accept anything.domain.com, you can do so with the following guide (Admin access required)
1) Setup the dns with a wildcard A record. Go to Dns Control, and add an "A" record:
* -> 1.2.3.4
where 1.2.3.4 is the IP of your domain.
This will allow anything.domain.com to resolve to your server. Apache does not yet know how to direct that name though.
2) To setup apache, go to:
Admin Level -> Custom Httpd configurations -> domain.com
In the top text area, add this *one* line:

ServerAlias *.|DOMAIN|

then click "Save".
That should be it. Wait a few minutes for everything (apache, named) to be restarted then test it out.
The wildcard subdomains will point to your main public_html directory for the domain.
If you want to change this, it’s probably best not to do step 2, and to setup your own custom virtualhost manually into the /etc/httpd/conf/httpd.conf (DA wont delete/overwrite it there) with the same ServerAlias directive as in step 2.
Other similar uses might be subdomain aliasing, where test.domain.com is the same as test.domain2.com.
You can accomplish this by following step 1) above, then insert the following instead of step 2) above:

|*if SUB|
    ServerAlias |SUB|.domain2.com
|*endif|

which will make any existing subdomain from domain2.com point to domain.com.

Incoming search terms: