{"id":553,"date":"2016-10-20T10:39:02","date_gmt":"2016-10-20T10:39:02","guid":{"rendered":"http:\/\/www.fastwebhost.in\/blog\/?p=553"},"modified":"2019-01-31T07:28:31","modified_gmt":"2019-01-31T07:28:31","slug":"different-ways-to-fix-500-internal-server-error","status":"publish","type":"post","link":"https:\/\/www.fastwebhost.in\/blog\/different-ways-to-fix-500-internal-server-error\/","title":{"rendered":"6 Ways to Fix 500 Internal Server Error"},"content":{"rendered":"

Internal Server Error is one of the common WordPress errors that can put a WordPress beginner in panic mode. If you have been surfing the web for more than a year, then you probably have seen the HTTP 500 Internal Server Error at least a few times.<\/p>\n

I assure you that they are all fixable. In this article, I will show you how to fix 500 Internal Server Error in WordPress. Let me compile a list of all possible solutions in one place.<\/p>\n

\u200b<\/p>\n

\"How<\/span><\/p>\n

\u200b<\/p>\n

Check .htaccess file<\/h2>\n

Most commonly 500 Internal Server Errors occurs due to misconfiguration of ‘.htaccess’ file. So, you may want to rename it like ‘.htaccess_bk’. Usually, this folder is present in public_html folder of your file manager. As it is a hidden file you need to select the option called show hidden files in settings of your file manager. Check the permissions for ‘.htaccess’ mostly it is 644.<\/p>\n

\u200b<\/p>\n

\"11\"<\/span><\/p>\n

\u200b<\/p>\n

Check PHP version<\/h2>\n

In case you are using PHP version above 5.3 and your .htaccess file consists of “register_globals = on” line you need to remove it and reload your site. As register globals only support till PHP version 5.3.<\/p>\n

Check WordPress Plugins <\/h2>\n

Another reason for 500 Internal Server Error, it may cause due to WordPress plugins. If you are getting this error after activating any new plugin, I recommend you to deactivate the new plugin and reload  your website.<\/p>\n

There might be a case in which you cannot access the WordPress dashboard. Here you can use FTP or cPanel to navigate to the \u2018plugins\u2019 folder to the wp-content folder.<\/p>\n

Rename the \u2018plugins\u2019 folder (say plugins_old). Reload your website after activating all plugins one by one. Reload your website and check if 500 Internal Server Error is gone or not. If not, there is some other cause of this error. Let’s discuss this further.<\/p>\n

\"22\"<\/span><\/p>\n

Check WordPress Themes<\/h2>\n

This same procedure implies for themes. Make use of an FTP client or cPanel. Now, open the \u2018themes\u2019 folder and rename the folder containing all files which access the theme which is activated.<\/p>\n

This will deactivate the current theme and the default theme will be active automatically. Reload the website. If you still see that error message, nothing is wrong with the theme.<\/p>\n

Check php memory limit<\/h2>\n

Plugins,scripts, and themes often utilize huge memory. All you need to do is to add following line of code “memory_limit = 64M” in your php.ini file present in your home directory.<\/p>\n

When WordPress files corrupts<\/h2>\n

If your WordPress core files corrupted, then you need to re-upload a fresh version of wp-admin and wp-includes folders from a new WordPress installation. As the wp-content folder remains untouched.<\/p>\n

\u200bConclusion<\/h3>\n

So, from this article,  you will get clear perception from where exactly the problem occurs when you encounter 500 Internal Server Error. Hope this article saves your time from researching and fixing error.<\/p>\n

All the best!<\/p>\n","protected":false},"excerpt":{"rendered":"

Internal Server Error is one of the common WordPress errors that can put a WordPress beginner in panic mode. If you have been surfing the web for more than a year, then you probably have seen the HTTP 500 Internal Server Error at least a few times. I assure you that they are all fixable. […]<\/p>\n","protected":false},"author":11,"featured_media":600,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[83],"tags":[31,12],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/posts\/553"}],"collection":[{"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/comments?post=553"}],"version-history":[{"count":3,"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/posts\/553\/revisions"}],"predecessor-version":[{"id":4816,"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/posts\/553\/revisions\/4816"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/media\/600"}],"wp:attachment":[{"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/media?parent=553"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/categories?post=553"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fastwebhost.in\/blog\/wp-json\/wp\/v2\/tags?post=553"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}