Magento Hosting

about the author

related articles

17 Responses to “500 Internal Server Error After Magento Installation”

1. shuron on January 7th, 2009

   Be aware, after update of magento check the URLS of the site. Sometimes .htaccess is overriden. So you need to back upt it befor any upgrade.

2. Jesse on October 29th, 2009

   Hi,

   I saw your post about permission having got the 500 page after the first step of the installer from the page http://www.alloywheelrims.co.uk/downloader/

   all was well (after adding php.ini files to increase memory) and then press nest step……500.

   Anyway, changed the permissions as above and still no joy.

   My PHP info say this: http://www.alloywheelrims.co.uk/php_info.php

   Could you give me a pointer?

   Thanks

3. Scott @sydneydesign on November 17th, 2009

   Hi Great post thanks for the info.

4. Oliver on November 25th, 2009

   In my case it was not about the permissions, it was about the htaccess override.
   Just needed to change the rewrite base from /magento/ to / and it worked again.
   But for some minutes my heartbeat was “a bit higher” then usual

5. Owen on March 17th, 2010

   thanks for this, very helpful!

6. Cynthia on March 24th, 2010

   I got the error AFTER i changed the permissions to 777. Now the magento wizard will not start and page not found when http://www.wireyourworld.com/magento is tried.

   Oliver seems to have a solve but I’m unclear on what he means. the htaccess in the main magento directory? The line like that in mine says #RewriteBase /magento/ no from or to?

7. Andrew Taylor on June 11th, 2010

   I just had a dreaded 500 error after trying to get Magento Connect to update. Changing the permissions on the above folders to 755 solved it for me

8. cft on August 4th, 2010

   good post,
   though, only the first page of the sample data where visible until I set the rewrite base from /magento/ to / as suggested by Oliver

9. Seb on August 24th, 2010

   In my case it was RewriteBase, which was set to “/” but guess what – I’ve forgotten to uncomment it by removing the hash symbol “#”.

   Now it’s working like a charm!

10. Nurali on November 6th, 2010

    Hi there,

    I have fix my issue of 500 error by looking at the error log and it says:
    (.htaccess: Option FollowSymLinks not allowed here). So I disable it by putting a # at the command. Now I finally can view the setup page.

    Thank you.

11. Chandrashekar Reddy on November 17th, 2010

    i am searching about Magento Installation for developing a e-commerces website.

12. Jerry Smith on April 29th, 2011

    Thanks It also helped with some plugin issues I was having.

13. duck_prince on September 24th, 2011

    Hi,
    I set folders and file you mention above to 755, but still run into “Internal Server Error” problem.

14. Sukhwinder Singh on November 25th, 2011

    That’s great buddy

    It’s working

15. johs on December 11th, 2011

    yes I have never resolved this bull shit

16. Jordi on December 20th, 2011

    Perfect.
    Has been the solution to my problem.

    Thanks

17. Hannan on January 5th, 2012

    I got no information about this 500 error. yes although every one tried to answer best way but all in vain

    any how guys if you are getting this sort of problem then I suggest you these options:

    1) Rather than doing direct installation on live server you better to check that on your local PC . That will give you easy option if the package itself has some configuration problem that will not create any headache for you to start with new project to try again in Xampp/ wampp.

    And upload your local work to live server you just then need to make changes in “config_data” some sort of named table and ETC>> LOCALE.XML and removing all from cache from VAR>>CACHE .

    2) Other option it gets some configuration problem sometimes and htaccess override that doesn’t let you access your any .php file as well. So you just create another folder on side and out of your current magento folder. i.e.

    OLD : magento_projects/myMagentoProject1
    NEW : magento_projects2/myMagentoProject1

    And this will work. This is a good tip for specially those guys who suddenly gets into this problem

Leave a Reply