Fix Your Sites Experience Technical Difficulties
WordPress has a few very annoying bugs that can completely shut down your site, but it doesn’t give you much information about what’s causing the problem. One such issue is the error “The site is experiencing technical issues.”
On the surface, it doesn’t reveal anything. Fortunately, most of the time, it is pretty simple to fix. With a few troubleshooting procedures, you should be good to go in no time.
We’ll go over where you might notice this WordPress problem and what causes it in this article. Then, if it appears on your own site, we’ll lead you through six steps to remedy it.
Let’s get started!
Contents Table of Contents
An Introduction to the “The Site Is Experiencing Technical Difficulties.” Error in WordPress
How to Get Rid of “The Site Is Having Technical Issues.” Error in WordPress (In 6 Steps)
The “Site Is Experiencing Technical Difficulties” section begins with an introduction. Error in WordPress
A deadly WordPress error is “The site is having technical issues.” This means that your website will be unavailable on the frontend as well as the backend. It could appear like this for your visitors:
There are some technical issues with the site. error
On the frontend, a notification reads, “The site is experiencing technical issues.”
The message looks like this on the backend:
There are some technical issues with the site.
On the backend, a notification reads, “The site is experiencing technical issues.”
“There has been a significant mistake on your website,” states a variation of this message in recent WordPress versions. This is how it will appear on your site’s frontend:
visitor with a critical mistake
On the frontend, the notice “There has been a critical issue on your site” appears.
Here’s a look at the backend:
admin critical error
On the backend, you’ll get a notification that says, “There was a critical error on your site.”
The updated variation, as you can see, is very identical to the previous one, with the exception of a tiny alteration in language.
WordPress will occasionally send an email to the site’s administrator with more details about the mistake. It’s also possible that you’ll receive this warning with no explanation as to why it arrived.
The most common cause of this problem is a plugin or theme conflict. Because WordPress is open-source, many different developers with diverse coding backgrounds and styles create extensions for users to use.
Unfortunately, this implies that plugins and themes from various authors don’t always work well together. When two tools with incompatible code are installed on the same WordPress site, it can cause a slew of problems.
One or both plugins may simply stop operating in some instances. However, in some cases, a disagreement like this can result in a fatal error, such as the notice “The site is having technical difficulties.”
Is your WordPress site down and displaying an error message that reads, ‘The site is experiencing technical issues.’ Don’t be alarmed! Here’s how to troubleshoot it and get it up and running again quickly:
TO TWEET, CLICK HERE
How to Fix the “The Site Is Experiencing Technical Difficulties.” WordPress Error (In 6 Steps)
How to Get Rid of “The Site Is Having Technical Issues.” Error in WordPress (In 6 Steps)
Resolving the “The site is experiencing technical issues.” error should be quite simple if you’re already familiar with troubleshooting plugin incompatibilities. Don’t worry if you don’t. We’ve included step-by-step instructions for completing this task, as well as what to do if the problem persists.
Step 1: Look for a Fatal Error Notification in your email.
As previously stated, WordPress will occasionally send an email to the site’s administrator with further information about what may be causing the error:
issues with technology For the “The site is experiencing technical issues.” error, send an email to the Admin email address.
The following critical pieces of information will be included in this email to assist you in troubleshooting the situation more quickly:
The name of the plugin or theme that is creating the issue.
A link that will place your site in’recovery mode.’
Without this information, troubleshooting the error is possible. However, determining which extension is causing the issue will need a lot of guesswork. If you have a lot of plugins on your site, the procedure can take a long time.
It’s advised to check your site admin email inbox for instructions if the “The site is experiencing technical issues.” error notice includes the addendum: “Please check your site admin email inbox for instructions” (remember to try your spam folder as well). Then, in recovery mode, follow the troubleshooting procedures below.
Never fear if you aren’t the site’s administrator and they can’t be reached, or if your error notice doesn’t mention an email. You can still troubleshoot utilizing File Transfer Protocol (FTP) by following the steps below.
Step 2: Look for a conflict between a plugin and a theme.
You won’t be able to enter the backend of your site to deactivate the extension that’s causing the problem because of the nature of WordPress’ fatal errors. You have two possibilities for getting past this constraint, depending on whether or not you have access to a recovery mode link.
In Recovery Mode, Resolving a Conflict
If a recovery mode link is available, select it. This will lead you to the backend of your site, where you’ll be asked to log in with your WordPress credentials:
To fix, log in to recovery mode. “There are technical issues with the site.” error
The login page for recovery mode
You are not need to utilize an administrator account. The site administrator can transmit the recovery mode link to another user, who can then use their own credentials to troubleshoot the mistake.
It’s vital to remember that while you’re in recovery mode, the fatal mistake will continue to affect other users and visitors to your site. Only those who accessed the website through the recovery mode link will be able to do so normally.
The plugins and/or theme that WordPress has recognized as causing the error will be suspended in recovery mode. A banner notification at the top of the screen will also identify them.
To see the extensions involved in the dispute, click the link to the Plugins screen:
recovery mode for wordpress
WordPress’s restoration mode
Click Deactivate: under the name of each plugin and/or theme.
plugins for recovery mode
In recovery mode, deactivating a plugin
Then, in the admin bar, select Exit Recovery Mode:
get out of recovery mode
Getting out of recovery mode
All users will now have the troublesome extensions disabled, and your site should be accessible to everyone again. Of course, you’ll want to double-check that this is the case. After that, you can:
Do you want to discover how we grew our traffic by over 1000%?
Join the 20,000+ people who receive our weekly email with WordPress insider secrets!
Now is the time to subscribe.
If the extension(s) aren’t required for any vital functionality on your site, remove them.
Remove the incompatible plugin or delete and replace the theme.
To resolve the conflict, contact the plugin or theme’s developer and ask if they can update the extension’s code. Then reactivate and upgrade the new version.
To resolve the disagreement, edit the tool’s code and then restart it.
You might have better chance working with the developer to make the necessary changes, especially if the plugin is popular. It’s worth emphasizing, though, that you should test all prospective changes and new extensions on a staging site before putting them into production.
Using FTP to find the source of the problem
You can still troubleshoot a plugin conflict even if you don’t have access to WordPress’ recovery mode. You’ll need an FTP client and your FTP credentials to do so. You should be able to find the latter in the profile of your hosting account:
ftp credentials kinsta
In the MyKinsta dashboard, you’ll find FTP credentials.
Using your FTP credentials, log into your site’s server using your FTP client. After that, go to wp-content > plugins:
directory of filezilla plugins
FileZilla’s Plugins subfolder
There are subdirectories for each of your plugins in this directory. If you know which one is the source of the issue, right-click it and choose Rename:
Plugin for renaming files in Filezilla
In FileZilla, you can rename a plugin.
Make the folder’s name something like “plugin-name-deactivated.” WordPress will be unable to find the plugin’s files as a result of this:
The plugin for Filezilla has been deactivated.
In FileZilla, a plugin that has been disabled.
The plugin will now be disabled, and you should be able to access the backend of your site regularly. Then, using the choices given in the last section, you can deal with the troublesome plugin as you see fit.
If you’re not sure which plugin is causing the fatal error, just rename the first one on the list. Then go back to your site and refresh your browser to see whether the problem has gone away. Rep this procedure, renaming your plugins one by one, until the error is no longer present.
The last plugin you deactivated will be the one creating the conflict at that moment. You can then either delete it or contact the developer. The same procedure applies to themes, and the required subdirectories may be found in wp-content > themes.
Step 3: Make Sure You’re Using a PHP Version That’s Supported
You can end here if your site is back to normal after finishing Step 2. However, checking for a plugin or theme incompatibility may not be enough to fix the “This site is having technical difficulties” error.
Do you have troubles with downtime with WordPress? Kinsta is a hosting solution that prioritizes performance and security. Take a look at our plans.
If that’s the case, your next step should be to see if your site is running on a supported PHP version. WordPress hasn’t supported versions older than 5.6.20 since version 5.0.
Furthermore, PHP’s developers no longer provide support for versions older than 7.4.
By login into your hosting account, you should be able to see which version of PHP your site is using. Customers can obtain this information by clicking on Sites in the sidebar of their MyKinsta dashboards:
Sites with mykinsta dashboard
In the MyKinsta dashboard, you may access your sites.
To the right, you’ll see the PHP version for each of your websites:
PHP version currently in use
In the MyKinsta dashboard, you can see your current PHP version.
You’ll need to update PHP if you’re still using an old version. Depending on your hosting provider, the stages for this process may differ.
Our PHP Engine tool is available to Kinsta clients. To use it, go to the name of the site you wish to update and click on it. After that, go to the Tools tab:
In the MyKinsta dashboard, you can change your PHP version.
Scroll to the bottom of the page until you see the PHP Engine tool. Select the version you want to upgrade to from the drop-down option labeled Modify.
For security and efficiency reasons, you should use the most recent PHP version available. Return to your site after the upgrade is complete to see if the fatal error has been repaired.
Step 4: Enable the Debug Mode in WordPress.
If the “This site is having technical issues” message persists, you can use WordPress debug mode to try to figure out what’s wrong. Another built-in troubleshooting feature that will identify any underlying PHP issues is this one.
To enable this feature, FTP into your wp-config.php file and add the following line of code just before “That’s all, quit editing!” “Good luck with your publishing.”:
define(‘WP DEBUG’, true); define(‘WP DEBUG’, true); define(‘WP DE
Return to your site and refresh the page after saving and re-uploading the file. Examine the error messages presented in debug mode to see if any of them could be the source of the catastrophic issue. Then you’ll need to follow the troubleshooting instructions for that issue.
It’s crucial to remember that WordPress isn’t designed to be run in debug mode all of the time. Because it makes sensitive information potentially accessible to anybody, this mode should only be used for debugging.
Change the status in the wp-config.php code snippet from “true” to “false,” then save and submit the file again to turn it off.
Step 5: Check the Error Log on Your Server
If you don’t see any strange messages in debug mode, examine the error log on your server. This should be accessible through your hosting account. Customers using Kinsta can do so by going to the Logs tab in the relevant site’s profile:
log of kinsta errors
Using MyKinsta to View Error Logs
Select error.log from the drop-down selection. Then, if necessary, troubleshoot any issues that may be producing the “This site is experiencing technical difficulties” message.
Step 6: Get in Touch With Your Web Hosting Provider
If you’ve tried everything above and still can’t get rid of the “This site is experiencing technical issues” error in WordPress, it’s time to seek professional assistance. The problem could be with your server, and you won’t be able to reach it without help from your host.
As a result, you should contact your hosting provider via any channels they provide. Customers can contact our support team by chat, email, or our Contact page at any time.
In WordPress, the “The site is having technical issues.” error can be an irritating problem. It’s extremely difficult to fix vague alarms that give you no clue of what’s causing the problem.
Fortunately, you can address this problem in as few as six steps:
Check your email for a notification of a fatal error.
Look for a conflict between a plugin and a theme.
Make sure you’re using a supported PHP version.
Enable the debug mode in WordPress.
Examine the error log on your server.
Make contact with your web hosting company.
Save time, money, and improve site performance by using:
Expert WordPress hosting assistance is available 24 hours a day, 7 days a week.
Integration with Cloudflare Enterprise.
With 29 data centers across the world, we can reach a global audience.
With our built-in Application Performance Monitoring, you can improve your performance.
All of this and more is included in a single plan that includes no long-term obligations, aided migrations, and a 30-day money-back guarantee. Check out our plans or speak with a sales representative to find the ideal plan for you.