The server you are on runs applications in a very particular way in most cases. The machine generally expects files like HTML, Images, and other media to have a permission mode associated with 644 . The server also needs the permission mode on directories to be set to 755 in most cases.
File and Directory Ownership
Then try something like this
File and Directory Permissions
Once you have the process IDENTIFICATION (“pid”), type this to kill the specific process (be sure to replace pid with all the actual process ID): ps faux
Command Syntax Errors within. htaccess file
ps faux |grep username kill pid DirectoryIndex default. html
#AddType application/x-httpd-php5 php Or type this particular to view a specific user’s account (be sure to replace username with the actual username): For example , when the. htaccess looks like Note: Due to the way in which the machine environments are setup you might not use php_value arguments in a. htaccess file. DirectoryIndex default. html
AddType application/x-httpd-php5 php
Surpassed Process Limits
If you would like to check a specific rule inside your. htaccess file you can remark that specific line within the. htaccess by adding # to the beginning of the line. You should always make a backup of this file before you begin making changes. There are a few common causes with this error code including problems with the individual script that may be carried out upon request. Some of these are usually easier to spot and right than others. The server you are on runs applications in a very specific way in most cases. The machine generally expects files and directories be owned from your specific user cPanel user . When you have made changes to the document ownership on your own through SSH please reset the Owner plus Group appropriately. (See the particular Section on Understanding Filesystem Permissions. ) In the. htaccess file, you may have additional lines that are conflicting with each other or that are not allowed. Your own web host will be able to advise you on how to avoid this error if it is caused by process limitations. Make sure you contact your web host. Be sure to include the steps needed to see the 500 error on your site. It is possible that this error is brought on by having too many processes within the server queue for your person account. Every account on this server may only have twenty five simultaneous processes active at any time in time whether they are associated with your site or other procedures owned by your user for example mail.