Beginner's Guide for WordPress / Start your WordPress Blog in minutes

How to Fix the 500 Internal Server Error in WordPress

Are you seeing 500 internal server error in WordPress? Internal server error is one of the most common WordPress errors. Since the error doesn’t give any other information, many beginners find it quite frustrating. In this article, we will show you how to easily fix internal server error in WordPress.

How to fix internal server error in WordPress

What Causes Internal Server Error in WordPress?

Internal server error is not specific to WordPress. It can happen with any website running on a web server. Due to the generic nature of this error, it does not tell the developer anything.

Asking how to fix an internal server error is like asking your doctor how to fix the pain without telling them where the pain is.

Example of a WordPress website showing internal server error

Internal server error in WordPress is often caused by plugin or theme functions. Other possible causes of internal server error in WordPress that we know of are: corrupted .htaccess file and PHP memory limit.

We have also heard internal server error only showing up when you are trying to access the admin area while the rest of the site works fine.

That being said, now let’s take a look at how to go about troubleshooting the internal server error in WordPress.

Video Tutorial

Subscribe to WPBeginner

If you don’t like the video or need more instructions, then continue reading.

Checking for Corrupt .htaccess File

The first thing you should do when troubleshooting the internal server error in WordPress is check for the corrupted .htaccess file.

You can do so by renaming your main .htaccess file to something like .htaccess_old. To rename the .htaccess file, you will need to login to your site using FTP or File Manager app in your hosting account’s cPanel dashboard.

Once you connected, the .htaccess file will be located in the same directory where you will see folders like wp-content, wp-admin, and wp-includes.

Editing .htaccess file in WordPress

Once you have renamed the .htaccess file, try visiting your site to see if this solved the problem. If it did, then give yourself a pat on the back because you fixed the internal server error.

Before you move on with other things, make sure that you go to Settings » Permalinks page in WordPress admin area and click the save button without making any changes. This will generate a new .htaccess file for you with proper rewrite rules to ensure that your post pages do not return a 404 error.

If checking for the corrupt .htaccess file solution did not work for you, then you need to continue reading this article.

Increasing the PHP Memory Limit

Sometimes internal server error can happen if you are exhausting your PHP memory limit. Use our tutorial on how to increase PHP memory limit in WordPress to fix that.

If you are seeing the internal server error only when you try to login to your WordPress admin or uploading an image in your wp-admin, then you should increase the memory limit by following these steps:

  1. Create a blank text file called php.ini
  2. Paste this code in there: memory=64MB
  3. Save the file
  4. Upload it into your /wp-admin/ folder using FTP

Several users have said that doing the above fixed the admin side problem for them.

If increasing the memory limit fixed the problem for you, then you have only fixed the problem temporarily. You still need to find the cause that is exhausting your memory limit.

This could be a poorly coded plugin or even a theme function. We strongly recommend that you ask your WordPress web hosting company to look into the server logs to help you find the exact diagnostics.

If increasing the PHP memory limit did not fix the issue for you, then you are in for some more troubleshooting.

Deactivate all Plugins

If none of the above solutions worked for you, then this error is most likely being caused by a specific plugin. It is also possible that it is a combination of plugins that are not playing nice with each other.

Sadly, there is no easy way to find this out. You have to deactivate all WordPress plugins at once.

Follow the instructions in our guide on how to deactivate all WordPress plugins without WP-Admin.

Deactivate all WordPress plugins

If disabling all plugins fixed the error, then you know it is one of the plugins that is causing the error.

Simply go to the WordPress admin area and click on ‘Plugins’. Now you need to reactivate one plugin at a time until you find the one that caused the issue. Get rid of that plugin, and report the error to the plugin author.

Re-uploading Core Files

If the plugin option didn’t fix the internal server error, then it is worth re-uploading the wp-admin and wp-includes folder from a fresh WordPress install.

This will NOT remove any of your information, but it may solve the problem in case any file was corrupted.

