Common Solutions for the 500 Internal Server Error

he two most regular reasons for this blunder are a tainted .htaccess record and surpassing your server’s PHP memory limit. The .htaccess record in your WordPress registry can move toward becoming tainted after you introduce a module or roll out another improvement to your WordPress site. The fix is straightforward. You should simply make another .htaccess document.

PHP memory limit issues frequently happen as the consequence of an inadequately coded module running on your site or a site that is developed impressively after some time and is utilizing such a large number of modules. You’ll start to surpass the PHP memory limits set by your facilitating supplier once both of these things occur. The outcome is a 500 inward server blunder.

We will figure out how to make another .htaccess to dispose of the tainted one just as how to test regardless of whether you’re surpassing your PHP memory limits.

Making a New .htaccess File

Open your WordPress root registry in FileZilla or your favored FTP customer. This is ordinarily called public_html. In the event that you see organizers named wp-administrator and wp-content, you’re in the ideal spot. On the off chance that you don’t see your .htaccess document or any dotfiles, make shrouded records visible by clicking Server and choosing Force Showing Hidden Files.

When you discover your .htaccess record, right-click it, and rename it “.htaccess.bak”. This basically erases your site’s .htaccess document, so we have to make another one. Go into your WordPress administrator territory. Drift over Settings, and select Permalinks. Look down to the base of the page, and snap Save Changes.

Open your site in your program. In the event that the 500 inner server blunder is gone, it was brought about by an adulterated .htaccess document and your issue is presently fixed. In case despite everything you’re seeing the mistake, you have some more tests to run.

It’s additionally worth referencing that an inappropriately named .htaccess document will make this blunder keep running on your site. Ensure this record isn’t named something besides “.htaccess”.

Leave a Reply

Your email address will not be published. Required fields are marked *