Trusted WordPress tutorials, when you need them most.
Beginner’s Guide to WordPress
WPB Cup
25 Million+
Websites using our plugins
16+
Years of WordPress experience
3000+
WordPress tutorials
by experts

How to Fix the 500 Internal Server Error in WordPress

Editorial Note: We earn a commission from partner links on WPBeginner. Commissions do not affect our editors' opinions or evaluations. Learn more about Editorial Process.

Are you seeing a 500 internal server error in WordPress?

The internal server error is one of the most common WordPress errors.

It is a bit tricky because 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 the 500 internal server error in WordPress.

Fixing the internal server error in WordPress

Here is a quick overview of the topics we will cover in this article:

What Is the 500 Internal Server Error?

The 500 internal server error is a common web server error. It is not specific to WordPress and can happen with any website.

The 500 in the error message is technically an HTTP error code. Looking up this code will only show its standard description:

500 Internal Server Error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

This is a generic catch-all error message, which means that the server was unable to assign a better, more helpful error message when it encountered the issue.

The error page looks different depending on which web server software (Nginx or Apache) your website uses and which browser you use.

Here is how the Apache error page may look:

Internal server error page on Apache

It may look different if you are using Nginx and Google Chrome.

It will also look different if Google Chrome is unable to find an error page to display:

Google Chrome http 500 error

For beginners, this can be incredibly frustrating. No clue or message will point them in the right direction to quickly fix it.

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

However, if you know the common causes that trigger this error, then you can try fixing them one by one to resolve the error without breaking anything.

What Causes the Internal Server Error in WordPress?

Internal server error in WordPress is often caused by a corrupt .htaccess file, poorly coded plugins, or your active WordPress theme.

Other possible causes of the internal server error in WordPress are PHP memory limit or corrupt core WordPress files.

In some conditions, the internal server error may only show up when you are trying to access the WordPress admin area while the rest of the site works fine.

Usually, the error is triggered before WordPress can load and the server cannot get enough information about what stopped it.

To understand more, see our article on how WordPress works behind the scenes.

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 prefer written instructions, then just continue reading.

Fixing the 500 Internal Server Error in WordPress

Before you begin troubleshooting, make sure that you have a complete WordPress backup of your website on hand.

If you have access to the WordPress admin area, then you can use a WordPress backup plugin to create a complete backup of your website.

We recommend using Duplicator to handle this. It not only helps you quickly back up your website, but you can also store your backups on the cloud, and most importantly, you can restore your website from backup.

On the other hand, if you don’t have access to the WordPress admin area, then you can manually create a WordPress backup using phpMyAdmin and an FTP client.

After that, you can follow the following steps to troubleshoot and fix the internal server error on your website.

Clear WordPress and Browser Cache

Browsers and your WordPress caching plugins can sometimes mistakenly store a cached copy of an error page.

The easiest way to fix this is by first clearing your browser cache.

Clear cache

After that, if you have access to the WordPress admin area of your website, then you can empty the WordPress cache by visiting your caching plugin’s settings page.

For details, see our tutorial on how to clear WordPress cache.

Checking for Corrupt .htaccess File

The .htaccess file is a server configuration file that is also used by WordPress to set up redirects.

One of the most common causes of the internal server error is the corrupt .htaccess file.

The easiest way to fix this is by simply visiting the Settings » Permalinks page in the WordPress admin area and then clicking on the ‘Save Changes’ button without making any changes at all.

Update permalinks to regenerate .htaccess file

WordPress will now try to update your .htaccess file or generate a new one for you. You can now visit your website to see if this has resolved the internal server error.

If you can still see the error, then you need to make sure that WordPress was able to generate or write to the .htaccess file.

Sometimes, due to file and directory permissions, WordPress may not be able to create or write to your .htaccess file.

You can now try to replace the .htaccess file manually. First, you need to log in to your website using FTP or the File Manager app under your hosting account control panel.

Next, you need to rename your main .htaccess file to something like .htaccess_old. This lets you keep the file as a backup, but WordPress won’t recognize it.

To rename the .htaccess file, you will need to log in to your site using FTP or the File Manager app in your hosting account’s cPanel dashboard.

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

Simply right-click on the .htaccess file and rename it to .htaccess_old.

Rename .htaccess file

Next, you need to create a new .htaccess file.

Inside your site’s root folder, right-click and then select the ‘Create new file’ option in your FTP client or File Manager app.

Create new htaccess file

Name this new file .htaccess and click ‘OK’ to save it.

Now, this .htaccess file is currently empty, and you need to add default WordPress rewrite rules to it.

Simply right-click on the file and then select ‘View/Edit’ in your FTP client or File Manager app.

Edit .htaccess file

The empty file will open in a plain text editor like Notepad or TextEdit.

