Simple Steps to Solve 500 Internal Server Errors
This error is one of the frustrating for the beginners. Often this error occurs when you blog core files or corrupted or not install properly. If you are seeing 500 internal server errors on your blog then this step by step guide will help you to fix the error easily.
If something goes wrong on your core files of WordPress blog, then you will see 500 internal server errors which will be bit tough to deal with. Typically, this error occurs when you install or update the faulty plugins or the theme in your WordPress blog.
Another possibility cause of this error is the corrupted .htaccess file which is main file that holds the configuration file of your blog. There could be another reason that you will see this error and that is limited PHP memory which is set in your server.
500 internal server error is one the common issue that every blog may experience once. Since the error messages do not direct you the specific path where to find and fixed, it can be overwhelming to anyone to know the exact issue.
These guides will help you to troubleshoot 500 Internal Server Error looking into few core areas of your blog.
4 ways to Troubleshoot the 500 Internal Server Error
- Fix/Replace .htaccess File in the server.
- Increase the memory limit of PHP
- Disable all the Plugins
- Try Reinstalling WordPress Core Files
Step-1: Fix/Replace .htaccess File in the server.
First thing you should look into is your .htaccess files which is the core files that have configuration code to run your WordPress blog in root folder of your hosting server which you need to access using FTP client such as FileZilla or CoreFTP.
Go to the official website and Download FileZilla and install it into your computer. After downloading, connect FileZilla to the hosting server where you need to username and password that will get from your hosting providers. You will see have two sections Local site and Remote site.
From Remote site, go to public_html folder to open where you will see the list of WordPress core files and folders such as wp-admin and wp-content, you will also see the core files called .htaccess in the same location.
Find .htaccess file in the same location. Right click on .htaccess file and rename the file name e.g. .htaccess-fix.
Go back to your web browser and load your site, if your site load without error then you have fixed the 500 internal server error successfully. Now, you have to login to WordPress dashboardand update the Permalink under Settings which will generate new .htaccess file and avoid 404 page error in your blog pages and posts.
Login to WordPress Dashboard and Click on Permalinks under Settings. Click on Save Changes without changing the any settings.
If you still see 500 Internal Server Error then follow the next step.
Step-2: Increase PHP Memory Limit
Internal Server Error can also cause by the limited PHP Memory. You can fix this error by increasing PHP memory by editing wp-config.php files located in the root directory of the web server.
Connect to your web server using FileZilla. Open public_html at the right side. You will see the file called wp-config.php file in the same location where your wp-content and wp-admin folders are located.
Right click on wp-config.php file and click on View/Edit.
Your file will open in file editor where you have to add the line of code below <?php tag.
After adding the line of code, save the file and reload your website. If the issue is fixed by increasing the PHP memory limit then Great! But you still have to find the problem which plugins or themes is eating the PHP memory and remove or replace it from your website.
If increasing PHP memory limit did not fix the error then follow the next step.
Step-3: Deactivate Plugins
Faulty plugins can also cause 500 Internal Server Error. You can deactivate all the plugins renaming the plugins folder located in root directory of the web server. Connect to the server using FileZilla and double click on public_html folder to open where you will see the WordPress core files and folders.
Open wp-content folder and you will find plugins folder. Right click on the plugins folder and click on rename then type any name e.g. plugins-fix. These will deactivate all the installed plugin in your WordPress site.
You can refer this guide on How to deactivate all the WordPress plugins for more details.
Once all the plugins deactivate you can try loading your site, if everything goes well and website loads without error then you know the issue is cause by one of the plugins.
To find the faulty plugin login to WordPress dashboard and activate the installed plugins one by one until your site breaks. Once you figure out which plugin is creating issue you can remove or replace it from your website.
Step-4: Reinstall WordPress Core Files
If above troubleshooting does not fix the error, then you should reinstall wp-admin and wp-include folder from the fresh copy of WordPress file. Re-uploading those folders will not affect your blog data.
Use this link to Download Core WordPress file and save it on the desktop.
Once downloaded you will see WordPress file in ZIP format. Right click on the file and click on extract here. It will extract and create separate WordPress folder on the desktop.
Now, Open FTP client FileZilla and connect to your web server. From Server Section, click on public_html to open root directory of your website where you will find WordPress core files and folders e.g. wp-admin, wp-content, wp-includes.
From the PC section expand Desktop and select WordPress folder. Select wp-admin and wp-includes holding CTRL key then right click on the folders and click on Upload.
FileZilla will start transferring those folders to your web server which will replace existing wp-admin and wp-content folder in the server. You will see the pop up to overwrite the folders. Click on Always use this action and click ok button.
We hope that this guide is being helpful to you. You may also like to take a glance on How to Solve Image Upload Issue. Please share and follow us on Facebook. and let us know your opinion in the comment section below.