Since 500 Internal Server Errors aren't ever really caused by Wakaba or Kareha themselves, but are still a big problem for lots of people, I'm setting up this thread to discuss various problems and solutions related to them.
Firstly, things that often cause Internal Server Errors:
#!/usr/bin/perl
is the correct one, but sometimes Perl is installed elsewhere. In that case, you will have to find out where, and change the hashbang. On Windows servers, it should often be changed to #!perl
.Options +ExecCGI
and AddHandler cgi-handler .pl
. SOMETIMES, but definitely not always, this can be put into the .htaccess
file. See the next point..htaccess
file. Spelling errors, trying to use modules that are not installed, or trying to use options that have been forbidden elsewhere will all cause Internal Server Errors.Secondly, things that DO NOT cause Internal Server Errors:
Third, what to do when you get Internal Server Errors?
error_log
. Internal Server Errors often generate two or more lines in the log file, make sure you read them all.Try the Perl test script:
#!/usr/bin/perl
print "Content-Type: text/html\n\n";
print "<html><body><h1>Perl is working!</h1></body></html>";
If this doesn't run, work with the server config until it runs, and only when it does, get to work on Wakaba.
Dear >>5,
Thank you for you opinion on the matter. It is being reviewed by our trained message scripts for traces of intellegence, and will be fowarded to a human if any is found. We at iichan thank you for your understanding, and will respond at the soonest a representitive is available.