How to Fix 500 Internal Server Errors Print

Introduction

A 500 Internal Server Error means something has gone wrong on the server, but the server can't be more specific about what the problem is. It's one of the most common errors you'll encounter, and the good news is that it's usually caused by something in your account that you can fix yourself.

This guide walks through the most common causes and how to resolve them.

Common Causes and Fixes

1. Corrupted .htaccess File

This is the most common cause of 500 errors. The .htaccess file controls how your server handles requests, and a single typo can bring your site down.

How to fix it:

1. Log into cPanel and open File Manager.
2. Navigate to your website's root directory (usually public_html).
3. Click Settings in the top right and tick Show Hidden Files.
4. Find the .htaccess file and rename it to .htaccess_backup.
5. Visit your website. If it loads, the .htaccess file was the problem.
6. Create a new .htaccess file with default WordPress rules (if using WordPress):

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

2. PHP Memory Limit Exceeded

If your site runs out of PHP memory, it can trigger a 500 error. This often happens with complex plugins or themes.

How to fix it:

1. In cPanel File Manager, navigate to your WordPress root directory.
2. Open wp-config.php and add this line before "That's all, stop editing!":

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

If this doesn't help, contact our support team as the server may need a configuration change.

3. Faulty Plugin or Theme

A recently installed or updated plugin or theme can cause 500 errors if it has a bug or compatibility issue.

How to fix it:

1. In cPanel File Manager, navigate to wp-content/plugins.
2. Rename the plugins folder to plugins_disabled.
3. Check your website. If it loads, a plugin was the problem.
4. Rename the folder back to plugins.
5. Re-enable plugins one at a time (via WordPress admin) to find the culprit.

For themes, repeat this process with the wp-content/themes folder. WordPress will fall back to a default theme.

4. Incorrect File Permissions

File permissions that are too restrictive (or too open) can cause 500 errors.

Correct permissions:

• Folders: 755
• Files: 644
• wp-config.php: 600 or 640

You can check and fix permissions in cPanel File Manager by right-clicking a file or folder and selecting Change Permissions.

5. PHP Version Incompatibility

Some plugins or themes require a specific PHP version. Running an incompatible version can cause 500 errors.

How to fix it:

1. In cPanel, go to Select PHP Version (or MultiPHP Manager).
2. Try switching to PHP 8.1 or 8.2 (the most widely compatible versions).
3. Check your website after the change.

Check the Error Log

If none of the above fixes work, the error log will tell you exactly what's going wrong.

1. In cPanel, go to Metrics > Errors.
2. Look at the most recent entries for clues (file paths, PHP errors, permission issues).

The error log is the fastest way to pinpoint the exact cause.

Still Stuck?

If you've worked through all the steps above and the error persists, open a support ticket and include:

• The URL that shows the error
• When the error started
• Any changes you made recently (plugin updates, file edits, etc.)

Our support team will investigate and get you back online.