Failed to Recieve Download List. This May Be Due to Busy Server. Please Try Again Later
Running into errors on your WordPress site tin exist intimidating. However, most errors requite you some clue as to what caused them, which can make troubleshooting these common issues a lot easier. The 503 mistake is non as polite, unfortunately, and doesn't give you much data to become on.
Information technology helps to understand what the well-nigh common causes are for the 503 error in WordPress. Later that, you'll need to be methodical when it comes to troubleshooting the error, which means following several steps in order to locate the root crusade.
What's the HTTP 503 Service Unavailable Error?
The 503 fault in WordPress signifies that your website can't exist reached at the present moment because the server in question is unavailable. This could happen because it's too decorated, under maintenance, or something else which requires a deeper analysis.
In this article, we'll cover what the 503 error is and how information technology typically manifests. Then we'll guide you through half-dozen steps in lodge to troubleshoot it. Permit's become to piece of work!
What Is an HTTP Mistake 503?
The Cyberspace Technology Task Force (IETF) defines the 503 Service Unavailable as:
The 503 (Service Unavailable) condition code indicates that the server is currently unable to handle the asking due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay. The server MAY send a Retry-Subsequently header field to suggest an appropriate amount of time for the client to await before retrying the request.
When you see the 503 mistake, information technology ways that the server in question is unavailable. That could be because it'southward as well busy, for example, or it's under maintenance. Unlike other similar error codes, 503 signifies that your website is online and running, just can't exist reached at the present moment.
What'due south so vexing about this item error is that it barely gives you any information to keep. Nearly of the time, it only shows up with a "Service temporarily unavailable" message. That's the equivalent of calling a eating place via phone, only to have them tell you that they're closed merely decline to allow yous know when they'll be open up once again.
If you're lucky, the 503 error code will have occurred considering your WordPress website is nether maintenance. WordPress very briefly sets your site to maintenance fashion when you're updating a plugin, a theme, or the core software:
Usually, this timeout is so cursory that no one will observe information technology. Notwithstanding, in those cases where the 503 error persists, you'll have a bigger problem to bargain with. After all, not only will users be unable to visit your site, simply yous'll lose access to your WordPress admin expanse besides. That means y'all can't update your site in any fashion, and in social club to troubleshoot it, you'll need to dig into its files.
503 Error Variations
The 503 error can testify upward in a lot of ways. All the same, almost every variation comes accompanied by that 503 code, making it easy to identify.
Here are some of the variations you might come across, depending on your server configuration and browser:
- 503 Service Unavailable
- 503 Service Temporarily Unavailable
- HTTP Server Mistake 503
- HTTP Error 503
- Error 503 Service Unavailable
- The server is temporarily unable to service your request due to maintenance reanimation or chapters problems. Delight effort again later.
Whatever the code you run into might look like, it ways you lot need to become to work fast before it affects your users negatively.
How to Fix the 503 Fault in WordPress (six Steps)
Since you oft can't be sure what caused the 503 error in any given situation, you'll need to become most troubleshooting it methodically. The following 6 sections each embrace a potential fix, aimed at resolving the different potential root causes.
After each footstep, accept a moment to render to your website and see if the 503 fault is gone. If it is, yous've successfully fixed the event. If non, go on on to the side by side stride in the process.
one. Temporarily Deactivate Your WordPress Plugins
One of the most common causes of the 503 error in WordPress is plugin compatibility issues. To decide if that's what'south happening, you'll need to disable all of your site'south plugins.
Since the 503 error prevents you from accessing the WordPress admin area, you'll need to use an FTP client for this footstep. If yous don't have i ready up, we recommend FileZilla.
In one case your FTP customer is ready, connect to your website through it and navigate to your WordPress root folder. In case y'all can't observe it, it's usually called public_html, html, public, www, or your site's name. If you're a Kinsta client, it's your public folder.
Open up that binder, and navigate to the wp-content directory. Inside, y'all'll meet a folder called plugins, which contains individual subdirectories for each of the plugins installed on your site (both active and inactive).
What you're going to practice at present is right-click on the plugins folder, and rename it to something else. We recommend plugins.old or plugins.deactivated, so you lot can easily recognize it subsequently.
WordPress will at present not be able to find whatever of your plugins. When that happens, it will automatically disable those plugins.
Now, attempt accessing your WordPress dashboard. If the 503 error is gone, then you can presume that 1 of your plugins was the culprit. All you take to do is figure out which one was at error.
Render to the wp-content directory, and rename your original plugins binder correctly. So, you'll need to disable each of your plugins one past 1, until you find the culprit.
To do this, open the wp-content/plugins directory. Inside, you lot'll find one folder for each of your plugins. The process you're going to follow is much the same as before:
- Start with the first folder, and rename it to anything you lot like.
- Bank check your website to see if the error is gone.
- If it isn't, return the plugin folder from the previous step to its original name.
- Motion on to the next plugin on your listing, repeating the above steps.
This process can take a while if you have a lot of plugins, but it'due south vital to check each plugin in turn. If at any point yous identify the plugin that's causing the error, you lot can uninstall it or supervene upon it with another tool.
If you brand it to the end of these steps without finding a solution, you can move on to the next phase of troubleshooting.
two. Deactivate Your WordPress Theme
Now that y'all've ruled out your plugins as the crusade of the 503 error, information technology'due south time to do the same with your active theme. In fact, your theme could also be creating compatibility issues.
Unfortunately, the process doesn't work the aforementioned every bit above. WordPress won't revert to the default theme if simply rename the theme folder, y'all would end upward with an fault like "The theme directory "theme name" does not exist." Or if you attempt to rename the entire theme directory folder, you end up with "ERROR: The themes directory is either empty or doesn't exist. Please bank check your installation."
Therefore, you lot demand to access your WordPress database by logging into phpMyAdmin. If you're a Kinsta customer, this can be found within the "Info" section of the MyKinsta dashboard.
Click into the "wp_options" tabular array, and then click on the "Search" tab. You lot will want to search nether the "option_name" for template.
Under the "option_value" column you volition see the current name of your theme. Alter this to one of the default themes, such as "twentynineteen."
Subscribe Now
Check your website once again to see if this has fixed the error. If information technology did, information technology simply means information technology's a problem with your WordPress theme and yous might want to effort reinstalling it or reverting to your about contempo backup.
3. Temporarily Disable Your Content Delivery Network (CDN)
Sometimes, the 503 error will show up non because of a problem on your website, but because of your Content Delivery Network (CDN). If you're using a CDN, a quick style to figure out if that'due south the instance is to temporarily disable information technology.
Every CDN should include some feature that enables you to pause its services. If yous're on Kinsta, you tin can disable your Kinsta CDN by navigating to CDN → "Disable CDN" inside your MyKinsta dashboard:
The process you need to follow may be dissimilar depending on which CDN you're using. Cloudflare has also been known to cause 503 errors sometimes. If you can't find the option to pause yours, check out your service's knowledge base, which will usually comprise detailed instructions.
If you don't use a CDN or find that pausing your service doesn't help with your consequence, at that place are still a few more than fixes to effort. Exercise remember to reactivate your CDN before moving on.
iv. Limit the WordPress 'Heartbeat' API
The WordPress Heartbeat is an API built into WordPress, which the platform uses for auto-saving content, showing you plugin notifications, letting you know when someone else is working on a post you're trying to access, and more.
But like a regular heartbeat, the API works in the background with a high frequency then that it doesn't miss annihilation. As you might imagine, this API consumes server resources. Unremarkably, that's not a problem just in some cases, it may pb to a 503 mistake if your server tin't handle the load.
The quickest manner to determine if the Heartbeat API is at the centre of your problems is to temporarily disable it. To do that, connect to your WordPress website via FTP one time more than, and and so open up your current themes folder and look for the functions.php file within:
Right-click on the file and select the View/Edit choice, which will open up information technology using your local text editor. In one case it's open up, you'll need to add together the following lawmaking snippet inside:
add_action( 'init', 'stop_heartbeat', 1 ); function stop_heartbeat() { wp_deregister_script('heartbeat'); } Those 3 lines of lawmaking tell WordPress to disable the Heartbeat API. Save the changes to the functions.php file, close information technology, and effort to access your website again.
If the 503 error is gone, you'll know that the API was the problem. Disabling it altogether removes a lot of useful functionality, all the same. Instead, we recommend that you lot 'slow downwards' the Heartbeat, and then that it doesn't crusade issues.
The easiest fashion to do that is by installing the Heartbeat Command plugin. Activate the plugin and navigate to the Settings > Heartbeat Control section. Expect for the Modify Heartbeat options, and driblet the frequency to the lowest possible number:
Save the changes to your settings and return to the functions.php file you tweaked a while dorsum. For the higher up changes to work, you'll need to remove the cord of code you added earlier and save your changes to the file.
At this stage, the 503 error should exist gone if the Heartbeat API was the problem. If it isn't, then it's time to endeavour something different.
5. Increase Your Server's Resources
If the 503 error is still occurring despite all your attempts to set up it and then far, then in that location's a expert chance the problem might be due to a lack of server resources. That is to say, you lot'll need to upgrade your hosting programme to see if that fixes the outcome. This is peculiarly true if you're using inexpensive WordPress hosting, as they tend to throttle resources. We don't do this at Kinsta.
Upgrading your plan is a big decision, however. The smart move is to showtime contact your web hosting back up service and hash out the 503 error with them, as well equally the steps yous've taken and then far to try and solve it. The support team should exist able to help you work out the cause and suggest you lot on whether you lot need to upgrade your program or not.
At Kinsta, our back up team is more happy to have a expect for you lot. We tin even temporarily enable New Relic to see if we tin pinpoint the result down to something on your site that is causing the trouble.
6. Review Your Logs and Enable WP_DEBUG
Yous should also take advantage of your error logs. If you're a Kinsta customer, yous can easily see errors in the log viewer and enable WordPress debug style in the MyKinsta dashboard. This tin can help you lot quickly narrow down the effect, specially if it'southward resulting from a plugin on your site.
If your host doesn't take a logging tool, yous tin can as well add the following code to your wp-config.php file to enable logging:
define ( 'WP_DEBUG' , true ) ; define ( 'WP_DEBUG_LOG' , true ) ; define ( 'WP_DEBUG_DISPLAY' , false ) ; The logs are typically located in the /wp-content directory. Inside it, await for a file called debug.log and open it up.
Others, like here at Kinsta might have a defended folder called "logs".
Interpreting your debug log can be a chip intimidating but it's not as difficult to read as you might imagine. In a nutshell, the log contains each error that pops up on your site in chronological society. It shows which file caused each error, as well as which specific lines of code were involved.
Beware: you're non going to find direct references to the 503 error inside your log. Even and then, if all else fails, it tin can betoken you lot in the right direction past showing you lot what files are causing problems. That way, you'll know where to focus your efforts side by side. As we mentioned in the previous step, now is a good fourth dimension to go far touch on with your hosting provider if you demand farther assistance resolving this error.
You can also cheque the log files in Apache and Nginx, which are commonly located here:
- Apache: /var/log/apache2/error.log
- Nginx: /var/log/nginx/error.log
To learn more, please check out our web server showdown: Nginx vs Apache.
If you lot're a Kinsta client you can besides take advantage of our analytics tool to get a breakdown of the total number of 503 errors and encounter how often and when they are occurring. This tin can help you troubleshoot if this is an ongoing upshot, or mayhap something that has resolved itself.
If the 503 error is displaying because of a fatal PHP error, you lot can as well try enabling PHP error reporting. Simply add the following code to the file throwing the mistake. Typically yous tin can narrow downwards the file in the console tab of Google Chrome DevTools.
ini_set ( 'display_errors' , 1 ) ; ini_set ( 'display_startup_errors' , one ) ; error_reporting ( E_ALL ) ; And yous might need to also modify your php.ini file with the following:
display_errors = on Summary
If yous're lucky, the 503 error will just evidence upwardly when you put your website into maintenance manner. Withal, if it appears without alert, then you'll have to ringlet upwards your sleeves and practise some troubleshooting.
To get at the root crusade of the 503 mistake, you'll demand to follow these steps to fix it:
- Temporarily deactivate your WordPress plugins.
- Conciliate your WordPress theme.
- Disable your CDN.
- Limit the WordPress Heartbeat API.
- Increase your server resource.
- Review your logs and enable WP_DEBUG.
Take you ever run into the HTTP 503 fault in WordPress? Share your experiences with united states of america in the comments section beneath!
Save fourth dimension, costs and maximize site performance with:
- Instant aid from WordPress hosting experts, 24/seven.
- Cloudflare Enterprise integration.
- Global audience reach with 29 data centers worldwide.
- Optimization with our congenital-in Application Performance Monitoring.
All of that and much more than, in one plan with no long-term contracts, assisted migrations, and a xxx-day-money-back-guarantee. Check out our plans or talk to sales to detect the plan that'due south right for you lot.
Source: https://kinsta.com/blog/http-error-503/
0 Response to "Failed to Recieve Download List. This May Be Due to Busy Server. Please Try Again Later"
Post a Comment