First you will need to visit the WordPress.org website and click on the Download button.

Download WordPress

This will install WordPress zip file to your computer. You need to extract the zip file and inside it you will find a wordpress folder.

Next you need to connect to your WordPress website using an FTP client. Once connected go to the root folder of your website. It is the folder that has wp-admin, wp-includes, wp-content folders inside it.

In the left column open the WordPress folder on your computer. Now you need to select wp-includes and wp-admin folders and then right-click and select ‘Upload’.

Upload fresh WordPress files

Your FTP client will now transfer those folder to your server. It will ask you whether you would like to overwrite the files. Select ‘Overwrite’ and then select ‘Always use this action’.

Overwrite files

Your FTP client will now replace your older WordPress files with newer fresh copies. If your WordPress files were corrupted, then this step will fix the internal server error for you.

Ask your Hosting Provider

If all methods fail to fix internal server error on your website, then it is time to get some more help. Contact your web hosting support team and they will be able to check the server logs and locate the root cause of the error.

If you want to continue troubleshooting on your own, then see our ultimate WordPress troubleshooting guide for beginners.

We hope this article helped you fix the internal server error in WordPress. You may also want to see our complete list of the most common WordPress errors and how to fix them.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

Disclosure: Our content is reader-supported. This means if you click on some of our links, then we may earn a commission. See how WPBeginner is funded, why it matters, and how you can support us.

The Ultimate WordPress Toolkit

Get FREE access to our toolkit – a collection of WordPress related products and resources that every professional should have!

Reader Interactions

