★ Black Friday★ Cyber MondayWeb hosting up to 85% off, checked on each host’s own siteGrab the deals →

How to Fix 500 Internal Server Error in WordPress (2026)

Share

In December 2006 QuickOnlineTips was down for 36 hours with a 500 internal server error on every page. My host’s replies came 24 hours apart and didn’t fix it, so I investigated myself. Hosting WordPress in a subdirectory let me put a temporary index page up, and the real culprit turned out to be the WP-Cache plugin: clearing its cache brought the blog back instantly. The lesson still holds: work through the likely causes methodically. Here’s how in 2026.

Fix 500 internal server error in WordPress

Quick answer: A 500 error means the server hit a problem it couldn’t explain. In WordPress, check the PHP error log first, then rename .htaccess and save permalinks, deactivate all plugins (rename the plugins folder), clear any cache, switch to a default theme, and raise the PHP memory limit. If none of that works, ask your host to check server logs.

How to fix a 500 internal server error

1. Check the error log

Your hosting panel’s error log, or WordPress debug logging (define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false);), often names the exact file and line. Turn debugging off afterwards.

2. Reset .htaccess

Rename .htaccess to .htaccess-old. If the site loads, go to Settings > Permalinks and save to create a clean one.

3. Disable plugins and cache

Rename wp-content/plugins to plugins-off. If the site works, rename it back and activate plugins one by one. Caching plugins, like WP-Cache in my case, are common culprits; clear their cache folders too.

4. Switch the theme

Rename your active theme’s folder so WordPress falls back to a default theme.

5. Increase PHP memory

See how to fix the allowed memory size exhausted error.

6. Re-upload core files

Replace wp-admin and wp-includes with fresh copies of the same WordPress version.

7. Contact your host

Server misconfigurations, PHP version changes or resource limits may need the host’s help. Send them the time of the error and what you’ve tried.

Related errors

WordPress’s own debugging guide (external site, opens in new tab) explains the debug settings in detail.

FAQ

Does a 500 error hurt SEO?

A short outage won’t, but errors lasting days can cause pages to drop from Google.

Why does the error appear only in wp-admin?

Usually a plugin or memory limit affecting admin pages.

Can a cache plugin cause a 500 error?

Yes, corrupted cache files or bad rules can; clear the cache or disable the plugin.

Found this useful? Share it with someone who needs it.

Subscribe to our weekly tech newsletter

New tech guides, free tools and 2-minute fixes, once a week.

🎁 100 Tech Terms ebook comes free with every subscription.

Unsubscribe anytime. See our privacy policy.

Related Tech Guides

Leave a Reply

Your email address will not be published. Required fields are marked *

17 Comments

  1. Because I am unable to get into my admin area, I cannot disable the stupid cache and even though I have deleted all cached files and the wp_cache_mutex.lock over and over again…everytime I try to view my page, the wp_cache_mutex.lock file reappears in the file manager!!!

    Does anyone know how to get rid of it?

  2. I can’t even get to my admin panel to do any of this. I can only get to the file manager.

    Yahoo tech won’t help – it isn’t their product.

    What can I do?

  3. I even can;t access the wp dashboard. Then I delete wp_cache_mutex.lock at wp-content/cache. And it works perfectly, thx

  4. Beetlejuice – that is a different problem… blank pages is a totally different issue.

    This is a new problem which has cropped up with Dreamhost (and maybe others)… and hard to believe but no solutions can be found.

    This error will cause your entire blog to be down and usually will spit out ugly error messages on your home page that look something like…

    blah blah wp-cache-phase2.php on line 96

  5. Dreamhost have a fix for this problem in their Help pages:

    1. Open /wp-content/plugins/wp-cache/wp-cache-phase2.php file* in your favourite text editor, where is the domain that you’re having troubles with EG: dreamhost.com/wp-content/plugins/wp-cache/wp-cache-phase2.php
    2. Alternatively if that file is not in that location for some reason you can issue this command to find it from the directory: find . -name wp-cache-phase2.php
    3. Locate the wp_cache_ob_end function
    4. then inside that function find the line with: ob_end_clean(); (it should be line 219 or about)
    5. and finally replace that line with: ob_end_flush();

    http://wiki.dreamhost.com/WordPress#Blank_Pages

  6. if your new host is godaddy then there is no fix currently because its a problem with the host.

  7. funny i was having the same problem too with the mutex lock, i changed host was succesful to migrate everything. but when i enable wp-cahe im having the mutex lock error. has any one found a solution for this?

  8. I have just installed WP-Cache and was happy to finally get it working. Right after i started getting 500 errors. So i knew something was up. After doing some research i found out that all people with godaddy.com have this problem and can not fix it. I tried deleting the wp_cache_mutex.lock file and all that but the problem just wont go away.

    So far I’m told there is no solution. But nice post i found it on google. just thought i would leave that godaddy.com has a problem as well.

  9. I think this only happens on WordPress hosted on DreamHost. I’m using DreamHost too and faced this problem since long ago. It’s due to wp-cache. Yesterday it occur again, and after experimenting, the problem is gone.

    I think DreamHost realize this problem as many DreamHost users sent them the problem. But they just don’t bother to do something.

  10. I encountered this problem today. Luckily i remembered about this post.

    Deleting the cache files and the wp_cache_mutex.lock file solved the problem.

    Thanks. :D

  11. Contact your server administrator or your web hosting company and they will fix it for you

  12. I deleted the wp_cache_mutex.lock which was found in Cache folder. But it still does not work. Instant internal server errors. What does this wp_cache_mutex.lock file do? I see it is edited out by comments in wp-cache-phase2.php

  13. I am getting this problem, too. For some reason, I just need to delete the wp_cache_mutex.lock and the site is back on track.

    I wish it never happens anymore… But I do know how… =/

  14. @Sweta
    I am no expert in web servers as I have clearly mentioned in this post. I am just another wordpress blogger like most others.

    This post just shows my attempt to fiddle with my wordpress settings (when the site was down so long and webhosting support could not fix the issue). I tried disabling WP-cache and the errors were gone and blog went online instantly. I tried this out and it worked for me. :-)

    Thanks for pointing out that link. I am sure the readers will learn more ways to fix such errors.

  15. Error 500 is generated by webserver. I have not 1 but 15 blogs running using wp-cache and wordpress 2.5. Ask your service provider to fix this or move to other good service provider.

    Just search using google “http error 500 php”

    https://www.google.com/search?q=http+error+500+php&gws_rd=ssl

  16. Are u sure u fixed the problem, i just got a internal server 500 error. I think u haven’t learnt ur lesson properly. :D