500 Internal Server Error
If your page responds with an "Internal Server Error" (error code 500) you first have to determine what caused it. It's either ProcessWire or (more likely) your server which has a conflict with a command in the .htaccess file.
If the error message shown is cursive, uses a sans-serif font like arial and in smaller font size it's probably an error caused by ProcessWire. In this case you it's probably better to ask in the forum directly.
If the error message looks different and appears on every site - including the homepage - you're trying to reach it's probably caused by your server which has a conflict with a command in the .htaccess file. This happens often because every hoster configures the server like it wants to. So sometimes they disable some commands, which causes this error. This guide will lead you through solutions for the most common error triggers.
If you take a look in the ".htaccess" file which should be in the root folder of your installation you already see some notes at commands which could be the problem. The first command you should try to deactivate by putting a # in front of it is "Options +FollowSymLinks". Sometimes you have to put a # in front of "Options -Indexes", too.
Options -Indexes Options +FollowSymLinks
If this doesn't change anything and you're still getting the same error continue to comment (put a # in front of the line, which basically declares the line as a comment) the following. You should comment each of this lines:
<IfModule mod_php5.c> php_flag magic_quotes_gpc off php_flag magic_quotes_sybase off php_flag register_globals off </IfModule>
If the error is still there try to comment:
SetEnv HTTP_MOD_REWRITE On
And finally - if it's still not working - comment everything. If it works then you can start uncommenting line for line until the error appears again. Then you know which line/command causes the problem.
Next: Login Problems »
Your e-mail is kept confidential and not included with your comment. Website is optional.