The following HTTP status code 500 indicates an issue with the server. This status code is a bit generic and does not provide further and sufficient information on what exactly is wrong. It usually presents itself on the browser and can upset users and technicians. This simply tells us that there is something wrong and the server responded with this code on the browser\u2019s request.<\/p>\n
The reasons for the error can differ and can be caused either by the server or by some changes made by the user. Here are some of the checks and fixes that anyone can use and try:<\/p>\n
The default permissions on a Linux\/Unix environment are 644 for the files and 755 for the folders. It is a common case where some files in a WordPress installation (such as the index.php file) will either have restrictive(non-readable) permissions or they will have too open permissions which in some cases can also lead to the error depending on the web server settings. If you have access to a terminal you can try to run the following commands from the document root folder of the website which will set the default permissions for files and folders:<\/p>\n
Another common cause is that there is a syntax error or a conflicting rule in the .htaccess file. You can check the server error logs as such errors will be recorded there and also you can try to rename the current active .htaccess file and test with a default WordPress .htaccess with only the default rewrite rules.<\/p>\n Again check this file for any syntax errors, typos, or missing \u201c;\u201d and the end of a function.<\/p>\n You can try to add this line in your wp-config.php file:<\/p>\n Or you can try adding the line in your php.ini file:<\/p>\n Of course, you can adjust the value accordingly and also have in mind any hosting limitations on this PHP value.<\/p>\n You can try to deactivate all your plugins and then check if the site will load. If it loads then the issue is probably caused by some of your plugins due to poor code or due to incompatibility with some other plugin. You can then try to activate the plugins one by one and try to identify the troubled one.<\/p>\n In some cases, there can be a corrupt core file and it might be difficult to locate the exact one. What you can do is upload fresh core files. This would mean all files and folders except your wp-content folder your wp-config.php file and your .htaccess file.<\/p>\n If you have tried all of the above and the issue persists then you can then get in touch with the hosting support as there is a high chance that there might be a server issue, or they might be able to further help you.<\/p>\n","protected":false},"excerpt":{"rendered":" The following HTTP status code 500 indicates an issue with […]<\/p>\n","protected":false},"author":1,"featured_media":13878,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[142],"tags":[],"class_list":["post-8535","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress-common-issues"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tfind . -type d -exec chmod 755 {} \\;
\nfind . -type f -exec chmod 644 {} \\;<\/code><\/p>\nCheck your .htaccess file<\/h3>\n
Check your wp-config.php file<\/h3>\n
Increase memory<\/h3>\n
define( 'WP_MEMORY_LIMIT', '512M' );<\/code><\/p>\nmemory_limit = 512M<\/code><\/p>\nCheck your plugins<\/h3>\n