Getting Started

USTeam.Net, Inc.

UST's Self-Help Center -
"Working with your Virtual Hosts (for RESELLERS only!)"

Reseller Information

Virtual Host Information
Creating FTP access for Virtual hosts
Creating POP accounts for Virtual Hosts
Creating CGI-bins for Virtual Hosts
Creating Logs for Virtual Hosts
Clearing Logs for Virtual Hosts
Creating QuickStats for Virtual Hosts
Counters for Virtual Hosts

Reseller Information

UST will configure your servers for each virtual host you order Reseller Order Form
Virtual Host information
Virtual hosts are located in subdirectories off your 'htdocs' directory.
They are accessible via the back door by typing "http://yourdomainname/name" of directory. ('name' being similar to the domain of the virtual host, ie. your virtual host is 'xyz.com' they would be located in your "/www/htdocs/xyz/" directory or "http://yourdomain.com/xyz" but come up as "http://xyz.com". You can point potential customers to "http://yourdomain.com/name" that don't use standard browsers.

Creating FTP access for Virtual Hosts

Once your virtual host has been configured, you will need to modify an account IF you want your customer to have ftp access to their account.

Go to your Control Panel
Select the 'Add a new account' option.
Go through new account process like detailed above (for adding new FTP account).

The only difference is that you need to select '/www/htdocs/username' for the account type.

Select the 'Modify an account' option.

When asked for the username, enter the FTP username you just created.

Go to the 'Change current home directory' field and change the directory to point to the virtual host subdirectory (virtual hosts are usually named the same as the domain name [ie. xyz.com would be located in your '/www/htdocs/xyz/' directory]) In this case, change the home directory to reflect that virtual host's sub-directory, so that they have FTP access into that directory.
Click the "Modify the user" button to make the changes.
You have now created a way for your customers to ftp into their virtual host account ONLY. Always check the ftp accounts you create to ensure they work!
Your user would FTP to their domain name with the username/password you setup for them and would be taken directly to their virtual host sub-directory where they can start uploading their site, etc.

Creating POP accounts for Virtual Hosts

POP email accounts for your virtual host domain name accounts will have to be done by you with your control panel. Remember, since virtual hosts share your IP address and server space, they also share any usernames you set up in your control panel for POP accounts or aliases. If you use info@yourdomainname.com than none of your virtual hosts can use 'info@theirdomainname.com' on their websites. All their mail would be sent to your email address.

After setting up your POP email account you will need to configure your email software (Netscape, Eudora, MSN, etc) Find the reference to servers or hosts and change incoming and outgoing servers to your domain name (no www) Username is whatever name you assigned that POP.

Creating CGI-bins for Virtual Hosts

To create CGI-bins for your virtual hosts you will need to FTP into your virtual server.
After logging into FTP, you would go to "/www/htdocs/yourclient/" ('yourclient' being your virtual host account) and create a "cgi-bin" (so that there is a dir. now called "/www/htdocs/yourclient/cgi-bin/")
You now want to go to your "/www/conf/" directory and download the "srm.conf" file (this file is an ASCII file so be sure to change your download type from BINARY to ASCII)

At the end of the "srm.conf" file add a line reading:
ScriptAlias /yourclientcgi/ /usr/local/etc/httpd/htdocs/yourclient/cgi-bin/
Save the "srm.conf" file and upload it back to your "/www/conf" (don't forget to upload it as ASCII)
That's it!

When informing your client of their new CGI bin, make sure that they add the "/yourclientcgi/" to their HTML and script files. (ie. If your client is 'xyz.com' and you created '/www/htdocs/xyz/cgi-bin/' as their cgi-bin directory, they will use the URL "http://xyz.com/xyzcgi/" as their cgi-bin directory for their HTML and script files.

Creating Logs for Virtual Hosts

To create Error and Transfer (Access) Logs for your virtual hosts you will need to FTP into your virtual server.
After logging into FTP, you would go to your "/www/conf/" directory and download the "httpd.conf" file (ASCII mode).

At the end of the 'httpd.conf' file you will find two (2) blocks for each of your virtual hosts (one with the 'www' and one without)
(start example)

<VirtualHost example.com>
ServerName example.com
ServerAdmin whatever@email.com
DocumentRoot /usr/local/etc/httpd/htdocs/example
</VirtualHost>

<VirtualHost www.example.com>
ServerName www.example.com
ServerAdmin whatever@email.com
DocumentRoot /usr/local/etc/httpd/htdocs/example
</VirtualHost>

(end example)

To allow logging for that virtual host, add directives for "ErrorLog" and "TransferLog" like this:
(start example - highlighted is what you would add)

<VirtualHost example.com>
ServerName example.com
ServerAdmin whatever@email.com
DocumentRoot /usr/local/etc/httpd/htdocs/example
ErrorLog logs/example.com-error_log
TransferLog logs/example.com-access_log
</VirtualHost>

<VirtualHost www.example.com>
ServerName www.example.com
ServerAdmin whatever@email.com
DocumentRoot /usr/local/etc/httpd/htdocs/example
ErrorLog logs/example.com-error_log
TransferLog logs/example.com-access_log
</VirtualHost> (end example)

Save the file and upload the 'httpd.conf' back into the '/www/conf/' directory.
That's it!
Access and Error logs for 'example.com' will now go to the specified files. Using the "logs/" at the beginning will place the new logs in the same place as your original logs (/www/logs).
NOTE: Remember to clear (delete) logs regularly, as the can accumulate over a period of time and will go against your alloted web space (there is a fee of $1/meg if you go over your alloted space!)

We have recently added the following QuickStats Program.

The QuickStats program is designed to perform a quick a easy analysis of an http server transfer log. This is the same program that is used in the UST cpanel under the heading "Graphical Statistics Analyzer." This copy of the program is written so our server2 clients can offer on-demand log analysis to their virtual host customers without giving them access to the cpanel.

Reset logs for Virtual Host

Once you have created the cgi-bin and wwwstat for your virtual host, some of your client may prefer to take care of their log files.

You will need to save the three files below to your system.
Note: On some browsers you may need to hold your left shift key when clicking.
vhreset.html
vhresetlogs.pl
CGI.pl

You will need to edit the vhreset.html, vhrestelogs.pl and CGI.pl.

Open vhreset.html in a dostext editor (notepad works fine).

Find the line:

Change virtualcgi to the cgi-bin ScriptAlias you gave your virtual host in the srm.conf file.

Save file.

Open the vhresetlogs.pl in a dostext editor (notepad works fine).

Find these lines:

open(LOG,">/usr/local/etc/httpd/logs/virtualhost.com-error_log");

open(LOG,">/usr/local/etc/httpd/logs/virtualhost.com-access_log");

Change virtualhost.com to the domain name.

The name of the log files must match the names you gave them in your httpd.conf file.

Save file.

Open the CGI.pl in a dostext editor (notepad works fine).

Find these lines:

$mydomain = "vhhostname";

$myaccount = "vhname";

Change vhhostname to the domain name.

Change vhname to the username you have given your virtual host

Save file.

Upload the vhreset.html to the same directory as your virtual host wwwstat.html.

Upload vhresetlogs.pl and CGI.pl to your virtual host cgi-bin.

Set permissions for vhresetlogs.pl and CGI.pl to executable. (755)

Now your virtual host should be able to go to vhreset.html and reset their server logs.

View logs for Virtual Host

If your virtual host want to view thier own log files you will need to save the following files to your system.
Note: On some browsers you may need to hold your left shift key when clicking.
vhserverinfo.html
vhshowlogs.pl

Open the vhserverinfo.html in a dostext editor (notepad works fine).

Find these lines:

<A HREF="/virtualcgi/vhshowlogs.pl?log=Access">Examine Access Log</A>

<A HREF="/virtualcgi/vhshowlogs.pl?log=Error">Examine Error Log</A>

Change virtualcgi to the ScriptAlias you created for your Virtual Host cgi-bin in your srm.conf file.

Save file.

Upload vhserverinfo.html to your virtual host site.

Open the vhshowlogs.pl in a dostext editor (notepad works fine).

Find these lines:

if ($FORM{'log'} eq "Access") { $logf = "$logdir/vhdomain.com-access_log"; }

elsif ($FORM{'log'} eq "Error") { $logf = "$logdir/vhdomain.com-error_log"; }

Change vhdomain.com to the virtual's domain name.

Change vhdomain.com to the the virtual's domain name.

The log names should match the names of the log files you created for your virtual host.

Save file.

Upload vhshowlogs.pl to your virtual host cgi-bin.

Set permissions for vhshowlogs.pl to executable. (755)

Now your virtual host should be able to view their server logs.

Counters for Virtual Hosts

Each of your virtual hosts will need to be added to your 'count.cfg' file in order to have the counters implemented on your virtual hosts' sites.

FTP to your server.
Go to the '/usr/local/etc/Counter/conf/' directory.
Open the file named count.cfg (don't forget to ftp the file to your computer using ASCII format).
Find the reference to your domain name (section 5 in the count.cfg) and add each of your virtual hosts on the next line after the reference to your domain name using both the 'www.' prefix and without. (ie. www.example.com and example.com)
It will look something like this.
{
yourdomian.com
www.yourdomain.com
virtualhost1.com
www.virtualhost1.com
virtualhost2.com
www.virtualhost2.com
}
Save the file with the changes and FTP the count.cfg file back to the server (again, don't forget to ftp using ASCII format)
Your virtual host can now use counters.

USTeam.Net, Inc.

Windows, WS_FTP, Fetch, Thawte, Verisign, PGP, and any other company references are affiliated with their respective companies and remain a copyright/trademark of said respective companies. UST, Inc. claims no affiliation with any of the aforementioned companies nor claims any warranty or support for any products mentioned herein, in regards to aforementioned companies.