Those of you who are familiar with creating and maintaining a web site may find some of this information redundant, but we encourage you to explore this section to get an overview of your web site’s new home.

For those who are just beginning to learn the benefits of having and maintaining a web presence, you will find this section invaluable to your efforts to maintain your web site on our servers.

Choose the appropriate section link from below to continue.

Password Changes

Password Changes

Password Manager

You can also change all of the passwords associated with your account and its users from the Password Manager section of your PlusMailcontrol panel:

  1. Select “Password Manager” from the left navigation bar.
  2. Check the radio button next to the user whose password you want to change, enter and confirm your desired new password in the appropriate fields, then click the “Password Change” button.
  3. Allow 10 to 15 minutes for the password change to take effect.

POP/FTP/Telnet Password Changes with WebControl

You can change the password for any POP, POP/FTP, or POP/FTP/Telnet login using your PlusMail WebControl Panel’s User Manager feature. Just check the appropriate userid/login, enter the desired new password, and then click “Change Password.”

 

Click on the User Manager button from your main control panel page to get to the following input screen.
 

Primary POP/FTP/Telnet Login via Telnet

Use this method to change your primary account login (yourdomain@yourdomain.com).

  1. Telnet to your account and log in with your username and current password;
  2. At the Unix prompt, type: passwd
  3. You will be prompted to enter your current password. Type it in and then hit .
  4. After you successfully type in your password, you will be prompted to type in your new password. Type it, then hit enter again. Then it will ask you to confirm your new password.

Example:


charon:~$ passwd
Changing password for hostingmanual
Old Password: {enter your current password}
Enter the new password (minimum of 5 characters) Please use a combination of upper and lower case letters and numbers.
New Password: {type your new password}
Re-enter new password: {retype new password}
charon:~$ 


Note that your passwords will not display as you type them in.

Changing Your WebControl Login and Password

The login and password for your WebControl panel are initially set to the same values as your primary account login and password. However, they do not have to be the same, and they are completely independent of each other.

Instructions for changing your WebControl password from the control panel are available HERE.

To change your WebControl login and password from within telnet, locate the file named plusmail_pass in your account’s root directory (the first directory you’re in when you initially log in via telnet or FTP.) Delete the plusmail_pass file, then immediately point your browser to your WebControl Panel – you’ll be asked to enter a new login and password. The new login and password can be anything you want.

To delete the password file from telnet, type the following command at the Unix prompt:

rm plusmail_pass

To delete from FTP, just use your FTP client’s “delete file” function.

Wusage & Access Logs

Wusage & Access Logs

What is Wusage?

Wusage is a robust site statistics package. It shows you how many visits you’ve had, what pages have been visited most, etc. This program is already installed and running on your domain.

How do I use Wusage?

To count accesses, there is a directory called wusage in your www directory. To access it, just log on the Internet and with your web browser, go to:http://www.yourdomain.com/wusage. You will see a “Calendar of Reports” page. If monthly reports are enabled, just click on the name of the month to view those reports. If weekly reports are enabled, just click on the number corresponding to the number of the week (at the left of each week in the calendar) you wish to view.

Can I see my visitor’s domain names instead of their IP Number?

Yes. If you would like to see domain names in your stats and other programs rather than just IP numbers, put an empty (blank) text file in your www/wusage directory nameddns (no extensions). This will act as a switch and reverse authentication will be activated for the domain.

Can I just view my Raw Access Log?

The Raw Access Log which comes standard with each new domain gives you the IP# of the visitor, the date and time of the visit, the page visited, and the call method of the page (GET vs. POST).

In your home directory, you will see a file called access-log. You can download this file (in ASCII format) and open it in any word processor or text editor. In your FTP client, click on access-log, and “Get Link as File”. Please refer to your FTP client’s manual for the instructions on how to do this in your specific FTP client.

I don’t see referrers in Wusage. How do I know where my visitors came from?

Referrer logs will tell you exactly where the visitor came from (e.g. Search Engine with the keywords used to find you, other web site, etc.) If referrer logs are available for your account type, you need to install them from the Extras section of your Plusmail control panel.

Can I customize Wusage output?

