Skip to article content

WordPress error 500: what it means and what to do if your site won’t open

Seeing “There has been a critical error on this website” or error 500 in WordPress? What to check after an update or code change, and how to fix it.

Do you see “There has been a critical error on this website”?

This notice means WordPress detected a serious error that prevents normal operation. It can appear after updating WordPress, a plugin that adds features, or the theme that controls the site’s design. It can also follow a code change. The notice alone does not identify the cause.

In the default WordPress error screen, this message accompanies an HTTP 500 response, even when the number is not shown to visitors. You do not have to recognise the code to start investigating: the visible message and recent change already help identify the situation.

The “Learn more about troubleshooting WordPress” link opens help documentation; it does not automatically repair the site. Fixing the failure involves identifying its cause and applying the appropriate correction. If administration is inaccessible too, see the section about access and the recovery email.

What an error 500 means in WordPress

An error 500 means the server ran into a problem while trying to load a page or carry out an action on the website. It may appear as “500 Internal Server Error” or “HTTP ERROR 500”. The message establishes that something failed, but does not identify what needs fixing.

The definition of HTTP status 500 is general rather than specific to WordPress. Seeing it on your site does not establish that the hosting service is down or that a particular plugin caused the problem.

Resolving it involves connecting the error with the website’s action, recent changes and the details recorded by the server. Those details help your team decide what needs fixing and whether restoring an earlier version would help.

If it followed an update or code change, start with that change

You may have just updated a plugin, edited the theme or added a custom function. That change is a useful starting point, although its connection to the failure still needs checking.

  1. Identify what changed. Record the component or file, approximate time and previous version if known.
  2. Establish which areas fail. Does the error affect the whole site, one page or only administration? For a public page, a private browser window can help compare what a visitor sees.
  3. Avoid piling up more changes. Coordinate the review with the person maintaining the site so you can identify which action corrects the problem.
  4. Keep a copy of the current state. Before replacing files or recovering a version, establish which backup or change history supports the recovery and which later changes must be retained.

If an update never finished, use the guide to WordPress update problems as well. An incomplete installation needs a different review from code failing after an update has completed.

Where to find your website’s error log

The browser’s error page often reveals little. The next step is to consult the hosting error log, which records failures with their time and, where available, the file or process involved. Its location depends on the provider; hosting support can help you find it.

Work with the team to find the entry matching the time and page that failed. A file, line of code or resource limit can guide the investigation. A plugin name in a log is a clue to interpret alongside the rest of the message, not an automatic reason to delete the plugin.

WordPress offers diagnostic tools when more detail is needed. Its official debugging documentation distinguishes logging errors from displaying them to visitors and recommends preparing a backup or separate test environment. The technical team can collect the necessary detail without publishing notices or sharing complete logs containing private information.

How to fix an error 500 once its cause is understood

The right fix depends on the cause. This table explains what to check and what can be done once the source of the error has been confirmed. The MDN reference for status 500 describes different causes, including execution errors, configuration, permissions and memory.

What to investigate and how to approach a fix
Confirmed situationWhat to checkPossible fix
A plugin or theme fails when its code runsThe recorded error, versions and connection with the recent change.Correct the incompatibility or temporarily isolate the component to check its effect.
An edited file contains a coding errorThe identified file and line, compared with the previous version.Correct the code or recover the last working version of that file.
The server identifies a configuration errorThe rules or permissions named in the log.Correct that setting or recover a valid configuration while retaining necessary rules.
The log confirms that available memory was exhaustedThe process consuming memory and the available limit.Address the consumption and assess the appropriate limit with hosting support.

If the problem involves a plugin or theme

When administration is accessible and the change is identified, temporarily deactivating the component can help test the connection. Consider which function would become unavailable first. If the site opens again, the work continues: review compatibility and dependencies, and test the correction before reactivating the component. Deleting every plugin is not a general solution.

If recently edited code caused the error

Recovering the file’s last working version can restore the previous state while the code is corrected in a test copy. Use a version you can identify in a backup or change history. If only code changed, do not routinely restore the database as well: that could replace content or settings you want to keep.

If configuration or resources are involved

On servers using Apache, incorrect rules in .htaccess can contribute to the failure. The team should check this and retain necessary redirects and protections when correcting it. Not every installation uses that file. WordPress lists configuration and memory among the checks in its common errors guide; they are not settings to change whenever a 500 appears.

What to do if you cannot access administration either

If /wp-admin/ also fails, you cannot use the WordPress dashboard, but that does not mean the files or content have disappeared. Hosting support or the person maintaining the site can use authorised hosting tools to access the files and review the log.

Check the site administration email and Recovery Mode

Check the mailbox configured as the WordPress administration email address, including spam. If a Recovery Mode link has arrived, you can use it to log in and inspect the identified component. This mode may pause the component only for your session: the failure still needs fixing and the site needs checking after you exit. If the email does not arrive, support can continue through the hosting tools. The official Recovery Mode guide explains the process.

The person maintaining your site can inspect the affected file or plugin through the hosting tools. If restoring an earlier version would help, they should first check that the backup is reliable. If no backup is available, the problem will need another fix. Avoid replacing files with versions from unknown sources or without checking compatibility.

If a full backup recovery is proposed, review what the backup includes and which information will be recovered. The aim is to get the site working again without losing recent content or settings that need to be kept.

An example: the site stops opening after a function is changed

Fictional example: a theme function is edited and, after the file is published, the website starts showing an error 500. Administration stops opening too.

The hosting log connects the failure to a syntax error in the newly edited file. After checking the backup, the person reviewing the site restores the previous working version of that file. The change is then corrected and tested separately before being published again.

In this example, reinstalling WordPress or replacing the database would not appropriately address the cause. Identifying the changed file and confirming its error provides the useful next step. Another website showing the same 500 message could need a different fix.

How to check that the fix worked

Return to the address and action that produced the error. Check administration access and the functions depending on the corrected component as well. A working homepage is encouraging, but the specific failing page may still need attention.

The team can establish that the request no longer returns a 500 and that the same failure is not logged again during the test. For an intermittent error, retain the conditions under which it appeared and agree an observation period: one successful visit is not enough to establish that it is resolved.

Record the confirmed cause, applied change and checks performed. For future modifications, keeping a recoverable copy and testing significant changes before publication makes the work easier to manage.

If you need help reviewing the error

Share the message you see, when it started and what changed beforehand. If you have contracted maintenance or hosting support, use that channel to coordinate recovery.

You can also tell us what is happening with your WordPress site. We can help you decide what to do next. If you need us to investigate, we will explain the proposed work and agree a timeframe with you before we begin. If errors recur, reviewing maintenance and the way changes are applied can help you decide what needs improving.