you're reading...
Articles, News

Internal Server Error

Almost every WordPress user I know has encountered the internal server error at least once. It’s quite annoying because, unlike many common WordPress errors, the internal server error does not tell you what you need to fix. This can be frustrating since the error can be a result of several reasons as you’ll see below.

INTERNAL SERVER ERROR CAUSES:

Some of the possible causes for the Internal Server error are the following:

  • Corrupted plugin functions
  • Corrupted theme functions
  • Corrupted .htaccess
  • Exhausted PHP memory limit

INTERNAL SERVER ERROR SOLUTIONS:

This error can easily send a beginner into panic mode but worry not, here are some solutions.

a. Edit .htaccess file
Since the internal server error is mainly a result of a corrupted .htaccess file, login into your WordPress root directory via File Manager (or FTP) and rename your .htaccess file to .htaccess.old. Refresh your browser to see if you solved the error. If the error disappeared, go to Settings -> Permalinks and click on the Save Changes button to reset your .htacess and flush write rules. If this does not work, perhaps you need to check your plugins.

b. Deactivate all plugins
A plugin you just installed could be the problem, but that’s great because you know what to uninstall or delete. Other times, this WordPress error may crop up as a result of an old plugin (or several plugins that are incompatible). You won’t know for sure if the problem is your plugins unless you deactivate the plugins.

ASIDE: If you’re seeing the internal server error, you probably can’t access WordPress Admin. So, how will you deactivate your plugins? Well, we found this how to deactivate all plugins when not able to access the administrative menus post at WordPress Codex. Alternatively, you can check out this How to Deactivate All WordPress Plugins without WP-Admin post at WPBeginner.If the error disappears after deactivating all the plugins, you found your problem and it’s time to play a little trial and error game. Reactivate one plugin at a time until you get the culprit. Delete the plugin and get a better substitute. You can also inform the plugin author because WordPress is beautiful and so should be the plugins.

c. Change Themes
If the problem was not the plugins, perhaps your theme is. Switch to the Twenty Twelve theme and reload your website. If you’re still seeing the error, perhaps you need to upgrade some of your WordPress folders.

d. Repair the wp-admin and wp-includes folders
By this point, you’ve probably solved this WordPress error. But if this is not the case, try replacing your wp-admin and wp-includes folders with newer ones from a fresh WordPress install.

1memory=64MB

Save and upload the file to the /wp-admin/ folder. If increasing your PHP memory solves the problem, talk to your web host to put a finger on what is exhausting your memory. It could be anything from broken theme functions to poorly designed plugins among other things. Your web host will furnish you with information from your server logs.

e. Increase your PHP memory Limit
If everything else fails, you have to get down and dirty and mess with a few things on your server. The internal server error can be frustrating, so I don’t expect anything to stop you. Here is a great guide on increasing PHP memory by the good guys at WordPress.If you like taking shortcuts, fire up your code editor and create a text file named php.ini. Inside this file, add this code:

Ref: http://www.wpexplorer.com/wordpress-common-errors-solutions/

Advertisements

About Admin

#WP #D

Discussion

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: