WordPress has a few particularly frustrating issues that tin completely shut down your site, only don't provide much guidance about what'due south causing the problem. The "The site is experiencing technical difficulties." error is one such consequence.

On its face up, it doesn't tell you much. Fortunately, in most cases, it is actually quite elementary to resolve. A few troubleshooting steps should have it taken care of in no fourth dimension.

In this article, we'll discuss where y'all might encounter this WordPress fault, as well as what causes it. Then nosotros'll walk you through vi steps for fixing it if it shows upwards on your own site.

Let'south jump right in!

An Introduction to the "The Site Is Experiencing Technical Difficulties." WordPress Error

"The site is experiencing technical difficulties." is a fatal WordPress error. This means that your website will be downward, and likely unavailable on both the frontend and backend. For your visitors, information technology may look like this:

The site is experiencing technical difficulties. error
"The site is experiencing technical difficulties." bulletin on the frontend

On the backend, the bulletin appears similar this:

The site is experiencing technical difficulties.
"The site is experiencing technical difficulties." message on the backend

A variation of this error in newer WordPress versions reads: "There has been a critical error on your website". Here'southward how it will announced on the frontend of your site:

critical error visitor
"There has been a critical fault on your site" message on the frontend

And here'due south the backend view:

critical error admin
"There has been a critical error on your site" message on the backend.

As you lot can run into, the newer variation is quite similar to the old one, apart from a slight deviation in wording.

Sometimes WordPress volition send an email to the site'due south administrator, with more than information about what may be causing the error. However, it'southward only as probable that you'll see this message with no explanation regarding why it appeared.

Nearly of the fourth dimension, this error is the outcome of a plugin or theme conflict. Due to WordPress' open-source nature, many different developers with various coding backgrounds and styles create extensions that users can add on to the platform.

Unfortunately, this means that sometimes plugins and themes from different developers don't play nicely with one another. When ii tools with alien code are both installed on a WordPress site, it can lead to a broad range of problems.

In some cases, i or both plugins volition simply end working. Other times, however, this kind of conflict can result in a fatal error such as the "The site is experiencing technical difficulties." message.

Is your WordPress site unreachable and showing 'The site is experiencing technical difficulties.' error message? Don't panic! Here'southward how to troubleshoot and become information technology back online fast 🤦‍♂️💪 Click to Tweet

How to Prepare the "The Site Is Experiencing Technical Difficulties." WordPress Error (In 6 Steps)

If y'all're already familiar with troubleshooting plugin conflicts, resolving the "The site is experiencing technical difficulties." error should be adequately piece of cake. If not, don't worry. Beneath, nosotros've included detailed steps for how to tackle this chore, equally well every bit what to practice if the problem persists.

Stride 1: Check Your Email for a Fatal Error Notification

Equally we mentioned earlier, in some cases WordPress volition send the site's admin an email containing more information about what may be causing the mistake:

technical difficulties email
Admin email for the "The site is experiencing technical difficulties." fault.

This email will include the following central pieces of information that tin help you troubleshoot the error faster:

  • The name of the plugin or theme causing the conflict
  • A link to put your site into 'recovery fashion'

Information technology is possible to troubleshoot the error without this information. Notwithstanding, it will require a lot of guesswork to determine which extension is causing the problem. If your site is using a large number of plugins, the process can become fourth dimension-consuming.

If yous're the site's admin and the "The site is experiencing technical difficulties." mistake bulletin includes the addendum: "Please check your site admin electronic mail inbox for instructions", it'south best to exercise then earlier proceeding (remember to try your spam binder too). Then follow the instructions for troubleshooting in recovery mode below.

However, if you're not the site's admin and they tin can't be reached, or if your fault bulletin doesn't say anything nearly an e-mail, never fearfulness. You can nevertheless follow the steps for troubleshooting using File Transfer Protocol (FTP) beneath.

Step 2: Troubleshoot for a Plugin or Theme Conflict