Yes, you can customize Wusage by manually editing the file named wusage.conflocated in your www/wusage directory. Please note that we cannot provide support for wusage report customization. If problems occur, all we can do is reinstall the default configuration of wusage. Syntax for customization options (Wusage 7.1( is available athttp://www.boutell.com/wusage/7.1/topref.html.

Interpreting WUSAGE Reports

For a brief overview of what exactly WUSAGE is trying to tell you, read on:

The History Page

The first page that you see when browsing your WUSAGE directory contains summary statistics for your account since it was installed on our servers. It presents a graph and table describing “Overall Accesses” that summarizes your entire web site; and it presents a graph and table that describes your “Home Page,” or index page:

Totals (Overall Accesses)
Item Total Accesses Total Bytes Average Accesses Average Bytes Latest Accesses Latest Bytes
Overall Accesses 813,307 3,869,134,058 8,299 39,480,959 7,697 47,911,333
Home Page Accesses
Item Total Accesses Total Bytes Average Accesses Average Bytes Latest Accesses Latest Bytes
Home Page Accesses 47,182 323,294,556 481 3,298,924 1,350 7,252,596
Definitions

An “access” represents the download of one “element” of your web site. Elements include the HTML document itself plus all associated images. Example: If your web page includes 5 images, each time someone views that web page, it will contribute 6 accesses (1 for your web page plus 1 for each of the 5 images.) In the tables above, the Overall Access statistics count all elements on all of your web pages. Home Page Accesses count only the HTML document associated with your default home page.

“Bytes” measures the bandwidth consumed by your web site. An image on your web page that is 25 kB in size will contribute 25,000 bytes each time someone views that page.

“Average” figures are weekly averages. The “Latest” figures represent the most recent (or current) reporting period.

Weekly Reports

The weekly reports provide a much higher level of detail.

Overall Statistics

 

Category Total
Unique sites served 113
Unique documents served 9
Unique trails followed 17
Total visits 163
Unique sites served:
Every visitor to your web site has a unique IP (Internet Protocol) number associated with his or her Internet connection. The “unique sites served” figure represents the total number of those unique IP#s that have visited your site.
Unique documents served:
This represents the number of HTML documents, or web pages, that your visitors have viewed.
Unique trails followed:
A “trail” represents a unique sequence of pages viewed by your visitors. For example, if a visitor clicks on your home page (index.html), then on your information page (info.html), then on your contact page (contact.html), that visitor’s “trail” is described by index.html -> info.html -> contact.html. WUSAGE lets you know how many different trails visitors are following through your web site.
Total visits:
This is the number of times a visitor “clicked in” to your web site. It will be larger than “Unique sites served” if the same visitor (with the same unique IP#) clicked in more than once.
Accesses per Hour & Accesses per Day

This just lets you know what times of day and which days of the week are busiest for your web site.

Contents of / Sorted by Access Count

This shows you what directories and subdirectories are most popular within your web site.

Totals

 

Item Accesses Bytes
Overall Accesses 181 599,344
Home Page Accesses 158 129,203

This provides the same information for the current period as that provided in the initial History page .

Top 10 of x Documents Sorted by Access Count

Tells you what your top 10 most popular pages are. x is the total number of documents viewed.

Top 50 of x Sites by Access Count

This lets you know where your top 50 visitors are coming from — if you uploaded thedns file into your WUSAGE directory, it displays the resolved IP of your visitor; if you didn’t upload the file, it displays unique IP number.

Top 10 of x Referring URLs by Access Count

If you have extended referral logs installed on your account, WUSAGE will report the URLs of the pages your visitors are viewing immediately before coming to your site. This information lets you know what other web sites and search engines are linking to yours.

Top 10 of x Document Trails

Gives you the 10 most popular “trails” through your web site.

Visits Report

This section is self-explanatory. Example:

Total visits: 163
Average visit: 0.10 minutes
Longest visit: 11 minutes
Average accesses per visit: 1.28

10 Example Visits

Allows you to follow 10 random visitors through the trail they took through your web site.

Top x of y Documents Not Found

If a visitor attempts to browse a page on your site that does not exist, a 404 File Not Found Error is generated. This error could result because the visitor mistyped the URL, because you have a broken link somewhere in your web site, or because some browsers and search engines look for certain files automatically. This section tells you what pages are generating the 404 error.

There are at least two files that appear frequently in this report. These are files that search engines and browsers look for automatically:

robots.txt
The robots.txt file is part of the robots exclusion standard. You can use this file to control how search engine “robots” spider your web site.
favicon.ico
This is a file used by later versions of Microsoft’s Internet Explorer web browser. Internet Explorer allows you to customize the icon that appears in the visitors “Favorites” list when they bookmark your site.

The appearance of these files in your “Not Found” statistics is not cause for alarm. Your web site will function perfectly without them.

Accesses by Result Code

The Apache web server generates a “result code” each time a visitor calls a URL from your site. This section provides a summary of those result codes.

Account Disk Space Usage

Account Disk Space Usage

There are several different options available for checking your space usage. Read through the following descriptions to choose the one best suited to your needs.

Quick and Easy Quotatable

If you’re going to be checking your quotas frequently, you may want to consider installing a script that will display a summary in your browser. For example, Vladimir Koryagin’s Quotatable script provides a quick and easy reference. To install this script on your account, download the quota.cgi file, upload it to your account somewhere within your www directory structure, and set the permissions on the file to 755 (rwxr-xr-x). Then just point your browser to the URL of the quota.cgi file.

*Click the link to display the source code; or right-click and save, then rename the file to quotatable.cgi

Total Space Usage

To see the total space used by your account, telnet to your account and type:

quota -gv

The command returns the following data:
zeus:/home2/tintagel$ quota -gv
Disk quotas for group tintagelgrp (gid 760):

 

Filesystem blocks quota limit grace files quota limit grace
/dev/sda6 952 300000 310000 42 15000 15100
/dev/sdb2 103973 300000 310000 8446 15000 15100

One “block” = 1 kilobyte, or 1,000 bytes of data. The entries in the “filesystem” column indicate that two system areas – named sda6 and sdb2 – are allocated to the account.

The next four columns – blocks, quota, limit, and grace – refer to the total space used and allowed in blocks. “blocks” represents current usage; “quota” indicates allocated usage; “limit” tells you how much storage you can use before you receive an error; and “grace” is unused on our system. For this particular account, a total of 300 megabytes of storage space are allocated, with a total of approximately 105 mB (103,973 + 952 blocks) currently used.

The last four columns refer to the number of individual files used and allowed. We allocate 5,000 files per 100 mB of data, so this account has a total allocation of 15,000 files, with 8,448 in use.

www Directory Space Usage

To see space reports for the files and subdirectories contained within your www directory, type the following command at the UNIX prompt:

du -sc /home/www/yourdomain

(where yourdomain is your domain name without the extension.

This returns the total number of blocks used in your www directory. Multiply the result by 1,000 to get total megabytes used.

Home Directory Space Usage

To check how much space is being used by files in your home directory, type the following command at the UNIX prompt:

du -sc /home/yourdomain

Shared Secure Server (SSL) Access

Shared Secure Server (SSL) Access

Your web hosting account may include access to a shared secure server. Your secure server is not really a separate server — it’s simply a way to display your existing web pages through an encrypted connection. Any page on your site can be called through the secure server.

To access one of your pages through the secure server, use the following path (replace “machinename” with the name of the server your domain resides on, replace “yourdomain” with your domain name without the TLD extension, and replace “filename.html” or “scriptname.cgi” with the name of the file you want to call through the secure server):

https://machinename.safe-order.net/yourdomain/filename.html

To access scripts located in your CGI-BIN, use this path:

https://machinename.safe-order.net/cgi-yourdomainscriptname.cgi

Note the use of the prefix https instead of the usual http. Secure calls require the use of the https prefix.

How do I find out my server / machine name?

You can find your server name listed on the main page of your web control panel. The panel below indicates that the server name for joes.com is fornax.

If the owner of joes.com wanted to call a page named mycoolpage.html through the secure server, he would simply link to:

https://fornax.safe-order.net/joes/mycoolpage.html

That same page would ordinarily (non-securely) be called by this URL:

http://www.joes.com/mycoolpage.html

You can also telnet to your domain, and simply look at your prompt. It should look something like:

sphinx:~$
-or-
ares:~$

Your server name is the word before the :~$ in your prompt.

UNIX Naming Restrictions & Conventions

UNIX Naming Restrictions & Conventions

Usernames, passwords, and filenames must comply with standard Unix naming conventions.

Username Restrictions

A name of anywhere from 3-16 alphanumeric characters (i.e., the numeric characters 0 - 9 and the alphabetic characters a - z) is legal for email accounts, FTP accounts, and telnet accounts.

Password Restrictions

POP/FTP/Telnet passwords should contain 6 – 8 alphanumeric characters. For the highest level of security, choose a “difficult” password that contains some combination of upper-case and lower-case letters and numerals.

Server File Names

There is no limitation to the length of file names on the server. You can use some punctuation marks in characters in any filename: (e.g. +_-&).

HTML Note: While you can use spaces in your filenames, please note that some versions of Netscape will “throw away” anything after a space. This will result in a “File Not Found” error. Also, the UNIX operating system doesn’t really know what to do with filenames that contain spaces. Therefore, it’s a good idea to avoid the use of spaces in your file names.

HTML Tip: Remember that Unix is case-sensitive. We’ve found that developing the habit of always naming your files in all lower-case avoids a great deal of confusion.

Your “index” or “home” Page

Your “index” or “home” Page

If you want your visitors to see a home page by typing http://yourdomainname.com/ instead of http://yourdomainname.com/mypage.html, you need to define a “default” page. On some servers, this page must be named index followed by an allowable extension. Allowable index page names are:

index.htm
index.html
index.shtml
index.cgi
index.php

IMPORTANT: Unix, many servers’ operating system, is case-sensitive. Your index page must be named with all lower-case letters. Index.htmldoes not equal index.html.

Your account already contains an index page when we set the account up — that’s the “Coming Soon” page you see when you browse your domain name or IP number. To replace that page with one of your own, simply delete the file named index.html and replace it with your own index page.

Order of Precedence

If you have have more than one file named index.* in your directory, the web server will follow a default order of precedence. The precedence may vary by server, but generally it will be similar to this:

index.cgi ? index.php ? index.html ? index.htm ? index.shtml

You can change the order of precedence and even define competely new index page names by creating (or editing) a file named .htaccess in your www directory (or in any subdirectory of your www directory. Just add the following line to your .htaccess file:

DirectoryIndex home.html index.html index.shtml index.cgi

The file names that appear after the DirectoryIndex specification specify allowable file names that will serve as index pages for the directory. The order in which those file names appear specify the order of precedence.

Publishing Your Web Site

Publishing Your Web Site

Once you’ve created your web site, you can upload your web files to your account using an FTP client or you can publish your site using Microsoft FrontPage, Dreamweaver, or most other HTML editors.

Here are a few things to keep in mind:

  • You must upload your files into your www directory. When you first connect to your account via FTP or Telnet, you will be in your home directory. Files placed in your home directory are not viewable through the web. Your web files should be placed in the www directory, which is one level below your home directory.
  • The correct configuration of FrontPage, Dreamweaver, and the other HTML Editors/ Publishers is critical. Incorrect configuration can result in unintended (and sometimes damaging) consequences. The hosting manual includes Microsoft FrontPage configuration instructions. For other editors/publishers, please review the documentation that came with those programs carefully before publishing.
  • If you want your visitors to see something besides our standard Coming Soon page, replace the file in your www directory named index.html with one of your own. CLICK HERE for more information about your index (home) page.

Additional Information: Creating and publishing Web pages

The easiest way to create a Web page is to use a Web-authoring tool, also called an HTML-authoring tool. Some of the more common authoring tools are Composer, which is free and available from Netscape, Microsoft FrontPage, which is available for purchase from Microsoft, and Dreamweaver, which is available for purchase from Macromedia.

These tools write the HTML code for you as you compose your page. Using them is similar to using a word processor such as Microsoft Word.TrainingTools.com offers free training and tutorials for FrontPage, Dreamweaver, and several other useful applications.

As an alternative, you can create Web pages by writing the HTML code yourself in a text editor program such as Notepad. Pointers to learning HTML include:

Linux Program and System Paths

Linux Program and System Paths

This is the usual setup for Linux based systems.

Path to Perl: /usr/bin/perl

Path to Sendmail: /usr/sbin/sendmail

Path to Date: /bin/date

Path to TCL: /usr/bin/tcl

Path to C++: /usr/bin/c++

Path to Java: /usr/local/java/bin

Path to Python: /usr/bin/python

Your WWW Directory

Your www directory is simply one level below your root, or home, directory. Either of the following two paths should work:

/home/yourdomain/www/
/home/www/yourdomain/

where “yourdomain” is your domain name without the top-level-domain extension (e.g., if your domain name is hostingmanual.net, the path to your www directory would be “/home/www/hostingmanual”.

All files you want to be publicly available from the web must be located in your www directory.