Now, you need to copy and paste the following code inside it:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

This code is the default rule set used by WordPress. Don’t forget to save your changes and upload the file back to the server.

You can now visit your website to see if this has resolved the internal server error.

If it did, then give yourself a pat on the back because you fixed the internal server error.

Important: Before you move on with other things, make sure that you go to the Settings » Permalinks page in the WordPress admin area and click the Save button without making any changes. This will regenerate the .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, the internal server error can happen if a script consumes all the PHP memory limit.

The easiest way to increase the PHP memory limit is by editing the wp-config.php file. Be careful when you do this if you are a beginner. You want to follow these instructions carefully because even small mistakes in WordPress core files can break your site.

To begin, simply connect to your WordPress website using an FTP client or the File Manager app under your hosting account control panel.

You’ll find the wp-config.php file inside the main folder of your website. Right-click on it and select ‘Download.’ This will ensure that you have a file backup in case something goes wrong.

When you’ve saved that, you can right-click on it and select ‘View/Edit.’

Edit wp-config file

Inside the wp-config.php file, you need to add the following code just above the line that reads, ‘That’s all, stop editing! Happy publishing’:

define( 'WP_MEMORY_LIMIT', '256M' );

For more details, see our tutorial on how to increase the PHP memory limit in WordPress.

Note: If 256M doesn’t solve the problem, then try increasing it to 512M.

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

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

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, you are in for more troubleshooting.

Deactivate All WordPress Plugins

If none of the above solutions worked for you, then this error is most likely being caused by a specific plugin installed on your website.

It is also possible that it is a combination of plugins that are not playing nice with each other.

If you can access the WordPress admin area of your website, then you can simply go to the plugins page and deactivate all WordPress plugins.

Deactivate all plugins

However, if you are unable to access the WordPress admin area, then you can deactivate all WordPress plugins using FTP.

Simply connect to your WordPress website using an FTP client or the file manager app under your hosting account control panel.

Once connected, navigate to the /wp-content/ folder and rename the plugins folder to plugins.deactivated.

Plugins deactivated via FTP

WordPress looks for plugins in the plugins folder. If the plugins folder is not found, it will automatically deactivate all plugins.

You can now try visiting your website to see if this resolved the internal server error on your website.

To restore all your plugins, you can simply rename the ‘plugins.deactivated’ folder back to plugins.

Your plugins will now be restored, but they will still be deactivated.

You can now activate plugins individually and visit your website to figure out which plugin is causing the internal server error.

For more details, see our guide on how to deactivate all WordPress plugins without WP-Admin.

If deactivating all plugins didn’t fix the internal server error on your website, then continue reading.

Switch to a Default WordPress Theme

One possible cause of the internal server error could be some code in your WordPress theme.

To determine if this is the case, you need to switch your theme to a default WordPress theme.

If you have access to the WordPress admin area, then go to the Appearance » Themes page. If you have a default theme already installed, then you can simply click on the Activate button to switch the theme.

Activate a default theme

If you don’t have a default theme installed, you can click on the ‘Add New’ button at the top and install a default theme (Twenty Twenty-Three, Twenty Twenty-Two, and so on).

If you don’t have access to the WordPress admin area, you can still switch to a default theme.

Simply connect to your WordPress website using an FTP client and navigate to the /wp-content/ folder.

Right-click to select the themes folder and download it to your computer as a backup.

Download theme folder

Next, you need to delete the themes folder from your website. Once it is deleted, go ahead and create a new themes folder.

Your new themes folder will be completely empty, which means you don’t have any WordPress themes installed at the moment.

Next, you need to visit the WordPress themes directory and download a default WordPress theme to your computer.

Download a default theme

Your browser will then download the theme as a zip file to your computer.

Locate the file on your computer and then unzip it. Windows users can unzip the file by right-clicking on it and then selecting ‘Extract All’. Mac users can double-click on the zip file to extract it.

Extract theme files

You’ll now see a folder containing your WordPress theme.

Switch back to your FTP client or File Manager up and upload this folder to the empty themes folder.

Upload theme folder

Once uploaded, WordPress will automatically start using the default theme.

You can now visit your website to see if this resolved the internal server error.

If this doesn’t work, then you can reupload your WordPress themes from the backup or switch back to the theme you were using.

Don’t worry. There are still a few more things you can do to fix the error.

Re-Uploading Core Files

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

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

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

Download WordPress

This will download the WordPress zip file to your computer.

Go ahead and extract the zip file. Inside it, you will find a wordpress folder.

WordPress folder extracted

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 the wp-admin, wp-includes, and wp-content folders inside it.

In the left column, open the WordPress folder on your computer.

Now you need to select all files inside the wordpress folder and upload them to your website.

