{"id":10409820,"date":"2018-06-18T08:25:14","date_gmt":"2018-06-18T08:25:14","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/wp-admin-500-internal-server-error\/"},"modified":"2018-06-18T08:25:14","modified_gmt":"2018-06-18T08:25:14","slug":"wp-admin-500-internal-server-error","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/wp-admin-500-internal-server-error\/","title":{"rendered":"\/wp-admin 500 internal server error"},"content":{"rendered":"<p>Hi,<\/p>\n<p>Our server has recently moved to a new version of VPS.<\/p>\n<p>The front end is working fine.<\/p>\n<p>\/wp-admin produces an 500 internal server error.<\/p>\n<p>If I turn on wp_debug &amp; wp_debug_log, nothing is produced.<\/p>\n<p>The error_log in the web root says:<\/p>\n<blockquote><p>Error reading Wordfence Firewall config data, configuration file could be corrupted or inaccessible. Path: \/home\/user\/public_html\/wp-content\/wflogs\/config.php<\/p><\/blockquote>\n<p>\/wp-content\/wflogs\/config.php was a 0KB file, so I renamed it to config.temp.php, but \/wp-admin still produces a 500 internal server error.<\/p>\n<p>I&#8217;ve moved wordfence to \/wp-content\/plugins.temp, but the issue remains.<\/p>\n<p>Help appreciated.<\/p>\n<p>Steve<\/p>\n","protected":false},"template":"","class_list":["post-10409820","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/10409820","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/10409820\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=10409820"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}