from Q87 International Hosting Servers Merchant FAQ
Website Navigation

WEB HOSTING PLANS:
 • Q1 - Starter
 • Q2 - Bronze
 • W1 - Silver
 • W2 - Gold
 • Dedicated Servers

ADDITIONAL SERVICES:
 • Merchant Account
 • Secure Certificates

FREE E-COMMERCE:
 • Control Panel
 • Secure Server
 • Bonus Packs

NEED TO KNOW:
 • Order Online Now
 • FAQ
 • Our Network
 • Terms of Service
 • Contact Us

HELPFUL LINKS:
 • Domain Names
 • WHOIS Search
 • Trusted Businesses






Questions
cPanel Control Panel Manual (Linux Accounts):
http://www.cpanel.net/docs/cpanel
Domain FAQs
Email FAQs
CGI FAQs


Answers
Domain FAQs
Email FAQs
  • What are the mail server settings to configure my email software?
    Incoming POP/IMAP Email:
    mail.yourdomain.com

    Outgoing SMTP Email
    (port 25; or 26):
    mail.yourdomain.com

    Account Name:
    username@yourdomain.com

    The server requires SMTP authentication. Logon using:
    username@yourdomain.com

    Outlook Express users, please note: Go to the "Tools" menu, and choose "Accounts..." Then choose "Add"; then "Mail..." Then enter the information you're asked for, including the information above.
  • Why am I getting '550 unknown local host, not a gateway' errors?
    To combat SPAM, our email servers require authentication to send/recieve mail. All remote clients must enable the SMTP authentication function to send outgoing mail (see answer above).
  • [Back to top]

CGI FAQs
  • What is the path to Perl?
    The path to Perl tells your script where to find the Perl processing program on your server. This line should read:

    #!/usr/bin/perl

    [Back to top]

  • What is the path to sendmail?
    Sendmail is the program that allows a script to send e-mail. This line should read:

    /usr/sbin/sendmail

    [Back to top]

  • Does the server support server side includes (SSIs)
    Yes. All pages that utilize SSI must be named with the extension ".shtml."

    In order to use SSI, utilize the following format. Be sure that there are no spaces, except between the words "include" and virtual," and that the line is not indented.

    <!--#include virtual="/directory/filename.ext"-->

    [Back to top]

  • What is a 400 Internal Server Error and how do I fix it?

    This is a common error found in a Web browser when you are attempting to run a Perl or CGI script that has problems. The three most common reasons for this error are the following:
    • Your script permissions are set wrong. Try setting them to 777 temporarily while troubleshooting the error.
    • Your script was uploaded in binary file format instead of ASCII. You must upload Perl and CGI scripts in ASCII format only.
    • Your path to Perl line is wrong. The very first line in your Perl program must be "#!/usr/bin/perl". You cannot have any spaces between your characters, and you cannot have any hard returns or text lines before this line.

    If none of these three reasons correct your errors, then you may want to take a look at your Error Log files. If the script is coded to print the errors it encounters, these will be displayed in your Error Log file of your server.

    If all else fails, you can usually find the script errors by logging in to your server via Telnet and running the script from the command line. Once you are logged into the server, you must change directories until you are in the one in which your script resides. At that point, type the following at the command line:

      perl filename.cgi -w

    Note: There should be one space after the word "perl". "filename.cgi" should be the actual filename of the script you are having problems with. "-w" is a warning switch, this will prompt Perl to give you any errors it sees in the script and it will give the line number that the error is on or near.

    [Back to top]

  • What does CHMOD mean?

    When adding new files such as CGI, Perl, etc. it is necessary to set specific permissions for the script to work.

    The UNIX directory and file structure has a system of permissions. You have permission to read a file, you have permission to write to a file, and finally, you have permission to execute a file. However, you are not always you. Unix splits identities into three categories. The first is you, the owner of the file. The second is the group you belong to. And third, others is the world, basically anyone who comes to your website.

    To change permissions you must issue a "change mode command", or more commonly referred to as the UNIX command "chmod". The documentation for your file or script will usually come with the proper permissions you need to set for your program to work. To set permissions, there are basically 2 methods UNIX recognizes.

    With FTP (and Telnet) your file properties are shown as -rwxr-xr-x.

    The first space designates if this is a directory by the letter "d".

    The next three characters designate the permissions for the "owner", r = read, w = write, and x = execute if the permission is set to "on" and "-" is the permission is set to off.

    Permissions for the "group" and "world" (other) are designated by characters 5-7 and 8-10 respectively.

    The second method we are calling the alpha method because permissions are set, by way of a telnet session, using alpha characters. You simply specify with the group or groups whose settings you want to change ("u" represents "user" or you, "g" represents "group", "o" represents other or world and "a" represents "all") and all the settings you want to change ("r" for read access, "w" for write access, and "x" for execute access). To set your file world-writable, you would type "chmod o+w ". To set it executable to everyone, you would use "chmod a+x <filename>". The plus sign indicates you're adding permissions. You can use a minus sign to remove permissions.

    [Back to top]




  Hosting Servers Merchant FAQ



We accept:

Copyright © 1999- Q87 International, San Diego, California - All Rights Reserved. Terms of Service.