In this article, I’ll help you pinpoint the exact cause of the error on your WordPress site and guide you through fixing it.<\/p>\n\n\n
Common causes of the 500 internal server error<\/h2>\n\n\n\n
Basic definitions:<\/p>\n\n\n\n
- \n
- “HTTP” refers to the protocol used for communication between the client (your browser) and the web server.<\/li>\n\n\n\n
- “500” is the status code indicating an internal server error<\/em>.<\/li>\n<\/ul>\n\n\n\n
Therefore, the “HTTP 500 internal server error” as a whole indicates that something unexpected went wrong during the communication between the browser and the web server and that the problem originates from the server side. However, there’s probably nothing wrong with your server, so don’t worry. <\/p>\n\n\n\n
As for the real cause of the error, it could have occurred because of any of the following issues:<\/p>\n\n\n\n
- \n
- Poorly coded plugins or themes<\/strong> can cause conflicts with other plugins and themes, triggering the error;<\/li>\n\n\n\n
- PHP memory limit exhaustion<\/strong> causes resource-intensive operations to terminate prematurely;<\/li>\n\n\n\n
- Corrupted .htaccess<\/em> file,<\/strong> a core WordPress file, due to incorrect configurations or syntax errors can disrupt the server’s ability to process requests properly, leading to a 500 error;<\/li>\n\n\n\n
- Changed file permissions<\/strong> can cause the server to encounter issues accessing the necessary files or directories to fulfill a request, thus triggering the error;<\/li>\n\n\n\n
- On rare occasions, browser incompatibility<\/strong> can cause the website to open normally on one browser and to throw errors on another.<\/li>\n<\/ul>\n\n\n\n
Now that we have the common causes out of the way, let’s look at the best ways to get rid of this error:<\/p>\n\n\n
<\/div>\n\n\n\nHow to fix the 500 internal server error on your site<\/h2>\n\n\n\n
Dealing with the internal server error on your website is a recipe for a bad day for sure, but hopefully we’ll get it fixed in no time together!<\/p>\n\n\n\n
Here’s how to get rid of the error<\/strong> if you’ve encountered it on your own website (running WordPress):<\/strong><\/p>\n\n\n
<\/div>\n\n\n\n1. Clear your browser cache<\/h3>\n\n\n\n
Caching<\/a> is the process of storing website data in the user’s browser for faster access. By taking the most frequently accessed site data and putting it in the cache, subsequent visits to the website can bypass certain time-consuming processes, such as retrieving data from the server or rendering complex page elements. This results in quicker page load speed and better user experience.<\/p>\n\n\n\n
The greatest downside of caching is that it can end up displaying outdated content to visitors. So, the 500 error displayed on the website that you are browsing may be a cached version of the site. The error could have been a temporary glitch and might have been automatically removed.<\/p>\n\n\n\n
This is why clearing your browser cache is the easiest and also very often the most effective step to “fixing” the 500 internal server error. I’m saying fixing<\/em> there in quotes since you’re not actually fixing it – you’re just refreshing your own browser so that you can access the website without the error.<\/p>\n\n\n\n
Here’s how to clear your cache in the most popular web browsers<\/a>.<\/p>\n\n\n\n
![\"clearing](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2024\/04\/clearing-google-cache.png\")
<\/figure>\n\n\n<\/div>\n\n\n\n2. Check the debug log<\/h3>\n\n\n\n
The debug log<\/a> is an in-built WordPress tool that contains detailed information about errors and warnings that occur on a WordPress website.<\/p>\n\n\n\n
The debug log of your website should contain details about the “HTTP 500 internal server error” and could point you to the source of the error. Knowing the cause is half the battle won.<\/p>\n\n\n\n
By default, the WordPress debug log is turned off to prevent displaying potentially sensitive information to visitors. You will need to turn it on first.<\/p>\n\n\n\n
With the internal server error being displayed on your website, you are unlikely to have access to your WordPress dashboard. Therefore, you will need to go to the backend of your website to insert a piece of code in the wp-config.php<\/em> file and enable the debug log.<\/p>\n\n\n\n
You can do this by connecting to your site via FTP or through your hosting account. To use FTP, read this guide<\/a>. Below, I’m going to show you how to use the tools available on your hosting account.<\/p>\n\n\n\n
Log in to your hosting profile\/account and look for a link to cPanel<\/a><\/strong> – it’s a hosting management panel that most web hosts use. Once there, go to the File Manager<\/strong>:<\/p>\n\n\n\n
![\"file](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2024\/04\/file-manager-cpanel-namecheap.png\")
<\/figure>\n\n\n\nInside the File Manager, select the public_html<\/strong> folder and then locate the wp-config .php<\/em><\/strong> file.<\/p>\n\n\n\n
Right-click on the file and select the Edit<\/strong> option. The file will open on a different page.<\/p>\n\n\n\n
![\"edit](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2024\/04\/edit-wpconfile-in-file-manager.png\")
<\/figure>\n\n\n\nScroll down to the end of the config file and paste the following code<\/strong> right before this line:
\/* That's all, stop editing! Happy blogging. *\/<\/code>:<\/p>\n\n\n\ndefine( 'WP_DEBUG', true); \ndefine( 'WP_DEBUG_LOG', true);<\/code><\/pre>\n\n\n\nSave<\/strong> the changes and exit the file.<\/p>\n\n\n\n
Next, go to public_html \u2192 wp-content \u2192 debug.log<\/strong>.<\/p>\n\n\n\n
Open the file by right-clicking and selecting the Open<\/strong> option.<\/p>\n\n\n\n
Look for the 500 internal server error record and read through the details of the error.<\/p>\n\n\n\n
If you’ve found the real cause, then jump to the relevant solution in the sections below. If not, then start implementing the following solutions one by one anyway.<\/p>\n\n\n
<\/div>\n\n\n\n3. Deactivate plugins<\/h3>\n\n\n\n
Open your hosting account and go to cPanel \u2192 File Manager \u2192 public_html \u2192 wp-content \u2192 plugins<\/strong>.<\/p>\n\n\n\n
Right-click<\/strong> on the plugins folder, select Rename<\/strong>, and rename the folder to “plugins-off<\/strong>.” It will deactivate all plugins.<\/p>\n\n\n\n
![\"rename](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2024\/04\/rename-plugins-folder-file-manager.png\")
<\/figure>\n\n\n\nDeactivation will help check whether a plugin conflict was causing the error. If you don’t see an error on your website any longer, then it confirms the plugin conflict theory.<\/p>\n\n\n\n
Next, revert to the original name<\/strong> of the folder to reactivate all your plugins. This will cause the error to return. Don’t worry.<\/p>\n\n\n\n
Open<\/strong> the plugins folder and start deactivating the plugins one by one – change each plugin folder’s name individually. Each time you deactivate a plugin, check whether the error is gone. At some point, the error will be removed and you will know that the plugin you just deactivated was causing it.<\/p>\n\n\n\n
Remove that plugin by right-clicking on the plugin folder and selecting the Delete<\/strong> option.<\/p>\n\n\n
<\/div>\n\n\n\n4. Deactivate your theme<\/h3>\n\n\n\n
To deactivate your current theme, you need to switch to a different one. I suggest switching to the default WordPress theme that you should have present on your site already – it’s probably just sitting there deactivated.<\/p>\n\n\n\n
To do this, connect to the database using phpMyAdmin<\/a> (or whichever tool your host uses) from the hosting control panel. Once you’re in, select the WordPress database and find the wp_options<\/em> (it might have a different prefix) table in the menu to the right.<\/p>\n\n\n
\n![\"The](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/wp-options-table.png\")
<\/figure><\/div>\n\n\nOpen the table and click on Search<\/em><\/strong> in the navigation menu at the top of the screen. Type “template”<\/em> into the Value<\/em><\/strong> field that corresponds to the option_name<\/em> column and click on Go<\/em><\/strong>.<\/p>\n\n\n
\n![\"Searching](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/template-option-name.png\")
<\/figure><\/div>\n\n\nThis will return a single entry from the wp_options<\/em> table. That entry tells WordPress which theme to use; the theme is twentytwenty<\/em> in our example.<\/p>\n\n\n
\n![\"The](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2023\/10\/template-value.png\")
<\/figure><\/div>\n\n\nDouble-click on the name of the theme under option_value<\/em> and you can change it to something else. This needs to be a theme that’s installed on the website or you’ll run into further errors.<\/p>\n\n\n\n
Some safe bets for most sites are default theme options, such as twentytwentythree<\/em> or twentytwentytwo<\/em>. When you’re done, check your website to see if the 500 internal server error persists.<\/p>\n\n\n
<\/div>\n\n\n\n5. Re-upload core files<\/h3>\n\n\n\n
Head over to wordpress.org<\/a> and download the latest version of WordPress on your local computer. Next, unzip<\/strong> the file (this is IMPORTANT<\/strong>).<\/p>\n\n\n\n
Go back to your hosting account and again into cPanel \u2192 File Manager \u2192 public_html<\/strong>. Click on Upload<\/strong> to upload the new WordPress folder.<\/p>\n\n\n\n
![\"upload](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2024\/05\/upload-button-public-html.png\")
<\/figure>\n\n\n\nYou’ll get informed that you’re about to overwrite the files. This is okay – it’s exactly what we want. Grant the permission and let the new files upload.<\/p>\n\n\n\n
It will take a few seconds for the process to be complete. Check if the 500 error is gone.<\/p>\n\n\n
<\/div>\n\n\n\n6. Regenerate .htaccess<\/em> file<\/h3>\n\n\n\n
To regenerate the .htaccess<\/em> file, go to public_html \u2192 .htaccess<\/em><\/strong>. Right-click on the file and hit the Download<\/strong> button to download the existing file to your local computer as a backup.<\/p>\n\n\n\n
Right-click again and hit the Delete<\/strong> button to delete the file.<\/p>\n\n\n\n
Click the +File<\/strong> icon in the toolbar at the top of your screen. Type in “.htaccess<\/em>“<\/strong> into the New File Name input field.<\/p>\n\n\n\n
![\"add](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2024\/04\/add-file-symbol-in-file-manager.png\")
<\/figure>\n\n\n\nClick Create New File<\/strong>. Right-click the newly created file to Edit<\/strong> it. Add the following code:<\/p>\n\n\n\n
# BEGIN WordPress\nRewriteEngine On\nRewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]\nRewriteBase \/\nRewriteRule ^index\\.php$ - [L]\nRewriteCond %{REQUEST_FILENAME} !-f\nRewriteCond %{REQUEST_FILENAME} !-d\nRewriteRule . \/index.php [L]\n# END WordPress<\/code><\/pre>\n\n\n\nThe code above comes from the official template for the .htaccess<\/em> file<\/a> that WordPress uses.<\/p>\n\n\n\n
Save<\/strong> the file before you close the window.<\/p>\n\n\n
- PHP memory limit exhaustion<\/strong> causes resource-intensive operations to terminate prematurely;<\/li>\n\n\n\n
- Poorly coded plugins or themes<\/strong> can cause conflicts with other plugins and themes, triggering the error;<\/li>\n\n\n\n
![\"select](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2024\/04\/select-php-version-cpanel-namecheap.png\")
<\/figure>\n\n\n\n![\"set](\"https:\/\/mllj2j8xvfl0.i.optimole.com\/cb:c5QE.37290\/w:auto\/h:auto\/q:mauto\/f:best\/https:\/\/themeisle.com\/blog\/wp-content\/uploads\/2024\/05\/increase-memory-limit-from-cpanel.png\")
<\/figure>\n\n\n\n