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

If you reinstall DA (./directadmin i) on a live box, your /etc/httpd/conf/httpd.conf file will get overwritten and emptied of all data. You’ll need to read all of the Include lines for your users so that their sites show up (you’ll be seeing the apache pages, or the shared IP pages instead)
Type:

cd /usr/local/directadmin/data/users
for i in `ls`; do { echo "Include /usr/local/directadmin/data/users/$i/httpd.conf" >> /etc/httpd/conf/httpd.conf; }; done;

Note that this add the include lines for *all* users.. so if you’ve added users to DA after you ran the "./directadmin i", you’ll end up with duplicates. Make sure you don’t have duplicate Include lines.. (apache won’t restart, it will let you know)

One common problem people have is an incorrectly setup mail system. Here is a list of rules that must be followed:
1) hostname must not match any domain that is being used on the system. Example, if you have a domain called domain.com and you want to recieve mail on user@domain.com, you must *not* set your hostname to domain.com. We recommend using server.domain.com instead. You must make sure that you add the A record for server.domain.com so that it resolves.
2) The hostname must be in the /etc/virtual/domains file.
3) The hostname must *not* be in the /etc/virtual/domainowners file.
4) The hostname must resolve. If not, add the required A records to the dns zone such that it does.
5) The directory /etc/virtual/hostname must exist.. (eg: /etc/virtual/server.domain.com). It must not contain any files.
6) Any domains that you want to use for email (eg: domain.com) must be in both the /etc/virtual/domains file and the /etc/virtual/domainowners file. The directory /etc/virtual/domain.com must exist and the files /etc/virtual/domain.com/passwd and /etc/virtual/domain.com/aliases exist.
7) File permissions for virtual pop inboxes should be (not applicable with Dovecot/Maildir):

/var/spool/virtual/domain.com 770 username:mail
/var/spool/virtual/domain.com/* 660 username:mail

If you’ve made any changes to you /etc/exim.conf file and require a fresh copy, you can retrieve one with this guide:
http://help.directadmin.com/item.php?id=51
Ensure your hostname does not contain any upper case letters.
9) Make sure that your main server IP has a reverse lookup on it.

Overview

The Bandwidth Usage feature allows you to see the bandwidth usage for your site. It shows the current month’s bandwidth usage as well as your total bandwidth usage. This will include all HTTP (web) and POP (mail) bandwidth usage and may include FTP bandwidth usage if your system administrator has enabled FTP bandwidth logging.

Monthly Bandwidth Limit

Today

The next section shows the amount of bandwidth or traffic used on your web site for the current day. The “Traffic for Today” graph shows the amount of bandwidth or traffic on the following protocols:

• Http – Web site page bandwidth usage.
• Pop – Mail bandwidth usage.
• Imap – Mail bandwidth usage.
• Ftp – File Transfer Protocol or amount of file upload and download bandwidth usage.
• Smtp – Outgoing mail bandwidth usage.
• All – Total bandwidth usage for Http, Pop, Imap, Ftp, and Smtp.

This Year

The next section shows the amount of bandwidth or traffic used on your web site for the current year. The “Traffic for CURRENT_YEAR” graph shows the amount of bandwidth or traffic on the following protocols:

• Http – Web site page bandwidth usage.
• Pop – Mail bandwidth usage.
• Imap – Mail bandwidth usage.
• Ftp – File Transfer Protocol or amount of file upload and download bandwidth usage.
• Smtp – Outgoing mail bandwidth usage.
• All – Total bandwidth usage for Http, Pop, Imap, Ftp, and Smtp.

The last three sections shows the amount of bandwidth used for the last three months including the current month. The two months prior to the current month displays a “circle” graphic that says “Click to Show.” Click on the circle graphic to display the amount of bandwidth used as displayed on a pie chart.

1) If you wish to change just 1 subdomain path, you’d use this guide as a starting point:
http://help.directadmin.com/item.php?id=3
and insert the following code

|*if SUB="subname"|
|?DOCROOT=/the/new/path/you/want|
|*endif|

This will do a check on the subdomain name.
Change subname to the name of the subdomain you want to set the path for.
Also change the path to the path you’d like.
Failing to use the if statement on the subdomain will cause the main domain and all subdomains to use this new path, which isn’t always as desired.
2) Going into more detail, the DocumentRoot for a subdomain will always have the "sub" name appended to the end. If this is not the desired effect, then the templates would have to be modified to get rid of the bit on the end, while still allowing subdomain paths for normal subdomains to be valid. To do that, first copy the templates to the custom folder

cd /usr/local/directadmin/data/templates/custom
cp ../virtual_host2*_sub.conf

Then edit both of the virtual_host2_sub.conf and virtual_host2_secure_sub.conf files. Find the following line:

|?DOCROOT=`HOME`/domains/`DOMAIN`/public_html|

and change it to be:

|?DOCROOT=`HOME`/domains/`DOMAIN`/public_html/`SUB`|

Same thing for this line:

|?CGI=ScriptAlias /cgi-bin/ `DOCROOT`/`SUB`/cgi-bin/|

change it to be:

|?CGI=ScriptAlias /cgi-bin/ `DOCROOT`/cgi-bin/|

and one last time for a 3rd line, change:

<Directory |DOCROOT|/|SUB|>

to be:

<Directory |DOCROOT|>

Save the 2 virtual_host2*_sub.conf with these 3 changes, then proceed with step 1 normally, and the path will be what you’re looking for. All existing subdomains will also remain unaffected, since we just moved the SUB part from the bottom, and moved it to the top.

---

3)Similarly, if you only which to change the path of the domain and not any subdomains, you can use

|*if !SUB|
|?DOCROOT=/the/new/path/you/want|
|*endif|

so that only if there is no subdomain name, then the path will be altered.