The AceHostNet knowledgebase is a growing collection of
support information which is generated by us and our users
for our users. By keeping this collection of support
growing, our customers are helping us create the most
detailed and complete collection of support documentation
possible.
A: Troubleshooting CGI-bin Problems
Below are solutions to some of the more common CGI script problems.
When I activate my CGI program, I get back a page that says "Internal server error. The server encountered an internal error or mis-configuration and was unable to complete your request."
This is generally caused by a problem within the script. Check your script settings again to see that you have entered the correct server information and have set the correct permissions for the script. If this information is correct, you'll need to contact whoever wrote or is distributing the script for further assistance.
I am being told "File Not Found," or "No Such File or Directory."
Upload your Perl or CGI scripts in ASCII mode, not binary mode.
When I test my Perl script in local mode (by Telnet), I have the following error:
"Literal @domain now requires a back slash at myscript.pl line 3, within string. Execution of myscript.pl aborted due to compilation errors."
This is caused by a misinterpretation by Perl. You see, the "@" sign has a special meaning in Perl. It identifies an array (a table of elements). Since it cannot find the array named domain, it generates an error. You should place a back slash (\) before the "@" symbol to tell Perl to see it as a regular symbol, as in an email address.
I am getting the message "POST not implemented."
You are probably using the wrong reference for cgiemail. Use the reference:
/cgi-bin/cgiemail/mail.txt
Another possibility is that you are pointing to a cgi-bin script that you have not put in your cgi-bin directory. In general, this message really means that the web server is not recognizing the cgi-bin script you are calling as a program. It thinks it is a regular type of file
A: Our network's servers are very basic in terms of Perl installation. We do not use any cgi-wrappers etc, which means that even sloppy code alot of times will work once the scripts are chmod'ed and configured.
If you are unable to troubleshoot a problem with your scripts, and we have already reviewed the script in question, we will respond to your ticket telling you to contact the maker of the script. If the maker is unable to assist you, your other option is to have AceHostNet.net look at it. Once we review the script (remember though, we are not Perl Programmers, but more than likely, we can find any mistakes if we review each line of code) we will charge you $50.00
