Internal Server Error or Error 500

To determine the reason for error 500, review the logs. Perhaps the error.log file contains an entry that indicates the cause of the problem. Consider the most common options.

Lack of resources

If the reason is this, the problem is solved very simply - refer to the hosting-
provider with a request to increase resources.

Availability of inoperable scripts or limited time for their execution.

If the server can not process the scripts within a certain period of time, which is often a minute, then Error 500 Internal Server Error appears.

Also, webmasters may encounter this error if they run the CGI script from under Apache, if the time specified in the server settings is not enough to run the script.

If the scripts were previously working, and the problems appeared, for example, when moving to another hosting, the problem may be caused by other reasons. For example, the fact that the server blocks requests.

Errors in setting access rights

The file permissions must be equal to 444 or644. CHMOD for folders should not differ from 755, ie only the owner of the resource can view them. Script access rights should be denoted as 600. Otherwise, the server, for security reasons, blocks access to the script, even if it is functional.

If the reason for the error 500 is in this, use the FTP manager to change the permissions. With these functions, Filezilla does a great job.

The .htaccess file contains unsupported directives

Check if the .htaccess file is present in the root of the site, or elsewhere. If there is one, open it with any text editor. You can use Notepad.

Error 500 may appear if you useserver running on suPHP, i.e. which supports php.ini. If there are directives in the .htaccess file that change the parameters of the PHP environment, you may experience problems. The most common directives are php_admin_flag, php_flag and php_value.

Often, as instructions, global variables are included - Register Globals.

This problem is solved very simply -You can simply delete unwanted parameters. Another option is to comment them out by adding the # sign to the beginning of the line. Between the grid and the name of the directive there should be a space character.

If you need to performcommented parameters, they can be written in the php.ini file. In this case, you do not need to use php_admin_flag, php_flag and php_value - simply mark them according to the principle: "the name of the required parameter = On".

Fatal error PHP

This problem can occur if PHPworks on the principle of CGI. In this case, you need to carefully check the program code, diagnose and fix errors. Note that the end of the CGI script lines should not be in the Windows format (rn), but should be denoted in the UNIX (n) format.

If none of the solutions offered does not solve the error, contact the hoster. In detail, explain to him when and after what actions the error 500 appeared. Ask for the reasons for the problem andhelp in its elimination. In case the hoster is not able to find out why the error appeared http 500 Internal Server Error, contact the CMS support that you are using. In the letter, be sure to include all the details, incl. - comments on the hosting provider regarding your situation.