This user manual is designed to familiarize new users with the WebHost Manager Interface; and also to provide extra knowledge for current users. This manual will focus on the tasks involved with installing, configuring, and administrating your server’s web hosting needs using WebHost Manager.

There are many terms and abbreviations in this manual that may be unfamiliar to you if you’re new to server administration and web hosting. We recommend purchasing a guide to System Administration to get familiar with how your server works and web hosting in general. You can also find information about the terms and abbreviations used in this manual by searching for them on a search engines such as Google.

To move from one section to another, use the list on the right side of your screen. Click on a section to reveal the tasks associated with that part of WebHost Manager. Click on a subsection in the table of contents for more information on that subsection and the tasks associated with that subsection.

This manual is arranged to mirror the WebHost Manager interface and therefore is not arranged by specific tasks. To search for specific tasks that you would like information about, use the search at the top left-hand part of your screen. For example, if you wish to find out how to add a “nameserver”, type “nameserver” into the search field and then click on SEARCH.

NOTE: Some Troubleshooting sections are for advanced users only. These sections may require that a SSH session is open on the server and that commands are run from the command line. We recommend only using these sections if you are comfortable with administrating your server as they may result in downtime. If you are uncertain of the cause of a problem, or are not comfortable using the commands outlined in these troubleshooting sections, please contact your web host or cPanel for support.

To disable the SSL2.0 protocol (thus forcing 3.0),
for apache 1.3, find the line:

#SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL

and change it to:

SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:!SSLv2:+EXP:+eNULL

Note the 2 changes: a) remove the # character at the beginning of the line, and b) change +SSLv2 to !SSLv2

For apache 2.x, do the same thing, but instead it will be in the /etc/httpd/conf/ssl.conf file, or for the new apache system, /etc/httpd/conf/extra/httpd-ssl.conf (if you have both files, just change it in both).

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:

Overview

The System Reboot Menu allows you to check on the status of your server and display a lot of valuable information about your server.

To access the System Reboot Menu, click on System Reboot, on the main screen of your WebHost Manager interface.

Forceful Server Reboot

A Forceful Server Reboot forces the system to restart and may not always shutdown all running processes. This process should not be used unless a Graceful Server Reboot does not work.

Steps

1. To access the System Reboot Menu, click on System Reboot, on the main screen of your WebHost Manager interface.
2. Click on Forceful Server Reboot.
3. Click on Ok.

Graceful Server Reboot

A Graceful Server Reboot attempts to shutdown all processes on your server and then reboot the system. This is a similar process to the reboot command.

Steps

1. To access the System Reboot Menu, click on System Reboot, on the main screen of your WebHost Manager interface.
2. Click on Graceful Server Reboot.
3. Click on Ok.

In order to force apache to allow cgi script to run, simply create a file called .htaccess inside the directory in which you wish to run the scripts. Insert this text into the file:

Options +ExecCGI
AddHandler cgi-script .cgi .pl