Upload core WordPress files

Your FTP client will now transfer those folders to your server.

It will ask you whether you would like to overwrite the files. Select ‘Overwrite’, then select ‘Always use this action’ and check the ‘Apply to current queue only’ checkbox.

Overwrite WordPress core files

Your FTP client will now replace your older WordPress files with new, fresh copies.

If your WordPress files were corrupted, then this step will fix the internal server error for you.

Enable Debug Logs in WordPress

WordPress comes with a built-in system to keep logs for debugging.

You can turn it on by using the WP Debugging plugin. For more details, see our guide on how to install a WordPress plugin.

Once activated, the plugin will turn on debugging logs on your WordPress website.

If you don’t have access to the admin area of your WordPress website, then you can turn on debugging by adding the following code to your wp-config.php file:

define( 'WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true); 

Once you have turned on debug logs, you can view these logs by using an FTP client and navigating to the /wp-content/ folder.

Debug log

You can open the debug log file in a text editor, and it will show you a list of errors and warnings that occur on your website.

Some errors and warnings can be harmless incidents that may not need fixing. However, if you are seeing an internal server error on your website, then these may point you in the right direction.

Ask Your Hosting Provider

If all methods fail to fix the 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 our guide on how to choose the best web hosting provider.

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. Here's our editorial process.

Editorial Staff

Editorial Staff at WPBeginner is a team of WordPress experts led by Syed Balkhi with over 16 years of experience in WordPress, Web Hosting, eCommerce, SEO, and Marketing. Started in 2009, WPBeginner is now the largest free WordPress resource site in the industry and is often referred to as the Wikipedia for WordPress.

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

677 CommentsLeave a Reply

  1. Syed Balkhi says

    Hey WPBeginner readers,
    Did you know you can win exciting prizes by commenting on WPBeginner?
    Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
    You can get more details about the contest from here.
    Start sharing your thoughts below to stand a chance to win!

  2. Shashank Priyadarshi says

    I am facing the same issue. Internal Server Error (HTTP 500 Internal Server Error) in my site. I tried following the steps, but i think i am missing something. I am not very good with servers and such. Please help…

    • WPBeginner Support says

      If none of the recommendations from our guide are able to help you solve the error, please reach out to your hosting provider and they should be able to assist!

      Admin

    • Jiří Vaněk says

      Renaming the htaccess file first helps me when looking for a problem. This will rule out a problem in this file. Then I try to rename the folder with plugins. If none of this helps, try asking the web provider. Usually, it can also be a specific php or server setting.

  3. Jiří Vaněk says

    As for the 500 error, in practice it has proven to be the fastest method to contact my provider and ask him for a printout of the error log. Very often, a problem appears there, which may be due to an unauthorized directive in the .htaccess file, or in the rights on the WordPress folder. with Error 500, it is probably best to really look at the logs right from the start. It can solve many problems very quickly.

  4. Uzair says

    Encountering the 500 Internal Server Error in WordPress has been a recurring challenge for me on client websites. I’ve found that the causes are often multifaceted, influenced by various factors such as the hosting provider and the specific WordPress environment, including the plugins and themes in use. Your article shed light on this complexity, and I appreciate it.

  5. A Owadud Bhuiyan says

    Thanks for sharing.

    Sometimes I actually do the permalink-saving thing. But I never knew the details about it.

    Now it’s very clear to me.

  6. Arielle says

    OMG you are a lifesaver!!! Simply uploading and replacing the WP admin and include file worked like magic!! THANK YOU !!!

  7. Taimoor Khan says

    The main cause of this problem is because of the Plugins updation. I faced that problem and can’t even access the Dashboard. So what I did for that is to log in to my hosting and update all my plugins which will help me in getting rid of that problem.

    • WPBeginner Support says

      Thank you for sharing what worked for you! It is not always the plugins but that can certainly be one of the causes.

      Admin

  8. David Cao says

    My .htaccess file was corrupted, thank goodness I found this article. Thank you very much!

  9. Gultekin irengun says

    I was looking for a fix and neither reallt worked for me to fic 500 errors for the pages of a site in multisite when I recently changed the domain name.

    What fixed it was, changing permalinks to plain. So I guess, re-doing permalinks was the easiest fix.

    • WPBeginner Support says

      Thanks for sharing what worked for you, with the pretty permalinks not working, you may want to check with your hosting provider that mod_rewrite is enabled for your sites.

      Admin

  10. Bianca says

    Thanks for this article. Just want to add an extra tip:
    Also check for additional .htaccess files in other folders like for example the ‘uploads’ folder. This may cause a partial 500 internal server error for images and everything that is in that folder. I experienced this recently and was caused by a rigid setting in a security plugin.

    • Kate says

      Thank you for sharing that tip! After going through all the steps in the post and still getting the error on my images, I found an extra .htaccess file that was causing the problem. I’m so glad I decided to read these comments.

  11. Mr Terry McBride says

    A most excellent tutorial, watched to keep me on the ball so to speak, but
    one issue that you missed, and I recently had, was a corrupted wp-config.php file – that was also causing me 500 errors.

    I urge everyone to copy this particular fie to their own machine for safe keeping, My own hosting provider (though brilliant), couldn’t hep me.

    Simply copying my own backup via FTP to my /public_html folder – saw my own site miraculously appear again.

    Hope it helped.

  12. Ramon Olivencia says

    In my case, I was getting an “HTTP ERROR 500” and an “Internal Server Error”, particularly at my WooCommerce checkout. GoDaddy fixed the issue after looking at the error log and increasing the memory limit by inserting a .user.ini file and then adding “define (‘WP_MEMORY_LIMIT’, ‘2048M’ );” to my wp-config.php file.

  13. American says

    I have tried all these methods, the error goes away by re-installing wordpress or refreshing core files but it appears again and again when I try to update any plugin or perform any task in the dashboard.

    Please advice, what could be the possible reason that it is keep happening with me.

    • WPBeginner Support says

      For that continued issue, please reach out to your hosting provider and they should be able to assist.

      Admin

  14. Connor says

    The issue for me was Wordfence security plugin installs an htaccess file in the wp-content/uploads file. Delete this an the internal error disappears! I hope this will help somebody :)

    • WPBeginner Support says

      We would recommend reaching out to Elementor’s support if you are having an issue with Elementor.

      Admin

  15. Chan says

    Thank you so much. I
    ‘m an experience web developer but new to WordPress.
    Had a 500 error, found this guide and followed it and my problem was solved.

  16. Emel says

    Hello there!
    Error code 500 appears when I click on the browser. The page never opens up since I updated the theme!
    I cannot even open my website to update it according to your instruction here. What to do in that case? Thanks in advance!

  17. mohamad says

    Hi. Thankful.
    for Error 500.
    My problem was after updating the template.
    The problem was solved by updating php version.

  18. lanre says

    Hello. I’m having the same problem on my site and it’s hosted on gcp. I tried installing some plugins before I got this error. Is there a way I can remove the plugin from mysql database or do I need to do it through the htaccess file. This blog is true great as it has helped me with most of my site issues. Hope this works also

      • lanre says

        thank you very much. it worked like magic. the thing now is should I delete the old .htaccess file or rename it back? Thanks once again

        • WPBeginner Support says

          You can get rid of the old file if that was giving you errors and resaving your permalinks should create a new file for you.

  19. Sophie says

    You save me every time! Renaming the .htaccess file and saving the page permalinks worked for me, the problem occurred after I updated all my plugins and cleared my cache. Thanks a lot!

  20. Esther Mitchell says

    Hi,
    I followed your guidance and need to undo the .htaccess change. Should I delete the new .htaccess and thereafter rename the old .htaccess_old to its original name .htaccess to do so? Hope you see this note soon and can help. :)

  21. Erica says

    Well, this is nice information! Thanks for sharing this as it would help many users to know about important information about WordPress. Knowing about this, we are looking forward to implementing things accordingly.

  22. Caitlin says

    Similar issue my website disappeared while undergoing a major update from a commerce platform plugin. Coming from no experience with these things, this solution was easy to follow even from a different file manager.

    Thank you.

  23. Sonam Jain says

    Your blog was very helpful. I had to upload the core files and the steps given by you made it very easy for me. Thank you.

  24. Luiz Verçosa says

    In my case, the problem was that my PHP version was automatically updated by my host and my old WordPress version was incompatible with it. They themselves found the problem and fixed it after my contact through e-mail.

    • WPBeginner Support says

      Thanks for sharing the issue you ran into and how it was fixed for others running into this problem :)

      Admin

  25. Stephan says

    Hi, thank you very much for your help. You solve my problem. (broken plugin)

    Best regards from Germany,
    Stephan

  26. Rene Con says

    My site is on HTTP Error 500, I did all the steps to fix the issue, is not working at all yet :(

    • WPBeginner Support says

      If you reached out to your hosting provider they should be able to give you a better idea of the source of the issue.

      Admin

  27. Saif Fuad says

    Thank you very much, one of the WP plugin was causing the error, i deactivated it made new installation of that specific plugin and it worked.

    Thanks

  28. Jaine says

    You save my site. Can’t thank you enough. Your instructions were clear and easy to follow. You’re amazing!

  29. Ajay vaja says

    wp-includes/post.php File are missing my site and admin panel are not opening

    Error Message :- The site is experiencing technical difficulties

Leave a Reply to Siddharth Cancel 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.