Internal Server Error 500 in Magento
17 Comments 8th MAR 2009 | Posted by Tomislav Bilic in Magento
Many of us who started experimenting with this interface and tried to place various values for Base URL, came to a dead end where Magento breaks. Usually, we get Internal Server Error 500 with each page load. The problem lies in the fact that we can no longer open the Magento administration to correct the error. What needs to be done in such a scenario?
One of our clients wrote me a message today:
I have put www.mydomain.com in a bad spot. I changed the base URL to {{base_URL}} and now im getting a 500 server error on both the front end and the admin panel. I have looked through the database and cannot find the right field to change this value back. Can you point me in the right direction?
The client went to System> Configuration> Web> Unsecure and placed an invalid value for Base URL field. Beware of this field. Unfortunately, Magento just updates it without any pre-warnings, but change of this specific value can cause Magento to crash.
Usually, we get an error that looks like this:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@mysite.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
The client was on right path to find a solution. We need to open MySQL (usually via php MyAdmin) and find core_config_data table. Once there, manually update 2 rows:
- config_id:3 web/unsecure/base_url => http://www.mydomain.com/
- config_id:4 web/secure/base_url => https://www.mydomain.com/
Everything should work now. Hope this will help someone.
If you like what you read, please share it.
To post code in comments, place your code inside [code] and [/code] tags.
There are 17 comments (Add Yours +)
Meet The Inchooers, the funny bunch of magento developers.
August 23rd, 2009 at 17:11
Great thanx, I just messed it up with setting the base url for another frontstore… I thought…
February 2nd, 2010 at 5:55
Thanks for this… i was having same problem….
March 17th, 2010 at 17:08
it works on my site,thanks again!
June 6th, 2010 at 16:18
How about when everything is working fine in the front end but when you try to access the back end or admin panel, you get this error sometimes and need to keep pressing F5 or refreshing the page to takr it away?
I have read about the right with the files and I have tired everything and I still get the error 500 sometimes when I try to access the admin panel.
Thanks
June 16th, 2010 at 21:23
I have the identical same problem as Raul there
June 16th, 2010 at 22:37
Hi Dan,
Would you like to share contacts and the one who get this bug first will tell the other?
diazwatson@rewstudio.com
June 17th, 2010 at 15:44
Hi Raul… sent you a response via the email you posted on here.
August 20th, 2010 at 14:46
I’m having the same issue, Front end works back end is down 500 error. If you guys know the fix please email me jkeller@gonecoastaldesign.com I would be so thankful.
August 20th, 2010 at 15:06
Currently I still have no fix. From what I read over the past several weeks as I off and on still look for a fix, seems to be a webhosting server memory problem when using 1and1 webhosting.
August 20th, 2010 at 17:10
Yikes, Still dealing without being able to get into admin after a few weeks? I may go the hard road and reinstall or go to an old reliable commerce product. Scary news when I can’t get to the sales I have pending in my cart =( Let me know if you hear anything!
August 20th, 2010 at 17:15
Actually yesterday I was reading an article somewhere about the configuration of the php5.ini file.
There is where you specify the memory limit for magento.
I will play a bit with it and let you know guys what comes up
August 20th, 2010 at 18:07
John: Re-install will not help. I’ve installed this software on two seperate domains with two seperate hosting accounts (both 1and1) and the problem persists. I am curious to see what Raul finds with changing the memory settings in what I believe to be the .htaccess file. I’ve done that in the past initially but had no success either.
August 25th, 2010 at 2:06
Hi everyone, sorry I been bit busy these days and that way I could have a look to the Internal server error Issue. I will do as soon as I finish updating one of my sites.
Although this is not the correct post, if someone is having trouble importing many configurable products, the solution (what worked for me) is create an advance import profile.
Going back to the Internal Server Error, I am still having this problem but fortunately at the end works by pressing F5 many times
August 25th, 2010 at 15:45
Pressing ‘F5′ has been the band-aid fix for the time being 3x (usually). Can I ask what web hosting people are using on here that are experiencing this internal server error problem?
August 25th, 2010 at 16:33
HeartInternet.co.uk
September 1st, 2010 at 18:22
I had edited an item in System> Configuration> Web> as I was in the process of adding a new store to my existing installation and wanted to select a diferent cms page, and got the Server Error. I fixed it by doing a server restore on GoDaddy. Now any time I edit anything within System> Configuration> Web> or Design I get the Server Error. When I click save does anyone know which files are being corrupted?
September 2nd, 2010 at 0:36
I think this is more related to the php5.ini file and the .htaccess file rather than a file being corrupted.
If you look at the posts you will notice all of us have this problem, even in a fresh installation.
Why I say this is a php5.ini and .htaccess problems is because looking at the servers logs I see that every time the 500 error comes up, something like “php script run out of memory….” appears in it.
that is all I can say by now
Hope it helps