Что значит ошибка error 503 backend fetch failed

Error 503 Backend Fetch Failed error conveys the message that the server of the internet website is not operating. It is a standard Hypertext Transfer Protocol response pop up shown by internet servers. To assure the development of a Magento, some system contributes and make it easy for the corporation to utilize and pinpoint where the difficulty lies when a website is not running as demanded.

Error 503 Backend Fetch Failed error occurs when the connection closes before Fastly cache servers are done reading the response. Error 503 Backend Fetch Failed error generally occurs when there is a removed or void Content and Length header on the response option, although there may be other sources leading to the failure.

What leads to the Error 503 Backend Fetch Failed

The error may be an aftereffect of the server not having sufficient memory, or it may be the case that there is an excessive number of solicitations lining up. The accident of the application pool, which serves the site, could be another explanation behind the event of the blunder.

The application may crash multiple times in less than five minutes, a speedy come up short happens, which results in the application pool being put out of activity by the IIS. The expiry of the SSL affirmation is known to cause the “error 503 backends fetch failed” error.

Back to the subject, the status code of this error is 500 and is what might be compared to inward server mistake. This blunder happens on all internet browsers and every working framework, even on cell phones.

Method #1 Refresh and Update the Webpage

Sometimes just refreshing the page again will control the problem. To solve it, follow the steps one by one:

1. Go to the website and sign in. For that website accessibility is needed further navigated to Host Server by using an FTP Client like “FileZilla” or Using Website Host cPanel “Document administrator”.
2. After that go to the Magneto site pull registry and look for the account “maintenance. Flag.” Make sure you erase it.
3. Refresh the Magento site. If the error is still there then try an alternate refresh solution.  Refresh the website page or press F5 to do proceed. While the 503 issue is a concern of another PC, it may be a precise issue and once in a while, refreshing can help remove the error.

See Also: 4 Ways to Fix the NET::ERR_CERT_AUTHORITY_INVALID Error

Method #2 Rectify using Reboot

Rectify by rebooting the switch and for instance, rebooting the device you are using. I the code titled “Administration Unavailable – DNS Failure” is popping up at that point a reboot of the framework on your side will complete the rest of the work. This is on the grounds that occasionally the error is because of issues with the DNS server, which can be rectified with a reboot.

Method #3 Contact the official Administrators

Directly contact the website for guidance. In most cases, the website’s administrators already know about the 503 error, but you should let them know or verify the status of the problem to confirm. See our Website Contact Information list for contact information for popular websites. Most sites have support-based social network accounts and some even have phone numbers and email addresses.

Method #4 Estimate the Total Memory Usage

The amount of memory that Varnish will use depends on the number of requests it receives. Higher the number of requests, higher memory consumption. Initially look for the Hosting Support Engineers at the official link, https://bobcares.com/dedicated-support/

After that, do a proper examination of the number of website visitors on the server. Then, measure the total memory routine. And, we add supplementary memory for varnish cache to avoid further difficulties.

Method #5 Look for the Varnish Interface

Similarly, the Hosting Support Engineers make sure to adjust the varnish port, IP address and other domains from the CentOS Web Panel.

And, when there is large pressure in the server even after the configuring once again the Varnish cache, one can disable the Varnish cache from the CentOS web panel (CWP). To do such, follow some simple steps with a blink of an eye:

1. Go to CWP and Login
2. Look for Apache Settings from the menu drop-down
3. Transform the Webservers

Method #6 Keep Patience and Wait for a While

Sometimes the error occurs due to overuse of the device. Keep Patience and try again fixing again later. ”Error 503 backend fetch failed” is particularly consistent when there is a server load caused by many visitors and individuals like one of us.

The best approach in such a case is to delay and try again after a short period of time. Once the site is free and devoid of many users, this error goes away.

Method #7 Look for the Plugins