Due to the nature of WordPress' fatal errors, you won't exist able to admission the backend of your site to deactivate the extension that'south causing the problem. Depending on whether or not y'all have access to a recovery mode link, you'll take two options for working effectually this limitation.

Resolving a Conflict in Recovery Fashion

If you take access to a recovery mode link, click on it. This volition accept y'all to your site's backend, where you lot will be prompted to log in using your WordPress credentials:

recovery mode login to fix "The site is experiencing technical difficulties." error
The Recovery mode login folio

You do not have to use an admin account. If the site's administrator wants to transport the recovery mode link to another user and let them to troubleshoot the error, the latter party tin use their own credentials.

Information technology'south important to note that, while you're working in recovery fashion, the fatal error will persist for other users and your site'southward visitors. Only the user who logged in via the recovery mode link will be able to access the website normally.

In recovery way, the plugins and/or theme that WordPress has identified as causing the fault will be paused. They will also be identified in a banner notification at the top of the screen.

Click on the link to the Plugins screen to see the extensions involved in the conflict:

wordpress recovery mode
The WordPress recovery manner

Nether each plugin and/or theme'due south name, click on Deactivate:

recovery mode plugins
Deactivating a plugin in recovery manner

And then, select Exit Recovery Style in the admin bar:

exit recovery mode
Exiting recovery style

The problematic extensions will now exist deactivated for all users, and your site should be available to everyone again. Of course, y'all'll first want to check and brand sure that's the case. And so you lot can:

Subscribe Now

  • Delete the extension(due south) if they are not necessary for whatsoever cardinal functionality on your site.
  • Remove the conflicting plugin or delete the theme and replace it.
  • Contact the plugin or theme'southward developer and enquire if they tin edit the extension'south code to resolve the conflict. And then update and reactivate the new version.
  • Edit the tool's lawmaking to resolve the conflict yourself, and then reactivate it.

Specially if the plugin is popular, yous may accept expert luck working with the programmer to brand the necessary changes. It's worth noting, however, that you lot'll want to test all potential changes and new extensions on a staging site before implementing them on your live site.

Determining the Source of the Problem With FTP

If you can't access WordPress' recovery style, you can nonetheless troubleshoot a plugin disharmonize without access to the backend. To do and then, you'll need an FTP client also as your FTP credentials. You lot should exist able to discover the latter in your hosting account's profile:

kinsta ftp credentials
FTP credentials in the MyKinsta dashboard

Log into your site'southward server via your FTP customer, using your FTP credentials. And then navigate to wp-content > plugins:

filezilla plugins directory
The Plugins subdirectory in FileZilla

There yous'll discover subdirectories for each of your plugins. If you know which one is causing the problem, right-click on it and select Rename:

filezilla rename plugin
Renaming a plugin in FileZilla

Change the proper noun of the folder to something like "plugin-name-deactivated". This will prevent WordPress from finding the plugin'southward files:

filezilla deactivated plugin
A deactivated plugin in FileZilla

The plugin will at present exist deactivated, and you should be able to return to your site and access the backend normally. You can then deal with the problematic plugin every bit you meet fit, co-ordinate to the options we outlined in the previous section.

If you don't know which plugin is responsible for the fatal error, simply rename the outset one in the list. And so return to your site and refresh your browser to see if the upshot is resolved. Repeat this procedure, renaming your plugins one at a time, until the error goes away.

At that point, yous'll know that the last plugin you deactivated is the one causing the conflict. You tin then remove it or contact the programmer accordingly. This same procedure will piece of work for themes, and you'll find the relevant subdirectories in wp-content > themes.

Step 3: Ensure That You lot're Running a Supported Version of PHP

If your site is dorsum to normal subsequently completing Step 2, you tin can stop here. However, there's a hazard that troubleshooting for a plugin or theme conflict volition not resolve the "This site is experiencing technical difficulties" fault.

If that's the instance for you, your next motility should be to determine whether your site is using a supported version of PHP. Since WordPress 5.0, the platform no longer supports versions older than 5.6.20.

