Home › Knowledgebase › KB-1225

Website showing 500 internal server error how to fix

Summary

This guide helps you troubleshoot and resolve: Website showing 500 internal server error how to fix. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

A 500 Internal Server Error is a generic response from your web server indicating that something went wrong, but the server cannot specify exactly what the problem is. Because this error originates on the server side rather than your local computer or internet connection, refreshing the page will not usually resolve it. This guide explains the most common causes and how you can isolate the issue to get your website back online.

Remember — If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

Quick Fix Steps

  1. Wait a few minutes and refresh your browser to see if the error clears.
  2. Clear your browser cache or try viewing the site in an incognito or private window.
  3. Check if the error affects the entire website or only specific pages, such as the checkout or admin dashboard.
  4. If you recently installed a plugin, theme, or update, that is the most likely cause.

Detailed Instructions

1. Review your server error logs

Most hosting control panels provide access to error logs that record the exact cause of a 500 error. Look for entries that occurred at the time the error started.

  1. Log in to your website hosting control panel.
  2. Open the Metrics or Logs section.
  3. Select Errors or Error Log.
  4. Review the most recent entries for file paths, PHP errors, or database connection failures.

2. Rename the .htaccess file

A corrupted .htaccess file is one of the most common causes of a 500 error, especially after a plugin update or site migration.

  1. Connect to your hosting account using FTP or the File Manager in your control panel.
  2. Navigate to the root folder of your website, usually public_html or www.
  3. Locate the file named .htaccess.
  4. Rename it to .htaccess_old.
  5. Refresh your website in a browser.

If the site loads, the .htaccess file was the cause. You can regenerate a default file by visiting your site's permalink settings in your content management system.

Do not delete the .htaccess file permanently. Rename it first so you can restore it if needed.

3. Increase the PHP memory limit

If your website exceeds its allocated PHP memory, the server may return a 500 error. This often happens during large imports, backups, or after adding new functionality.

  1. Access your site files via FTP or File Manager.
  2. Locate the wp-config.php file if you use WordPress, or the php.ini file for other platforms.
  3. Add or edit the following line for WordPress:
    define('WP_MEMORY_LIMIT', '256M');
  4. Save the file and refresh your website.

4. Deactivate recently installed plugins or themes

Incompatible plugins or themes frequently trigger 500 errors after an automated update.

  1. Connect via FTP or File Manager.
  2. Navigate to your content folder, for example wp-content/plugins.
  3. Rename the folder of the plugin you suspect to pluginname_old.
  4. Refresh your website.
  5. If the error persists, rename the folder back and try the next plugin.
  6. To test your theme, rename the active theme folder in wp-content/themes to force the system to use a default theme.

5. Check file and folder permissions

Incorrect permissions can prevent the server from reading or executing scripts.

  1. Open File Manager or your FTP client.
  2. Right-click a folder and select File Permissions or Change Permissions.
  3. Set folders to 755.
  4. Set files to 644.
  5. Apply the changes and test the website.

Avoid setting permissions to 777, as this creates a security risk on shared hosting environments.

Troubleshooting

Database connection issues

A 500 error can occur if your website cannot connect to its database. This is common after a password change or database server outage.

PHP version mismatches

Running an outdated or incompatible PHP version can cause scripts to fail after a plugin or theme update.

When to escalate

If none of the steps above resolve the issue, the problem may be related to server configuration, a corrupted core file, or a hosting environment fault. In these cases, gather the following information before contacting support:

Remember — If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket