Problem: After updating the blog to WP 2.7 everything was running smooth. But when opening some of the plugin setting pages the server responded with a “500 Internal Server Error” – especially when using plugins like “XML Sitemap Generator for WordPress” or when uploading pictures. When I activated the “StatPress Reloaded”-plugin non of the admin section was accessible anymore.
Diagnosis: PHP is running out of memory.
Solution: If you are running your own root, dedicated or virtual server this is an easy bugfix: You just have to change the php.ini of your server and provide more memory to your PHP installation. On a shared hosting server – like at the webhosting solutions at 1and1 you often don’t have access to that central php.ini. But there is an easy workaround:
Create a text file and name it “php.ini” (without the quotes 
) and with a single line of code in it:
memory=20MB |
This file has to be placed into the directory /wp-admin/ within your Wordpress installation.
That’s it!
Loading ...
January 13th, 2009 at 11:06 am
i will try this in my blog http://hem.com.np i am actually getting 500 when i try to edit pages
January 13th, 2009 at 11:11 am
Hope this helps for you! All the best to Nepal from Germany!
January 15th, 2009 at 3:31 am
Choosing a good web site provider and registrar is critical for a successful internet business.
I have come to the conclusion that I made the dreadful error of choosing a company because it had a 5 page ad in a popular computer magazine. I believe I have put my trust in a straw man. In my opinion 1and1, with CEO Oliver Mauss, is a horrible company and many customers have voiced a host of complaints on various blogs.
It should be a warning that when their phone is answered by a recording that tells you if you have gotten a notice from NCO, a collection agency, to press a certain number. If they are a reputable business, why do they have to send so many accounts to a collection agency?
Patrick Frey (Patterico) of the Los Angeles District Attorneys Office alleges his domain was high jacked and put up for auction on SEDO. SEDO is an associate company of 1and1.
Patterico: “I believe I’m facing massive incompetence, thievery, or very possibly a deliberate combination of the two. It feels like evil intent — but not for political reasons. It feels like cyber extortion — people going after the almighty dollar. Commenters have pointed out corporate ties between 1&1, which can’t seem to process my timely renewal, and Sedo/Domcollect, which stood to profit from 1&1’s failure. Usually, corporate incompetence does not earn the corporation money — but 1&1 and its related companies have found a way to make money off of their own slipshod procedures.”
Patterico was able to regain his domain.
Also Investigative journalist, Kelli Jack, has written 30 articles about this company and has a suit pending against them. Kelli alleges that 1and1 stole her domain name and sold it. Kelli states: “1and1 should be shut down.” As of today Kelli is working with the Pennsylvania Attorney General.
I have filed complaints with the Federal Bureau of Investigation, Federal Trade Commission, Eastern Pennsylvania Better Business Bureau, ICANN, and others. I recommend everyone else having a problem consider doing the same.
The Washington DC, Pennsylvania Better Business Bureau has them listed as “Unsatisfactory” Read comments on the BBB why. Read some customer comments on Red Flag.
Warth Publishing Inc
January 18th, 2009 at 10:37 am
Hey it worked great.. i also got my archives page up after doing this… perfect… thanks again from Nepal to Germany
January 19th, 2009 at 8:01 pm
This worked like a charm– thank you so much!!
January 22nd, 2009 at 9:25 pm
What is being achieved by this? I am in a Hosted environment an dcurrently have 32mb or so allocated for PHP, does this commit 20mb of the total global specified or allocate an additional? presume the former.
January 23rd, 2009 at 9:06 am
Hello webmaster I think your post ?n for 500 Internal Server Error after upgrading to Wordpress 2.7 at 1and1-server | codedifferent.com? it?s really great. Hope some another good post to read on this blog in the future. Take care.
January 23rd, 2009 at 8:19 pm
Love your post!! Finally someone got it right!!! Would you mind if I put a blogroll link back to your post?
February 3rd, 2009 at 7:22 am
Perfect work!Keep posting
February 5th, 2009 at 9:44 am
That’s just sweet! Thank you.
Do you know how many times I’ve uninstalled, deleted, reinstalled plugins across multiple blogs since 2.7!
You are my Wordpress God for a Day.
February 24th, 2009 at 10:59 am
Thank you! It solved my “500 server error problem” in a WP 2.0.11!
Regards,
Greg
March 11th, 2009 at 6:09 am
Thanks so much! This resolved my problem with the admin area in WordPress 2.7. I am running my site wosko.us on 1and1 and this was the first problem I’ve experienced. Guess I haven’t pressed their hosting solution to the limits yet.
Thanks, Simon
March 26th, 2009 at 1:00 am
Thanks! Your awesome! worked for me!
March 26th, 2009 at 8:51 pm
great, thank you very much, worked for me too
April 1st, 2009 at 1:25 am
sorry didn’t work for me. I have also disabled all plug-ins one at a time. I get a blank page when I click on a page or comment in FoxFire and 500 internal error for each of these in Internet Explorer. I have updated all the plugins and have upgraded to the latest wordpress as well as the latest foxfire and internet explorer. I don’t have wp-cache. I have checked all the files for blank lines. The problem is with all of my websites each has a different theme on the websitesource server but one of them is on a yahoo server and all have the same problem?????
April 1st, 2009 at 7:21 am
@Jolene: I’m not sure but this may be a compatibility issue of your wordpress-theme. Did you test your website with an other theme, yet? Hope this hint helps to get your blog running again.
April 3rd, 2009 at 3:35 pm
I tried it and it’s not working for me, although my problem is slightly different. I am only getting the error message when trying to post / edit / update Pages. Categories are fine, plugins fine, etc. I deactivated, deleted and reinstalled all plugins, and that did nothing to help. Coincidentally we are hosting with 1and1 and they were of no help yesterday. Any suggestions would be greatly appreciated!
April 3rd, 2009 at 4:18 pm
Nevermind, I actually found this suggestion and it worked for me.
http://www.designforunity.com/archives/425/comment-page-1#comment-78
April 15th, 2009 at 3:50 pm
Thanks! I saw this problem for the first time today and this fixed it. Cool!
April 20th, 2009 at 10:36 pm
Thanks!!!!!!!!!!!!
That worked perfect for me. I was just getting ready to call 1and1 tech dept. Appreciate you sharing the knowledge.
April 25th, 2009 at 12:47 am
Thank you so much!! This problem is now solved. It waste me many time before I discovered your post and I could fixed it in 1 minute.
April 29th, 2009 at 5:32 am
Solved my problem. Much appreciated! I’m surprised not enough people mention this simple solution elsewhere on the web, making it harder to find.
May 8th, 2009 at 5:45 pm
thanx for this – I’m used to editing php.ini and .htaccess for many of my sites (joomla and drupal) but didn’t even think about it for wordpress, but I’ve been getting several error 500’s on my blog here and there.
I just put this in and I sincerely hope it works!
May 15th, 2009 at 10:00 pm
Thanks for this post!
May 18th, 2009 at 6:01 pm
Man, this is awesome. I have been looking and doing so many things to correct the problem. I came across this solution at it worked like a charm. That was a big sigh of relief.
June 11th, 2009 at 4:25 am
Thanks so much! I too use 1&1 and was running into this error whenever I tried to use the automatic upgrade feature on any of my plugins. The thought of having to manually upgrade all the plugins (which get updated frequently) was driving me nuts. I followed your steps and now it’s working like a charm. YOU ROCK!
June 12th, 2009 at 2:55 pm
Excellent -this resolved my issue as well. Perhaps it it time to re-evaluate 1and1. Thanks again for your help.
June 12th, 2009 at 6:54 pm
This solution totally worked for me. I has used the WP Auto Upgrade plugin and then got the 500 error after doing the “upgrade” from 2.7 to 2.8. Am using self-hosted Wordpress on 1and1. Thanks so much!
June 14th, 2009 at 6:26 am
I can’t believe that worked! I mean, it seemed so simple, I was about to write it off, but wow! Upgrade from 2.7.1 to 2.8, just so you know. Thanks greatly.
June 14th, 2009 at 7:41 am
This solution also worked for me. thx
June 15th, 2009 at 12:25 pm
Thanks for this! I have solved most of my Error 500s now – I was getting them every time I moved around the wp-admn/ area. Now I get them infrequently.
I will try this for myself and add a backlink to this page on my own blog entry about my experiences with the upgrade, at blog.redcentaur.com/2009/upgrading-to-wordpress-2-8/ .
I think it is important for the community to share this information.
June 15th, 2009 at 7:55 pm
[...] to Codedifferent.com for identifying the second problem in their blog post: Codedifferent.com identified that some hosted server configurations run PHP for users without [...]
June 16th, 2009 at 2:44 pm
[...] http://www.codedifferent.com/2009/01/12/solution-for-500-internal-server-error-after-upgrading-to-wo... [...]
June 22nd, 2009 at 2:10 pm
Thanks!!
It worked for me!!
You’re great!!!
July 1st, 2009 at 3:49 pm
life saver! just met this error while saving a draft post on WP 2.8..