Quick answer: The WordPress 500 error is a PHP fatal error, usually from a corrupted .htaccess, exhausted memory, or a broken plugin, theme, or core file. Enable debug logging to read the cause, regenerate .htaccess, raise the memory limit, deactivate plugins, or re-upload fresh core files.
An HTTP 500 internal server error shows a blank or generic error page with no detail, because the real cause is written to a log rather than the screen. In WordPress it is almost always a corrupted .htaccess file, a PHP memory limit, or a broken plugin, theme, or core file. Work through these in order.
Turn on logging by adding this to wp-config.php:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
Reload the page, then open wp-content/debug.log - it names the file and line causing the failure. Also check your server's error log in the control panel. Set these back to false when done.
A corrupted .htaccess is a frequent cause. Rename it to .htaccess_old via FTP or File Manager, then reload the site. If it returns, go to Settings > Permalinks in wp-admin and click Save to generate a fresh, valid file.
If the log shows "memory exhausted", increase the limit (see the memory-limit guide) - add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php.
Deactivate all plugins - if you cannot reach admin, rename wp-content/plugins to disable them at once. If the error clears, reactivate one at a time to find the culprit. Then switch to a default theme to rule the theme out.
If nothing above works, re-upload fresh wp-admin and wp-includes folders from a clean copy of the same WordPress version, leaving wp-content and wp-config.php untouched. This repairs a corrupted core file without losing content.
How do I regenerate .htaccess?
Rename the file, then go to Settings, Permalinks and click Save to create a fresh one.
What if nothing else works?
Re-upload clean wp-admin and wp-includes folders from the same WordPress version, leaving wp-content and wp-config.php alone.
On SoftSys managed WordPress hosting the server logs are readily available and our team will trace and fix a 500 error for you, so you are not left guessing at a blank page.