WordPress 500 Internal Server Error

WordPress 500 Internal Server Error

WordPress 500 Internal Server Error, is very common WordPress error. We’ll show you, How to fix, WordPress 500 Internal Server Error. WordPress is a content management system (CMS) used by millions of people because it is free, customizable and easy to use. Although there is documentation for pretty much everything, many people find it difficult to manage their own sites. This may lead to their sites being down which is something nobody likes. One of the most common problems that occurs with WordPress is 500 Internal Server Error. In this guide we will show you few tips on how to fix 500 Internal Server Error and get your WordPress site up and running on your Linux VPS. Fixing WordPress 500 Internal Server Error, is really an easy task, just follow the steps below carefully.

The first thing you need to do is to backup your WordPress site and MySQL database. No matter what is the root cause of the problem and how bad it is, it is always good to have a backup of the site. Once you create a backup of your WordPress site you can continue with the other steps.

1. Enable Debugging in WordPress

It is always good to start by debugging the problem. WordPress comes with specific debug systems designed to simplify the process. To enable debugging in WordPress, connect to your server via FTP/SFTP or SSH and edit the wp-config.php file. Add the following lines before the /* That’s all, stop editing! Happy blogging. */ line:

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

WP_DEBUG is a PHP constant which is used to trigger the debug mode in WordPress while WP_DEBUG_LOG causes all errors to be saved in a log file called debug.log.

Save the configuration file and repeat the failed WordPress operation that caused the WordPress 500 Internal Server Error. Check for the debug.log log file inside the /wp-content/ directory for PHP errors, notices and warnings and if there are any you can try to fix them.

Ideally, you will want to have the following code in your wp-config.php file:

 // Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );

2. Increase PHP Memory Limit in WordPress

One of the most common causes for the 500 Internal Server Error message is exhausting the PHP memory limit. This is usually set in the php.ini file. You can directly try to increase the memory_limit in php.ini and restart your Apache HTTP server / PHP-FPM service. The alternative is to add the following line in your wp-config.php file:

Need a fast and easy fix?
✔ Unlimited Managed Support
✔ Supports Your Software
✔ 2 CPU Cores
✔ 2 GB RAM
✔ 50 GB PCIe4 NVMe Disk
✔ 1854 GeekBench Score
✔ Unmetered Data Transfer

Now just $43 .99

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

In case your application requires more memory due to multiple active plugins and heavy theme, you can set up a higher value here.

3. Create New .htaccess File

The .htaccess file can easily get corrupted due to bad plugin or manual changes. Log in to your server via FTP/SFTP or SSH and rename the file to .htaccess.BAK or .htaccess.CORRUPTED and create a new .htaccess file with the basic .htaccess settings.

4. Deactivate the Plugins in WordPress

If none of the previous solutions worked, you can try deactivating all your plugins in WordPress. If you have access to the WordPress dashboard you can navigate to the Plugins section and deactivate each plugin one by one. After each deactivation you can refresh your site and check if the problem is solved.

If you are unable to access the WordPress dashboard you can deactivate the plugins via FTP/SFTP or SSH. Log in to your server, navigate to your wp-content and rename the plugins directory to plugins.DEACTIVATED. Alternatively, you can navigate to the plugins directory and deactivate each plugin one by one. Do not forget to enable the plugins once you are done by renaming the plugins.DEACTIVATED directory back to plugins

Hopefully, some of these solutions helped you to fix the 500 Internal Server Error. If you still experience 500 Internal Server Error, it is recommended to contact your web hosting provider.

WordPress 500 Internal Server Error

Of course, you don’t have to fix 500 Internal Server Error if you use one of our WordPress VPS Hosting services, in which case you can simply ask our expert Linux admins to help you fix the WordPress 500 Internal Server Error, on your server for you. They are available 24×7 and will take care of your request immediately.

PS. If you liked this post, on How to Fix WordPress 500 Internal Server Error please share it with your friends on the social networks using the buttons on the left or simply leave a reply below. Thanks.

3 thoughts on “WordPress 500 Internal Server Error”

  1. Though the 500 Internal server error is recoverable and it is easy to do, there are many people who do not actually know how to get rid of this type of WordPress error. For those, the post is really a big solution to fix this error.

  2. Hi,
    I have moved my wordpress site to a different VPS machine.
    I have a dev environment setup on subdomain eg. dev.mysite.com.
    mysite.com is working fine but the dev env. is showing white screen with no errors even wp-admin panel is showing white screen.
    on google chrom the dev.mysite is giving error http 500.
    not sure what I am missing.

    • Check this Article for possible solutions and make sure that the migration to the different VPS was successful. You can check our article about WordPress migration https://www.rosehosting.com/blog/migrate-your-wordpress-website-to-a-new-virtual-server


Leave a Comment