A key source to the error 503 issue is the Varnish plugin or its absence. On the off chance that you have the problem on your site, check if the Varnish plugin’s power is on. For those of you who don’t have the foggiest idea, Varnish comes in use to build the speed of the site and is also in use by facilitating firms. If the module is empowered on the server, well, the facilitating firm needs a call.

In today’s modern world, where our lives are in tangles with social media, why can’t we get errors in our laptop fixed by using this platform only. There are a lot of links on youtube that provides solutions with video tutorials to fix a technical issue.

One such tutorial video to fix this error can be learn through is upload by the Naiwik Tech Vlogger. There is a chance that the issue is with your PC but the chances of this are very moderate.

According to this tech vlogger, your Magento installation will illustrate the following code: “Error 503: Service Temporarily Unavailable” page after you’ve set up or refreshed as an extension by utilizing Magento Connect.

In addition to this, the error happens because the website is change into support mode by “maintenance.flag” file within the Magento website root directory. You have to switch to “maintenance.flag” to solve this issue.

Method #9 Reset the Router and Restart

Sometimes there is a chance that a DNS can cause the problem and a straightforward restart of the switch can simply resolve the Error 503 Backend Fetch Failed error.

The “administration inaccessible DNS disappointment” could solve the issue with the DNS action course and further restarting and resetting it.

Method #10 Repair the Windows

This technique is the final retreat in such a case that nothing works out. Then this strategy will fix all issues with your PC. Setting the Install uses a setup move up to repair problems with the system without erasing client information on PC.

Conclusion

Error 503 Backend Fetch Failed happens mainly due to memory allocation issues or bad varnish cache configuration. In the article it mentions the main causes of Error 503 Backend Fetch Failed error and possible solutions for the same. The website passes on the message that the server of the site isn’t operating properly.

It is a normal HyperText Transfer Protocol response message popping up by the websites. Such are the codes that make it easier for a Magento improvement firm which can further investigate and point out where the problem lies when a site isn’t loading in properly.

Error 503 Backend Fetch Failed is displayed when the HTTP cache fails to fetch the requested data from the webserver.

There could be numerous reasons why it was unable to retrieve the data; the server could be down or unavailable, the connection could’ve closed before the cache server was done reading the response, the backend code or plugins could be at fault, and so on.

Regardless, we’ve listed what you can do both as a user and as the webmaster to fix Backend Fetch Failed Error 503 below.

What causes Error 503 Backend Fetch Failed?

What Can You Do as a User / Visitor?

As a user, there’s really not a lot you can do since this error occurs due to server-side issues. Nonetheless, here are some general troubleshooting steps you can take to make sure everything is good on your end:

1. Press F5 or the refresh button and refresh the page multiple times.
2. Ensure there isn’t too much packet loss with a ping test. If there is, move closer for a stronger connection or use an Ethernet cable.
   
3. Reboot your device and router.
4. If the browser has a lot of tabs open, close some of them and try loading the website now.
5. Reset your browser configurations to default. Alternatively, try using a different browser entirely.
6. Change your DNS and reset your network settings.

If you’ve taken all possible steps from your end, the only thing you can do now is wait. Since this error is often caused due to server overload, the site should work again as soon as the traffic settles down.

Generally, we’d recommend trying to visit the website outside of peak hours, but if you need to access the site urgently, you could contact the site administrator and notify them of the issue.

How to Fix Backend Fetch Failed Error 503 as a Website Owner?

If you installed any new Word Press plugins recently that you suspect may have caused this error, you should first disable/uninstall them.

Even older plugins that were working fine have malfunctioned and caused this error in the past. Fortunately, in cases like this, they get patched very quickly, so you needn’t worry about not having a certain plugin for long.

If deactivating the plugin helped, great! If not, check the solutions below.

Check Varnish Plugin

If your website uses Varnish cache, you should first determine if the issue is with Varnish or your web server. You can do this by turning off Varnish and trying to fetch without it. Here are the steps to do so:

1. Log in to your site’s cPanel.
2. Under the Web Accelerator section, select Manage Varnish > Disable Varnish.
   
