The URL to the control panel is as follows: http://www.yoursite.com/cpanel

Important Note: Make sure you substitute yoursite.com for your actual domain name.

A web user is an account that has its own web space that is separate from the main site. It can be accessed via http://www.your-name.com/~ftpuser (replace "your-name.com" with your actual domain name and "ftpuser" with the actual web user).

Here's how you create a web user for your site:

1.	Log in to your control panel
2.	Click on your domain name
3.	Click on WEB USERS
4.	Enter desired web username (the web username has to be unique on the server)
5.	Click on ADD
6.	Enter desired password
7.	Click on UPDATE

1.	Log in to your control panel
2.	Click on your domain name
3.	Click on REPORT

5 1.	Log in to your control panel
5 2.	Click on your domain name
5 3.	Click on DIRECTORIES
5 4.	Click on ADD
5 5.	Next to "Protected Directory", enter the path to the directory
56.	Select non-SSL, it will be created in the httpdocs directory
5 7.	Enter "Header Text" if any
5 8.	Click on UPDATE
5 9.	Select directory that you have just created
10.	Enter desired username
11.	Click on ADD
12.	Enter desired password
13.	Click on UPDATE

First, you need a FTP program such as WS_FTP LE which can be downloaded from http://download.cnet.com/

Run the FTP program and enter the information sent in your set up e-mail for:

1.	FTP hostname (ftp.yoursite.com)
2.	FTP username (Your account username)
3.	FTP password (Your account password)

Once you are connected, you should put your files into the httpdocs directory.

Any of the following will be recognized as the default page for any directory within your site including the top level directory:

index.html, index.htm, index.shtml, index.php, index.php4, index.php3, index.cgi

NOTE: Linux is case-sensitive, so Index.html is not the same thing as index.html

Most likely your domain name registration or modification has not propagated yet. Successful domain name registration or modification may take up to 48 hours to propagate.

Enter your domain and verify via our "online domain name search" www.webhostingmalaysia.com/domain_name_registration.htm

For each error page you want to customize, create the following html files:

File Not Found (404) = not_found.html
Bad Request (400) = bad_request.html
Forbidden (403) = forbidden.html
Internal Server Error (500) = internal_server_error.html

Once you created your custom error pages, upload them to the /error_docs directory.

Follow these steps:

1.	Log in to your control panel
2.	Click on your domain name
3.	Click on MAIL
4.	Enter desired mail name
5.	Click on ADD
6.	Check the "Mailbox" option
7.	Enter desired password
8.	Click on UPDATE
9.	If successful the icon under "B" should now be in color

To receive e-mail sent to this mailbox you now need to set up your e-mail program.

Follow these steps:

1.	Open Outlook
2.	Click on TOOLS > ACCOUNTS
3.	Click ADD > MAIL
4.	Enter your details including the mailname (account name) and password you created in the control panel for this mail account

Incoming mail (POP3) server: mail.your-name.com (replace "your-name.com" with your actual domain name)

Outgoing mail (POP3) server: mail.your-name.com (replace "your-name.com" with your actual domain name)

Click on FINISH

"The connection to the server has failed. Account 'your-name.com', Server 'your-name.com', Protocol SMTP, Port 25, Secure(SSL) No..." or "550 Relaying denied"

There could be 3 reasons for this:

1.	Our servers use pop/auth for relaying e-mail, this means you have to check/collect your mail before sending, if you use Outlook you can do the following:
	a.	Open Outlook
	b.	Click on TOOLS > ACCOUNTS
	c.	Select the mail account and click PROPERTIES
	d.	Click on SERVERS tab
	e.	Check the "My server requires authentication" option
	f.	Click on APPLY > OK
2.	Most ISPs do not allow private SMTP mail servers i.e. your-name.com, to over come this change your SMTP mail server in your e-mail program to your ISP's.
3.	Some firewall software/hardware is known to degrade/block e-mail connection

Follow these steps:

1.	Log in to your control panel
2.	Click on your domain name
3.	Click on MAIL
4.	Enter desired mail name
5.	Click on ADD
6.	Check the "Redirect" option
7.	Enter the e-mail address to redirect to
8.	Click on UPDATE
9.	If successful the icon under "R" should now be in color

Follow these steps:

1.	Log in to your control panel
2.	Click on your domain name
3.	Click on PREFERENCES
4.	Check the "Catch to address" option
5.	Enter your actual e-mail address
6.	Click on UPDATE

1.	Ensure to change the default transfer mode for FTP to ASCII
2.	Ensure to set permissions to 755 by using the chmod command in FTP
3.	Ensure the permissions of the script and the CGI-bin are set no higher than 755

1.	Path to Perl - #!/usr/bin/perl or /usr/bin/perl
2.	Path to sendmail - /usr/sbin/sendmail or /usr/local/psa/qmail/bin/sendmail
3.	Path to CGI-bin - /usr/local/psa/home/vhosts/your-name.com/cgi-bin

Our support does not cover CGI script debugging or installation for free. We consider this a function of web design and employee in-house web development and consulting staff to assist in these matters for additional charges. If you would like assistance with CGI script debugging or installation our pricing is negotiated between you, the customer and one of our professional programmers on an hourly rate. For further information, please email info@WebHostingMalaysia.com.

Here are a few things to try when you are troubleshooting a CGI script:

1.	First, thoroughly read through the instructions that came with the script
2.	Ensure that you have uploaded your script to your CGI-bin
3.	Ensure to upload to the server in ASCII mode
4.	Ensure there are not any DOS/Windows carriage returns (i.e. ^M) in the script
5.	Ensure script's magic comment specifies where Perl is located: #!/usr/bin/perl
6.	Verify that all the paths are correct, do not use "www" in public directory path
7.	Check if all the file permissions are set correctly and are set no higher than 755
8.	Check the domain's error_log file via FTP, sometimes you see a "Premature end of script headers" error which usually means that the file has been corrupted

Over 90% of the time it is a problem with the module dependencies. For security reasons we do not undertake any module or software installation.