Error 503 Backend Fetch Failed: What It Means & How to Fix It

Download Article

Common solutions for the backend fetch failed error

Co-authored by Darlene Antonelli, MA Reviewed by Luigi Oppido

Last Updated: September 18, 2024 Fact Checked

Download Article

What is Error 503?

|

Fixing Error 503

Are you getting the "Error 503 backend fetch failed" message when you try to access a website? This error, also known as the "Guru Meditation" error, is caused by the Varnish cache server and indicates a problem on the website or server's end. Read on to learn the meaning of error 503 and what you can do to fix it, whether you're the website owner or just browsing the web.

Error 503 Backend Fetch Failed: Fast Facts

If you come across error 503 when viewing a website, the server is having issues and can't fetch, or load, the website for you. If you're the website's owner, the error comes from the Varnish cache server and typically indicates a configuration issue.

Section 1 of 2:

What is Error 503?

Download Article

If you're browsing the web and come across this error, something is wrong with the website you're trying to view. This doesn't mean there's a problem with your computer, phone, browser, or internet connection, but you won't be able to access the website until its owner fixes it.
2
If Error 503 occurs on your website, there's a problem with the Varnish caching server. You may see this error when installing or using a plugin or module (such as for WordPress or Drupal) on your website and are using the Varnish cache server to improve your website speed.^{[1]
X
Research source} The error means some aspect of your website is unable to retrieve needed data from another application, which can be due to:
- The server the application is trying to connect to is unavailable.^{[2]
  X
  Research source}
- The IP address, hostname, or port for the web or application server is incorrect in your Varnish configuration file.^{[3]
  X
  Research source}
- The backend server is improperly defined in the relevant VCL file.^{[4]
  X
  Research source}
- Memory issues on the server.
- Network problems between applications.

Section 2 of 2:

How to Fix 503 Backend Fetch Failed

Download Article

1
As a user: If you can't load a website because of error 503, the error is not on your end. To be extra sure, try going to a different website, such as wikihow.com or Google.com, and make sure you're not getting an error there. You can also try clearing your cache and cookies, though this will not usually fix error 503 backend fetch errors.
- If you're supposed to be able to access the site, contact the admin to inform them of the error.
2
As a server owner: The fix for error 503 depends on the cause, so you'll need to dig around in the logs to determine what prompted the error. Check your Varnish logs to assess the health of the backend server using the command sudo varnishlog -g raw -i backend_health.
- If you cannot determine the cause of the error, run the command sudo varnishlog -g request -q "RespStatus == 503" to see which transactions resulted in the 503 backend fetch failed error.^{[5]
  X
  Research source}
- Depending on the application, plugin, or module you're using, you may need to make changes to the Varnish configuration file.