3. Press Confirm Action to disable it.
4. Check if your website loads properly now.

If the site is working now, something is wrong with Varnish. You can re-enable it once to check if restarting fixes the issue. If it doesn’t, you can find out what exactly is wrong by checking the log file which you can create with the steps listed below:

To log entries where varnish response or backend response status is 503, use the following command:
$ varnishlog -q 'RespStatus == 503' -g request

To log all entries >=500, use the following command instead:
varnishlog -a -w /var/log/varnish/varnish50x.log -q "RespStatus >= 500 or BerespStatus >= 500"

Modify Cache Tag Length

The default length of cache tags in Varnish is 8192 bytes. Exceeding this can cause the HTTP 503 Backend Fetch Failed error.

You can resolve this issue by increasing the value of the http_resp_hdr_len parameter in your Varnish configuration file.

The Adobe Commerce support site has an excellent article on how to do exactly this.

Modify Varnish and NGINX Configuration Files

The steps listed are for Varnish but the same can apply for NGINX as well. Here are the steps to modify the configuration files:

1. Locate and open the file from /etc/varnish/default.vcl.
2. Find the line .url = "/pub/health_check.php"; and remove /pub as such:
                   .url = "/health_check.php";
3. Or vice versa. If there’s no /pub, try adding it.
   
