Need help?

Our experts have had an average response time of 13.14 minutes in February 2024 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

CentOS Web Panel error “503 backend fetch failed” – Here’s how to fix it

by | Nov 29, 2018

CentOS Web Panel is a free control panel that allows quick and easy management of servers.

It allows to improve server performance and website speed with web applications like Varnish Cache.

But, enabling Varnish Cache often creates the error “503 backend fetch failed” due to configuration problems.

At Bobcares, we help server owners to find the real reason for such errors as part of our Support Services for Web Hosts.

Today, let’s see what causes the CentOS Web Panel error “503 backend fetch failed” and how we fix it.

 

What causes the error “503 backend fetch failed” ?

Before diving into the details of the error, we need to know the purpose of Varnish Cache in the web server configuration.

Varnish cache is a reverse proxy that is put in front of the web server. The helps to reduce the loading times of websites. The web page requests first reach the Varnish cache that listens on port 80.

Varnish visits the back-end server once to cache and store the pages. Then all future requests for the same page will be served by Varnish. This ensures faster loading of pages.

At times, when server do not having adequate memory or if there are too many requests queuing up, backend connection to server fails. Then website shows the error;

Error 503 Backend fetch failed
Backend fetch failed
Guru Meditation:
XID: 1639327
Varnish cache server

The typical reasons for the errors are :

 

1. Memory issues

For servers where there are too many requests queuing up, adequate amount of memory is needed to serve the requests. When there is limit for the memory use, it results in connection failure with back-end web server.

 

2. Wrong Varnish cache configuration

Similarly, from our expertise in managing servers, wrong Varnish Cache configuration also can cause the error.

The major configuration errors are :

  1. Varnish and Apache using same port 80.
  2. The IP used in Varnish configuration not listening properly.

 

How to fix “503 backend fetch failed” in CentOS Web Panel?

Now that we know the major failure points, let’s see how we can fix the error.

 

1. Allocate more Memory

The amount of memory that Varnish will use depends on the number of requests it receive. Higher the number of requests, higher the memory consumption.

Hence, firstly our Support Engineers do a proactive analysis of number of website visitors on the server. Then, we estimate the total memory usage. And, we add additional memory for varnish cache to avoid further problems.

 

2. Correct Varnish Configuration

Similarly, our Support Engineers adjust the varnish port, IP address and other parameters from the CentOS Web Panel. The interface looks as shown in the picture.

 

web_panel_503

 

And, when there is high load in the server even after re-configuring Varnish cache, we can disable the Varnish cache from the CentOS web panel (CWP). To do this,

  1. Login to CWP
  2. Click on Apache Settings drop down
  3. Change Webservers

Our Support Engineers re-enable the varnish cache only after ensuring proper memory allocation on the server.

 

Conclusion

CentOS Web Panel error “503 backend fetch failed” happens mainly due to memory allocation issues or bad varnish cache configuration. Today, we’ve seen the top causes for the error and how our Support Engineers fix them.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

SEE SERVER ADMIN PLANS

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Categories

Tags

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF