Before doing anything else, rule out the simplest possibilities.

• Hard refresh your browser: press Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac
• Clear your browser cache completely
• Try a different browser or open the site in an incognito/private window
• Wait 60 seconds and try again — sometimes 500 errors are momentary server glitches

If the error persists after all of the above, it's a real problem that needs fixing.

A corrupted .htaccess file is the single most common cause of 500 Internal Server Errors in WordPress. This is always the first real fix to try.

Step 1: Rename (disable) the current .htaccess file

1. Connect to your server via FTP or your hosting file manager
2. Navigate to the root WordPress directory (where wp-config.php lives)
3. Find the file named .htaccess

4. Rename it to .htaccess_old
5. Reload your website

If the site loads, the .htaccess file was indeed corrupted. Now you need to create a fresh one.

Step 2: Generate a new .htaccess file

1. Log in to your WordPress admin dashboard
2. Go to Settings → Permalinks
3. Without changing anything, click Save Changes

WordPress will automatically generate a clean, new .htaccess file with the correct rewrite rules. Your old one (now renamed .htaccess_old) can be deleted once you've confirmed everything is working.

If your WordPress site is running resource-heavy plugins or processing large amounts of data, it can run out of PHP memory and return a 500 error.

Edit wp-config.php:

1. Connect via FTP and open wp-config.php in your WordPress root folder
2. Add the following line just before the comment that says /* That's all, stop editing! */:

define('WP_MEMORY_LIMIT', '256M');

Save the file and reload your site

Edit .htaccess (Apache servers):
If editing wp-config.php doesn't work, try adding this to your .htaccess file:

php_value memory_limit 256M

Ask your hosting provider:
Some hosting plans have a hard cap on memory that can only be increased from the server side. If neither of the above methods works, contact your host and ask them to increase your PHP memory limit.

Plugins are the second most common cause of 500 errors. A single faulty plugin can crash the server response before WordPress finishes loading.

If you can access wp-admin:

1. Go to Plugins → Installed Plugins
2. Select all plugins using the top checkbox
3. Choose Deactivate from the Bulk Actions dropdown and click Apply
4. Reload your site

If wp-admin itself shows a 500 error:

1. Connect via FTP and navigate to /wp-content/
2. Rename the plugins folder to plugins_disabled
3. Reload your site — WordPress will disable all plugins automatically
4. If the site loads, rename the folder back to plugins
5. Log in to wp-admin and reactivate plugins one at a time, reloading after each

The plugin that brings back the 500 error is your culprit — leave it deactivated and contact the developer or find an alternative.

If disabling plugins didn't fix the 500 error, your active theme may be the problem — especially if the error started after a theme update or customization.

1. Connect via FTP and navigate to /wp-content/themes/
2. Rename your active theme's folder (e.g., rename divi to divi_old)
3. WordPress will fall back to the most recently installed default theme (such as Twenty Twenty-Four)
4. Reload your site

If the site now loads, your theme was the cause. You can either:

• Restore the theme and look for a syntax error (especially in functions.php)
• Update the theme to the latest version
• Contact the theme developer for support

If the 500 error is caused by a PHP fatal error, enabling debug mode will reveal the exact error message, file name, and line number responsible.

1. Open wp-config.php via FTP
2. Find this line:

define('WP_DEBUG', false);

Replace it with:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', true);
@ini_set('display_errors', 1);

Save the file and reload the page showing the 500 error

Instead of the generic error page, you should now see the actual PHP error. This will tell you exactly which plugin, theme file, or core function is causing the crash.

Once you've identified and fixed the issue, always turn debug mode off by setting WP_DEBUG back to false. Leaving debug mode enabled on a live site exposes sensitive information.

You can also check the debug log file at /wp-content/debug.log for errors that occurred before you enabled debug mode.

WordPress requires specific file and folder permissions to function correctly. If these are set incorrectly — often after a manual file upload or server migration — the server may refuse to read the files and return a 500 error.

Correct WordPress permissions:

How to fix permissions:

Using an FTP client like FileZilla:

1. Right-click on the folder or file
2. Select File Permissions
3. Enter the correct numeric value and check Recurse into subdirectories for folders
4. Click OK

You can also fix permissions in bulk via SSH:

# Fix folder permissions
find /path/to/wordpress/ -type d -exec chmod 755 {} \;

# Fix file permissions
find /path/to/wordpress/ -type f -exec chmod 644 {} \;

If the 500 error appeared after a WordPress update or if you suspect a malware infection may have corrupted core files, re-uploading fresh WordPress files can fix the problem without affecting your content.

1. Download the latest WordPress version from wordpress.org
2. Unzip the downloaded file on your computer
3. Delete the wp-content folder from the unzipped package — you must not overwrite your existing content
4. Also do not overwrite wp-config.php if it appears
5. Connect via FTP and upload all remaining files and folders to your WordPress root, overwriting existing files
6. Reload your site

This replaces all core WordPress files while leaving your database, themes, plugins, and uploads completely intact.

WordPress and its plugins have minimum PHP version requirements. If your host recently upgraded your PHP version, older code that was working fine may suddenly produce fatal errors — and 500 errors.

Check your PHP version:

1. Log in to your hosting control panel
2. Look for a "PHP Version Manager," "MultiPHP Manager," or similar tool
3. Note the currently active PHP version

Test with a different PHP version:

Try switching to a different PHP version (e.g., from 8.3 to 8.1 or 8.0) and reload your site after each change. If the 500 error disappears on a specific PHP version, one of your plugins or your theme has a compatibility issue with newer PHP.

Check the plugin's changelog or contact the developer for an update that supports your PHP version.

Every web server maintains error logs that record exactly what went wrong and when. These are often the fastest way to diagnose a 500 error when debug mode isn't showing a clear message.

Via cPanel:

1. Log in to cPanel
2. Go to Logs → Error Log
3. Look for entries timestamped around when the 500 error started appearing

Via FTP:
Error logs are sometimes stored in your WordPress root directory or in a logs folder. Common filenames are error_log, php_error.log, or access_log. Look for lines containing PHP Fatal error, PHP Parse error, or AH01215 — these will tell you exactly which file and line caused the server to fail.

If you've worked through every fix above and the 500 error persists, the problem may be at the hosting infrastructure level — something outside your control as a site owner.

Contact your hosting provider and share:

• The exact error message you're seeing
• When the error started
• Any changes you made before it appeared (updates, new plugins, etc.)
• What you've already tried

A good hosting provider will check server-side error logs, resource usage, and server configuration to identify the root cause.