4. Next, navigate to the Magento 2 root folder and open the ginx.conf.sample file.
5. Find the following line:
   location ~ (index|get|static|report|404|503).php$ {
6. Edit it by adding health_check as such:
   location ~ (index|get|static|report|404|503|health_check).php$ {
7. Save the changes and restart Varnish.

User-Reported Fixes

Note: User-Reported Fixes generally only apply to niche scenarios but they are still worth checking out.

A user on Stack Exchange reported that another website on the server was causing this issue, which affected his site as well. So if you’re currently hosted on a shared server, this might be something to consider.

One user said the issue was caused by a plugin of the hoster. Once the faulty plugin was disabled, the Backend Fetch Failed error was resolved.

Another user reported that the maintenance.flag file generated by Magento was causing the issue for them. This issue can be fixed by logging into your cPanel and renaming or deleting the maintenance.flag file from the Magento root directory.

Contact Hosting Provider for Support

If you’re still facing the Backend Fetch Failed error, we recommend contacting your hosting provider and asking for support. The error log files created using the steps above may help the support team determine the root of the issue and apply the necessary solutions swiftly.

Whether its Windows, Mac or Linux operating system, machines are too complex to be understood inside out. Machines are made up of thousands, and millions of components clubbed together in an integrated space. 

“Man makes machines to man the machines that make the machines.” Yes, it’s as complicated as that. The Human race relies on technology and machines, as they make our lives a lot simpler and allow us to accomplish our tasks with ease. 

So folks, while browsing the Internet, have you ever encountered the “Error 503 Backend Fetch Failed” issue? This error may occur, irrespective of the operating system you’re using or which device you’re browsing on, including your smartphone. 

Wondering how to fix this error? Here are a bunch of quick fixes to resolve the “Error 503 backend fetch failed” issue on your own without seeking any third-party technical assistance. 

Let’s get started, but before that here’s a detailed summary of what Error 503 is all about. 

Also Read: How to Fix Parse Error in Android

What is Error 503?

Error 503 is more like a server related issue which is often caused when too many requests pile up, leaving now adequate space in browser’s cache memory. If you need to understand this error in layman’s terminology, then we would say that this error mostly occurs when you’re requesting the content stored on the cache server. It is unable to respond or delivering too slow results. This error mainly was heard while using Magento, an open-source e-commerce platform written in PHP code. 

Here are a few common reasons why you might get stuck with the “Error 503 Backend Fetch Failed” issue.

Slow Internet Speed: One of the most common reasons why you might encounter this error while browsing is due to slow Internet speed or network connectivity issues. When you’re trying to open up a website, with slow Internet bandwidth, the site would take too much time to load, or not load at all. Resultantly, too many requests get piled up, and the website’s data gets stacked up in cache server memory, due to which this error is caused.

Site Server Under Maintenance: There are times when certain websites go under maintenance for testing and development. If you’re trying to access any website while it’s server is under maintenance, you might encounter the Error 503 on your browser. So, when a particular site’s server is temporarily under maintenance, all your requests might get queued up, leading to an internal server error. 

Blocking Suspicious Websites: To make our browsing more secure, we often block a few suspicious websites or the ones which display too many advertisements, right? So, when you’re blocking a specific site with the help of an ad-blocking tool, it prevents a lot of content to be displayed on the screen. This might also be the reason why you may encounter Error 503 while browsing when making too many requests on a website can queue up the cache server memory. 

Also Read: How To Resolve 404 Not Found Error

How to Fix Error 503 Backend Fetch Failed

You can try these below-mentioned workarounds to fix this error:

Refresh the Website

Refreshing a website might sound too simple, but it mostly helps you to overcome Error 503 while browsing. Tap the Refresh icon to reload the site and check if it resolved the issue. 

Close Other Active Tabs

As “Error 503 Backend Fetch Failed’ is mainly caused when the cache server gets temporarily overloaded, you don’t want to take any chances, right? When you encounter this error on a specific website, make sure that you close all other active tabs and services to lighten the load of cache server memory. 

Try an Alternative Web Browser

You might have no idea what’s going on in your browser’s background activities. Yes, it’s too complex to understand. So, if you’re having trouble while accessing a particular website, try re-opening it on an alternative web browser to see if you still face the Error 503 server issue. 

Reboot WiFi Router

Reboot is the magic fix to most complex technical issues. So, here’s what you need to do. Turn off your WiFi router and then restart it after 20-25 seconds, reboot your system, reload the website to check if it resolved the error. 

Also Read: Ways To Fix Error Code 0xc0000225 In Windows 10

Reset Web Browser

Reset is like the last resort to overcome this server related error. If nothing from the above-mentioned list works out well, then try resetting your web browser to start afresh. 

This wraps up our guide on how to fix the “Error 503 Backend Fetch Failed” issue that you might encounter while browsing. We hope these solutions help you in resolving the error so that you can make the most of your browsing experience without any hindrance. 

The Error 503 is one of the most common error messages on websites. The problem with this 503 error is that it gives you little information on how to fix it. In this article you can read what the HTTP 503 Service Unavailable error message is and, of course, how to solve it.

What does HTTP Error 503 mean?

The 503 error means that your website or webshop is currently unavailable due to a problem on the server, or that your website is in maintenance mode. For example, a problem on the server can be that it is too busy and your website in maintenance mode is a common action with WordPress websites.

Often the 503 error is displayed as “Service temporarily unavailable” or “Service unavailable”. This can differ, for example, between platforms such as WordPress and Magento. If you’re getting this error code on a website other than yours, all you can do is wait. Or, possibly contact the relevant website to report this. Many websites like Isitdownrightnow.com  allow you to check if the website you are trying to reach has problems. If the website is yours or under your management, you will have to take action yourself. Either you contact your web host, or you first try to see why this problem occurs and how you can solve it yourself.

503 Error variations

It is not said that you will always see the same error code. It may differ per platform, per browser and, for example, per service used. For example, sites that use Microsoft IIS provide more information than most others. The 503 error code includes these variations.

• HTTP Server Error 503
• Error 503
• HTTP Error 503
• Error 503 backend fetch failed
• Error 503 service unavailable
• 503 Service Unavailable
• 503 Service Temporarily Unavailable
• Http/1.1 Service Unavailable
• HTTP Server Error 503
• Service Unavailable – DNS Failure

Because the 503 error code provides little additional information, you have to look for a solution yourself. In nine out of ten cases, the recommendations below can help.

Let’s start with the easiest, those are the tips if you don’t own the website yourself. So what can you do to get around the error code?

1. Wait a moment and refresh the page

It can be that simple. The 503 error code is generally a temporary one. It is therefore possible that the server was too busy for a moment, or that maintenance was just being carried out on the website, so that it was not accessible. Even now, patience is a virtue. Wait 5 to 10 minutes and then just try again.

2. Restart your modem/router

This tip is especially applicable if you see the 503 error in combination with a DNS failure. In many cases there is something wrong with the DNS configuration in your router. If you restart it, there is a good chance that the error code has been resolved. Well, these were, of course, fairly simple steps.

What steps can you take if you are the owner of the website yourself?

1. Contact your web host

As mentioned, the 503 error is often shown on websites where the server is very busy at that moment. This could be due to a peak load, or perhaps even as a result of a DDoS attack. In any case, the web host can quickly see if something unusual is going on on the server. In some cases it can also be a matter of scaling resources (and therefore a higher package).

2. Disable your plugins

There is a good chance that the 503 error arises from a conflict with one or more of your plugins. Outdated plugins, or plugins that have recently been updated, can cause compatibility issues. The problem with a 503 error is that you often can’t get into the backend of your website. To disable your plugins, you can use an FTP client, such as Filezilla. In the example below, we have a WordPress installation with associated plugins installed as an example.

What you can do is either rename the parent folder ‘Plugins’, or temporarily change the name per plugin to something else, for example by adding _old. If you solved the problem with this or not, you can always rename the plugins to the official name and your plugins are activated again and all settings are remembered.

3. Temporarily disable your CDN

CDNs such as, for example, Cloudflare can also be the cause of the 503 error. Most CDN services have the option to pause them. With Cloudflare, for example, you do this on your dashboard:

If you’ve solved the problems with this, it is best to contact the relevant CDN. They may have a malfunction or can help you further. If this does not prove to be the solution, don’t forget to turn Cloudflare back on after testing.

4. Increase your server’s resources

Not always fun, but sometimes the solution to many problems. At Hypernode we always keep an eye on the resources used and give a notification if action needs to be taken. But with many webhosts you are left to your own fate. When your website has outgrown the resources, you will have to switch to packages that have more resources. Before you do this, it is always advisable to first contact the support of the web host you are using. They can quickly indicate whether switching to more resources really proves to be the solution or not. A good web host will proactively help you with this and look for a solution together with you.

5. View your error logs

Not the most fun way, but often enlightening. If there are technical problems with your site or server, this is often recorded in your error logs. The logs can often be found in the admin section of your web host or, for example, via FTP in your folders. You can also view your logs in Apache and Nginx. You can find these here:

Apache: /var/log/apache2/error.log

Nginx: /var/log/nginx/error.log

See if you spot errors and try to solve or contribute them to your hoster.

6. Check the configuration of your Firewall

We don’t see it often, but it does happen. Services that provide an automatic firewall can sometimes falsely give a false positive, treating safe and valid contents of CDNs as malicious. This causes a blockage and can sometimes lead to a 503 Service Unavailable error message.

7. For the WordPress users: turn off your theme

Besides the fact that plugins can cause a 503 error code, so can your WordPress theme. Due to compatibility issues, it sometimes happens that you run into an http error 503. To scale out your theme you need to have access to your database. This is possible, for example, with a tool such as PHPMyAdmin. You then look up the wp_options table and search for template in the row “option_name”. You should now get the name of your theme back. Then rename it to a default WordPress theme such as Twenty Twenty-One and check your website to see if the 503 error has been resolved.

Conclusion: Error 503

A 503 error code doesn’t have to be very exciting. As we described above, this is a common message that often resolves itself. In a few cases it is a persistent one and then you have to get started seriously. At Hypernode, we take a lot of work off your hands by actively monitoring this and providing you with excellent support for such 503 reports.

Solving 503 errors is for routine work. Would you like to be proactively helped in the future and benefit from hosting with the best performance in the Netherlands? Please contact us.