Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

500 Internal srver error

Discussion in 'General Discussion' started by alstar, Nov 8, 2009.

  1. alstar

    alstar Registered

    Jun 14, 2009
    Likes Received:
    Trophy Points:
    Hey guys I have no idea what a 500 internal server error means. How can I fix it? I can't find a straight answer anywhere on the web. Please advise. Thanks in advance.
  2. thewebhostingdi

    thewebhostingdi Well-Known Member

    Jan 10, 2008
    Likes Received:
    Trophy Points:
    Kindly check the error logs for the exact error message as there are many reasons regarding the 500 Error message. You can check the error logs from the below mentioned location:


    If you have an root access to the server then you can check the logs from SSH from the above mentioned location.
  3. ckh

    ckh Well-Known Member

    Dec 6, 2003
    Likes Received:
    Trophy Points:
    Phoenix, AZ
    cPanel Access Level:
    DataCenter Provider
    Another option is to log into the cPanel account for the site that has the error, scroll down to the logs section and click on the error log. You'll receive a better explanation of what is causing the 500 server error there. The real cause of the error isn't displayed publicly for security reasons so you need to view the logs to see what is specifically causing the error.
  4. Spiral

    Spiral BANNED

    Jun 24, 2005
    Likes Received:
    Trophy Points:
    There is a wide variety of causes for Error 500 so without looking at your log files as the
    previous posters suggested you do and knowing the information from that, I couldn't
    tell you directly to any one single item or cause.

    However, the following is the most common causes of Error 500 in ranking order ...

    1. Server runs SuPHP or phpSuExec and the user has a PHP script located
    within a folder or below a folder tree location that has 777 permissions.

    2. Server runs SuPHP or phpSuExec and the user has a PHP script that is
    itself configured to permission 666 or 777.

    3. Server runs SuPHP or phpSuExec and a PHP script is not owned by
    the owner login for the account where the script is located.

    (Keep a watch for files and scripts owned by "nobody" in particular)

    4. Server runs SuPHP or phpSuExec and the user has added "php_flag"
    or "php_admin" commands to a '.htaccess' file located in the account.

    5. A non existent or otherwise invalid command has been added to .htaccess

    6. Perl / CGI scripts were uploaded in "binary" transfer mode by mistake.

    7. Permissions for the "public_html" folder are wrong

    8. Apache handlers are not setup correctly (ALL SITES WILL BE 500)
  5. linux7802

    linux7802 Well-Known Member

    Dec 14, 2007
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator

    This is most common problem most of the clients facing after enabling the Suexec on server.First you need to check the server is suexec enabled or not? for that please refer following URL

    Simply check server is SuExec or not? | Linux Servers cPanel webhosting blog

    If your server is suexec than check servers apache logs and correct it and if you are not able to understand the apache logs then copy and paste in this thread so that we can help you to resolve your 5oo Internal Server Error message :)

Share This Page