Additionally, the PHP developers themselves no longer provide back up for versions older than vii.iv.

Yous should exist able to determine which version of PHP your site is using by logging into your hosting account. Kinsta customers will find this information in their MyKinsta dashboards, by clicking on Sites in the sidebar:

mykinsta dashboard sites
Accessing your sites in the MyKinsta dashboard

The PHP version for each of your websites will be listed to the correct:

current php version
Viewing your current PHP version in the MyKinsta dashboard

If you lot're running an outdated version of PHP, you lot'll need to update it. The steps for this procedure may vary based on your hosting provider.

Kinsta customers can simply utilize our PHP Engine tool. To access it, click on the name of the site you want to update. So select the Tools tab:

Modifying your PHP version in the MyKinsta dashboard
Modifying your PHP version in the MyKinsta dashboard

Scroll down until you find the PHP Engine tool. Click on the drop-down card labeled Alter, and select the version you wish to upgrade to.

It's recommended that you run the latest PHP version available, for both security and functioning reasons. Once the update is consummate, render to your site to come across if the fatal error is resolved.

Step iv: Enable WordPress' Debug Style

If you're nevertheless seeing the "This site is experiencing technical difficulties" bulletin, you can attempt to diagnose the underlying outcome past using WordPress debug mode. This is some other built-in troubleshooting feature that volition reveal any underlying PHP errors.

To enable this feature, yous'll need to admission your wp-config.php file via FTP, and add the post-obit line of code correct before "That's all, finish editing! Happy publishing.":

          define( 'WP_DEBUG', true );        

Salve and re-upload the file, so return to your site and refresh the page. Peruse the error messages displayed in debug mode, and determine whether whatever of them might exist causing the fatal mistake. Y'all'll and then need to follow troubleshooting steps relevant to that issue.

It's of import to note that WordPress isn't meant to be left in debug style permanently. This manner should exist used for troubleshooting purposes only since it makes sensitive information potentially available to anyone.

To turn it off again, change the status in the wp-config.php code snippet from "truthful" to false", then save and upload the file once more.

Step 5: View Your Server's Error Log

If y'all don't see any suspicious messages in debug way, you lot can also check your server's mistake log. Y'all should exist able to access this via your hosting account. Kinsta customers can do then by selecting the Logs tab in the relevant site's profile:

kinsta error log
Accessing Error Logs in MyKinsta

From the drop-down carte, select mistake.log. Then look for any bug that may be causing the "This site is experiencing technical difficulties" message, and troubleshoot them as necessary.

Footstep six: Contact Your Hosting Provider

If y'all've wearied all of the above steps, and you notwithstanding haven't been able to eliminate the "This site is experiencing technical difficulties" error in WordPress, then it's time to bring in some help. The upshot may lie with your server and exist unreachable without assistance from your host.

Therefore, you'll want to contact your hosting provider past whatever means they offer. Kinsta customers can accomplish our support team 24/7 via chat, email, or our Contact page.

Summary

"The site is experiencing technical difficulties." error in WordPress can be a frustrating consequence. Vague alerts that give y'all little indication as to what's causing the problem can be especially hard to fix.

Fortunately, you tin resolve this particular consequence in vi steps or less:

  1. Cheque your email for a fatal error notification.
  2. Troubleshoot for a plugin or theme disharmonize.
  3. Ensure that you're running a supported version of PHP.
  4. Enable WordPress' debug mode.
  5. View your server's error log.
  6. Contact your hosting provider.

Save time, costs and maximize site functioning with:

  • Instant help from WordPress hosting experts, 24/seven.
  • Cloudflare Enterprise integration.
  • Global audience achieve with 32 data centers worldwide.
  • Optimization with our congenital-in Application Performance Monitoring.

All of that and much more, in 1 program with no long-term contracts, assisted migrations, and a thirty-solar day-money-dorsum-guarantee. Cheque out our plans or talk to sales to find the plan that'due south right for you.