655 CommentsLeave a Reply

  1. My DigiWeb Advanced Hosting Package and 500 server error on activation attempt…

    In my case as a beginner and attempting to add a WooWoo theme and then WooWoo eCommerce plugin I had a 500 server error..
    The first time after the Theme was installed was rectified by the staff at hosting support.. They pointed out that a web.config file was created, that they renamed it to web.config_old and I was not to create any more.. Proceeding to add the eCommerce plugin and attempting to activate.. 500 error again.. but this time I looked in the directory and there was another ‘web.config’ file.. I changed the name and bingo, all was Ok.. I was happy for I don’t want to be hanging out of the apron of the tech guys at DigiWeb !

    I do hope this helps even one person…

  2. Since i set up my account for both wordpress and Cpanel, i discovered that my domain name on cpanel was not spelt correctly(probably my error) but i have been trying to change it but could not. i need to know the implication of this and how to correct it.my site has been running fine until recently,could it be the cause.

  3. I encountered this internal error (500) error when i added this line to my .htaccess
    max_input_vars = 1540; but as soon as I remove it , it works. I need to increase my Max_Input_vars from 1000
    Please help.

    • Just additional info. Godaddy asked me to create and use .user.ini to add this, but phpinfo still shows it at 1000 after the change. Its why I decided to use the .htaccess but that send my site to an internal error 500 status.

  4. Haylo!

    I had this issue today and I figured out the problem was with my file/folder permissions.

    I had tried setting all my folders, sub-folder, and file permissions to 777 because I was having major issues uploading images.

    This caused the internal server error for me. Switching everything back to 755 fixed it for me, though I’m assuming that simply applying 755 onto the wp-admin folder would have done the job!

    Hope that helps someone!

  5. Hi i’m facing different type of problem. When i try to load my website it shows ”The mydomain.com page isn’t working” and “mydomain.com is currently unable to handle this request” also “HTTP ERROR 500” (in small font).
    Even i’m not able to login in wp admin panel too. what to do? Please help.
    I changed the .htaccess file also i thought, may be its happened because of broken config.php file, so i delete it. And when i load my website its start showing the setup configuration setting.
    i setp up again, but when its come to login part, same thing happened.
    Please help!

      • I kept getting a 500 error ‘ [website] is currently unable to handle this request’. After reading through the 500 error advice, I found that a revision I had made to page.php in my theme directory was calling up a print command for a deactivated plugin. I removed the command line and the issue was immediately resolved! Now everything is coming up roses….I mean pages!

  6. Mine was none of the above. But I saw in my error logs that wordfence-waf.php had a error in the paths. Renaming wordfence-waf.php in the root folder fixed the issue.

    • You just hit the nail on the head.

      When I had the problem with my site, I first went ahead to check the log.

      My hosting support only gave the best they could but I had an opportune moment to solve the problem by myself.

    • I appreciate the management for the good work, more power to your elbow.

      I experienced this error when I was customizing my theme.

      The error log gave a clue.

      My hosting support only gave the best they could but I had an opportune moment to solve the problem by myself.

  7. you can solve the problem by updating the wordpress to the latest version by transferring the “core” files, but before disable all plugins renaming the folder “plugins”

  8. We were getting an “Internal Server 500” error when going to the WP Admin page.

    In our case, it was the .htaccess file being corrupt.

    Note, though, that deleting .htaccess did NOT fix the problem — in fact, deleting it caused the index page to then have a PHP error, when it had been working fine before. (And that was due to a WP Super Cache error, it seemed — it wasn’t finding the file it was looking for.)

    We had ¦ in place of #, and ¤ in place of $ in our .htaccess, for some reason. Fixing those fixed the WP Admin login problem.

    Hope it helps someone.

  9. I found an interesting reason for an internal server error after checking my host logs- my wordpress install had group writeable permissions. I had forgotten that I went crazy on my permissions when trying to solve an issue that was being caused by the host. When I changed the CHMOD setting to 755, it was working again. my admin folder is not in the root folder, I wonder if this is why I could still see the website and not be able to access the admin.

  10. Hi,
    as per your suggestion in this post I tried to Re-uploading Core Files(WP-ADMIN & WP-INCLUDES) to fix the 500 error in my website. But now, I am getting again the 500 error and when I contacted my Hosting provider(Hostgator) they send me this log (We have checked and we found there is issue with “akismet”. Please find the log below.

    [26-May-2016 04:19:04 UTC] PHP Fatal error: Class ‘WP_Widget’ not found in /home/makei3v5/public_html/example.com/wp-content/plugins/akismet/class.akismet-widget.php on line 5) , Now I am helpless, what should I do? I have done the step accurately as per the above guidance.

    Please help me out.
    Thanks, Riyaz

  11. Thanks for your guideline…I have deactivated all the plugins, but it still shows the same error.

    Then I deactivate my theme and it works fine. I realized that theme can create this type of error.

  12. Hello,

    What if this problems appears randomly?
    Sometimes when I open my website main page, some times when I bulk edit posts. It’s just happens randomly as far as I know, could the problem be that the hosting servers are loaded? because I’m using shared web hosting, I would like to know that if you could answer me?

    I don’t want to migrate to another host if the problem is some plug-in in my site.
    Please answer me.

    Thanks.

    • I would like to know this as well. I have the same issue. It happens sometimes, sometimes not. It can be from the admin panel or from viewing the site directly. I’m also using a very cheap shared hosting service and am wondering if it’s possible this is coming from “their end”.

  13. This article was a true life saver! Or a mental health saver, at least. Turns out a plugin was messing everything up, and thanks to this article I’ve been able to solve it. So many thanks from a relieved WP-beginner (since 2014…)!

  14. Hi, but my problem is that I cannot enter even to the dashboard, when I try also says internal sever error, so I cannot do nothing. Doesn’t work nothing. I am in panic.

  15. After reading the above mentioned solutions, I went to wp-content/plugins through ftp and sorted the plugins list as last modified and deleted the most recent modified plugin. Problem solved for me.
    Thanks

  16. In case you are not on a linux server and your hosting is done on IIS (Microsoft Platform) instead, you may have corrupted the web.config file which is used instead of an .htaccess file.

    Most servers I use are linux, so I just ran into this problem today on a Microsoft Server. FTP into your site and fix your web.config file.

    T.

    • If you’re hosting WordPress on a IIS (Microsoft Platform) instead of a linux server and have problems updating your WordPress, you need to install this plugin “WP Maximum Execution Time Exceeded’

      However the default execution time of the above plugin is 300 ms which you need to increase to 500 or 600 ms to make it work.

  17. The issues started right after adding this to my function.php file in my child theme:

    /*** Remove Query String from Static Resources ***/
    function remove_cssjs_ver( $src ) {
    if( strpos( $src, ‘?ver=’ ) )
    $src = remove_query_arg( ‘ver’, $src );
    return $src;
    }
    add_filter( ‘style_loader_src’, ‘remove_cssjs_ver’, 10, 2 );
    add_filter( ‘script_loader_src’, ‘remove_cssjs_ver’, 10, 2 );

  18. Thank you very much, you saved me from re installing my site

    changing the PLUGINS was the solution and i re installed the faulty plugin

    wish you all the best

    Yasser

  19. I was getting the 500 Internal Server error when trying to access the ‘Customize’ Menu (button located at the top when viewing your site). It turned out to be a plugin…

    The .htacces and php.ini methods didn’t work, in my case, uploading the php.ini file made me unable to access wp-admin until php.ini was deleted.

    I apologize I can’t give the name of the faulty plugin, I was in a hurry at the time and needed it to work asap…It was a plugin that added widgets to the SiteOrigin PageBuilder plugin.

  20. Hello guys,

    I could access to my wordpress admin panel again deactivating all my plugins from database,

    Then I was receiving a problem with an specific pluging, I recommend you to check what pluging is causing issues, in my case was woocommerce and my theme, both installed I was getting an error message about Memory Exceeded, I didn’t find a solution for this error, now I had to separate my page in two wordpress installation, one with all information, and the other with the virtual store,

    If anyone find raise of Fatal error: memory exceeded, please let a comment, Thaks for your support guys.

    Bye

  21. Hallo,
    many thanks for that tutorial and all the comments here.
    As my hosting is also with Strato I tried the recommandation from Karo A – and it works.
    After disabling the cache of PHP Boost at Strato no more Internal Server Error 500 occured.
    Might be this cache is running out of memory as I use also Slimstat statistics.
    Karo

  22. Hi,
    on Strato Websites with PHP 7.0 Power Boost on,wordpress with eg. Jetpack I ve got the 500 server error message.
    After checking the Server error log at Strato I found an error message in the log that the PHP handler (CGI) aborted.

    After changing the PHP handler (CGI) in the Strato Interface to PHP 7 WITHOUT Power Boost everything works fine!
    Best regards
    Karo

  23. Thanks for this, nothing worked but it at least gave me ideas to troubleshoot with. I renamed the theme in the same way to rename the plugins folder eg. themename_deactivate and it worked, I could login to my site again. Still troubleshooting why the theme is acting up all of a sudden.

  24. Hello, unfortunately my problem continues even after following all his steps.
    Would have any idea what could be?

  25. Everything tried but my problem not solved.
    I only get NetworkError: 500 Internal Server Error – when I try to login to my site. The browser goes to blank page and I get that error in console.

    Please help

  26. Thank you……… very much I’ve regenerate .htaccess file and now my site is working properly thanks again for your helpful solution.

  27. Great guide! Thank you guys. I just needed to resave my .htaccess file – unbelieveable but true.

  28. By update using InfiniteWP my site broke down. I tried all above without luck… But in my chase it was a Theme missing. I had to re upload the Mother Theme to get my site back;)

Leave A Reply

Thanks for choosing to leave a comment. Please keep in mind that all comments are moderated according to our comment policy, and your email address will NOT be published. Please Do NOT use keywords in the name field. Let's have a personal and meaningful conversation.