WP Maintenance disaster
Internal Server Error
The 500 Internal Server Error is a really general HTTP status code that indicates something has failed on the website’s server, however, the server might not be more specific on what the specific issue is. The internal server error is not particular to WP. It can occur with any website running on a web server. An internal server error (likewise known as “500 Internal Server Error”) can be among the most complicated mistakes a WP owner can experience. This takes place when there’s something wrong but the server cannot determine what it is. Because the message does not inform you what’s incorrect, you’ll have to conduct your own investigation.
This is how it looks:
Internal server error during WP Maintenance is often brought on by plugin or theme functions. Other possible causes of internal server error that we know of are corrupted .htaccess file and PHP memory limit. Here are the TOP 4 (FOUR) potential causes and their method to solve it:
1 – WordPress Maintenance disaster – Internal Server Error – plugin or theme problem:
If you suspect you’re dealing with a plugin or theme problem, attempt deactivating plugin(s)/theme and/or reverting to a previous version that was active when your site was working. If WP-ADMIN is also down, connect via FTP/cPanel/WHM/SSH and simply delete your theme from here: “…/public_html/wp-content/themes/” or your plugin from here: “…/public_html/wp-content/plugins/”
2 – WordPress Maintenance disaster – Internal Server Error – corrupted .htaccess file:
This is the most common reason for an internal server error. To fix it, merely gain access to your website root through FTP, and rename your .htaccess file to .htaccess_old. Refresh the website to see if this solves the problem. If it does, go to Settings > Permalinks to reset your permalinks. This will generate a new .htaccess for you.