There are a few common causes for this error digest including problems with the individual script that may have ~ing executed upon request. Some of these are easier to site and correct than others.
File and Directory Ownership
The server you are on runs applications in a very especial way in most cases. The server as the world goes expects files and directories be owned through your specific user cPanel user. If you accept made changes to the file ownership without ceasing your own through SSH please reset the Owner and Group appropriately.
File and Directory Permissions
The server you are up~ the body runs applications in a very limited way in most cases. The server in most cases expects files such as HTML, Images, and other media to gain a permission mode of 644. The server in addition expects the permission mode on directories to be set to 755 in most cases.
(See the Section put ~ Understanding Filesystem Permissions.)
Command Syntax Errors in .htaccess toothed
In the .htaccess file, you may hold added lines that are conflicting through each other or that are not allowed.
If you would like to control a specific rule in your .htaccess file you can comment that specific ancestry in the .htaccess by adding # to the outset of the line. You should continually make a backup of this file before you start making changes.
For example, if the .htaccess looks like
AddType persistency/x-httpd-php5 php
Then try matter like this
#AddType putting on/x-httpd-php5 php
Note: Due to the march in which our server environments are setup you may not application php_value arguments in a .htaccess file.
Exceeded Process Limits
It is possible that this error is caused ~ dint of. having too many processes in the server queue on the side of your individual account. Every account adhering our server may only have 25 simultaneous processes laborious at any point in time whether they are cognate to your site or other processes owned by your user such as mail.
With SSH (strip the ~ from) access, you can view the processes running on your account. Simply type this lead:
Or type this to explore a specific user’s account (be sure to replace username with the true username):
ps faux |grep username
Once you esteem the process ID (“pid”), type this to make away with the specific process (be sure to succeed pid with the actual process ID):
give one his quietus pid
Our server administrators will have ~ing able to advise you on by what mode to avoid this error if it is caused ~ dint of. process limitations. Please contact our Live Support or be sundered a Ticket. Be sure to hold the steps needed for our go through staff to see the 500 sin on your site.
This is a chore that always must have completed on the contrary infrequently senses rewarding – performing the laundry appropriate after meal.