Error 500 Internal Server Error: fix

What this error means

The 500 Internal Server Error means the server could not complete the request because something failed while the website was being executed.

It is a generic error. That means the browser does not show the exact cause, only that something is preventing the page from loading.

On PHP websites, WordPress, PrestaShop and other CMS platforms, a 500 error is often related to incorrect permissions, incompatible .htaccess rules, PHP errors or plugin conflicts.

Why it happens

The most common causes are:

1. Incorrect file or directory permissions.
2. Misconfigured rules in the .htaccess file.
3. PHP errors on the website.
4. Incompatible plugins, modules or themes.
5. A PHP version that is not compatible with the application.
6. Memory or process limits being reached.
7. Damaged files after an update or FTP upload.

How to fix it

1. Review file and folder permissions

The general recommended permissions are:

Files: 644
Directories: 755

If permissions are too open or too restrictive, the server may block execution and return a 500 error.

From DirectAdmin, cPanel or FTP, pay special attention to:

• index.php
• .htaccess
• WordPress folders such as wp-content, wp-admin and wp-includes
• cache, theme and plugin folders

2. Try renaming the .htaccess file

An incorrect .htaccess rule can trigger a 500 error across the entire website.

To test it:

1. Open the file manager or connect by FTP.
2. Locate the .htaccess file in the website root.
3. Rename it temporarily, for example:

.htaccess_old

4. Reload the page.

If the error disappears, the problem is in one of the .htaccess rules.

In WordPress, you can regenerate the file by going to Settings > Permalinks and saving changes without editing anything.

3. Review PHP errors

Check the error log from the control panel. It may appear as:

• Error Log
• Errors
• Logs

The log may indicate the exact file that is failing, the error line or a memory issue.

4. Disable recent plugins or modules

If the error started after installing or updating a plugin, theme or module, disable it temporarily.

In WordPress, if you cannot access the admin area:

1. Connect through FTP or the file manager.
2. Go to:

wp-content/plugins/

3. Rename the folder of the suspicious plugin.
4. Test the website again.

You can also rename the whole plugins folder temporarily to rule out a broader conflict.

5. Check the PHP version

A PHP version that is too old or too new can break an application.

From the control panel, review the active PHP version and confirm that it is compatible with your CMS, theme and plugins.

Before changing the PHP version, make a backup.

6. Restore files if the error started after an upload

If the issue began after uploading files by FTP, some files may be incomplete, damaged or placed in the wrong folder.

Upload the affected files again or restore a recent backup.

What to do if the problem continues

If the error still appears after reviewing permissions, .htaccess, plugins and PHP, open a support ticket and include:

• The affected domain.
• The exact URL where the error appears.
• Recent changes made on the website.
• The approximate time of the failure.
• A screenshot of the message if possible.

That information makes it easier to review server logs and find the cause.

Conclusion

The 500 Internal Server Error is often resolved by reviewing permissions, testing the .htaccess file, checking logs and disabling recent plugins or modules.

If you cannot identify the cause, contact support so they can review the case using the server logs.