Posting in the Magento forums has been disabled pending the implementation of a new and improved forum solution which should better serve the community.

For new questions please post at magento.stackexchange.com, the community-run support site for the Magento community. We will be providing updates on the new forum solution soon. For questions or concerns please email community@magento.com.

Magento Forum

What is the fix for the system backup “Internal Server Error 500”? 
 
patrick_004
Member
 
Total Posts:  33
Joined:  2010-11-03
 

Ok so after running the system backup I get an “Internal Server Error 500”. After doing some research I found that I need to change the permissions on the file index.php from 666 to 644. (Funny how the site goes to crap with the permission number of 666) But my question is, how do we keep this from happening again? I feel like i should not have to go back and change the permissions on my files after a backup..

 
Magento Community Magento Community
Magento Community
Magento Community
 
stormbyte
Jr. Member
 
Total Posts:  2
Joined:  2013-07-11
 

Monty22 give you the correct answer for your ERROR 500 problem. I had some trouble and solved consequently thanks to the linked above.

Cheers!
Akaoma

 
Magento Community Magento Community
Magento Community
Magento Community
 
patrick_004
Member
 
Total Posts:  33
Joined:  2010-11-03
 

I know that’s the right answer, but the question is “How do we keep it from happening again?” Its a nice little fix, but this is something i should not have to do every time i back up my site..

 
Magento Community Magento Community
Magento Community
Magento Community
 
patrick_004
Member
 
Total Posts:  33
Joined:  2010-11-03
 

Hello?? So all i get is a temporary fix?

 
Magento Community Magento Community
Magento Community
Magento Community
 
chiefair
Mentor
 
Avatar
Total Posts:  1848
Joined:  2009-06-04
 

They answered it over on StackExchange. <-- This is a link. Magento’s backup system is a site crippler.

And it’s agreed that the file permissions change is a Charlie Foxtrot. It kills any system that uses suPHP, cPanel WHM or similar security schemes. And no, there’s no permanent fix yet.

 
Magento Community Magento Community
Magento Community
Magento Community
 
damrussell01
Jr. Member
 
Total Posts:  3
Joined:  2013-10-16
 

This is a \’get all\’ blunder created by the Web server. Fundamentally something has happened, yet the server can not be more particular about the lapse condition in its reaction to the customer. Notwithstanding the 500 failure told once again to the customer, the Web server might as well produce an interior slip log which gives more portions of what happened. It is dependent upon the specialists of the Web server webpage to place and break down these logs.

สก็อตเทป | เรซิน

 
Magento Community Magento Community
Magento Community
Magento Community
 
digicloud
Jr. Member
 
Total Posts:  21
Joined:  2012-02-27
 

http://blog.onlinebizsoft.com/magento-solved-internal-server-error-500-error/

Try that link, I fixed my issue by changing the index.php permissions to 755 and now backend and front end are now up

 
Magento Community Magento Community
Magento Community
Magento Community
Magento Community
Magento Community
Back to top