Error 54113 Varnish Cache Server | How to Fix for Visitors and Administrators

Reload and wait a minute

Many 54113 errors are momentary. The backend may be restarting or briefly overloaded. Refresh once, then give it sixty seconds and try again.

Clear your browser cache and cookies

A stale cached copy or an old cookie can keep pointing you at the broken response. Clear them for that site, then reload. Testing in a private or incognito window is a fast way to check this.

Try the address with and without www

Some sites only resolve correctly behind a redirect. If the plain address fails, try the www version or the https version, since following the redirect can land you on a working node.

Flush your DNS or change DNS provider

If only you see the error, your network may be caching a stale route. Flush your DNS, or switch to a public resolver like 1.1.1.1 or 8.8.8.8, then reload.

Tell the site owner

If the error sticks across browsers and devices, the problem is on the server, not you. Let the site owner know, and include the time and the page so they can match it to their logs.

1
Confirm the backend is actually running

Before touching Varnish, make sure your origin web server is up and accepting connections. Check that Apache, NGINX or your app server is running, and confirm it answers on its own port directly. If the backend is down, Varnish has nothing to fetch, and that alone produces 54113.

2
Match the host and port in your VCL

Open your Varnish config, usually at /etc/varnish/default.vcl, and confirm the backend points at the exact address and port your web server listens on. A classic trap is Varnish trying port 8080 while the backend serves on port 80, or the other way around.

backend default {
    .host = "127.0.0.1";
    .port = "8080";
    .connect_timeout       = 5s;
    .first_byte_timeout    = 10s;
    .between_bytes_timeout  = 5s;
}

3
Loosen the backend timeouts

If the backend is healthy but slow under load, tight timeouts make Varnish give up early and throw the error. Raise the connect, first byte and between bytes timeouts to give a heavy page room to finish. Do not set them too high either, or a truly dead backend will hang requests.

4
Give Varnish more cache memory

If the error reads as a storage failure, Varnish has run out of room. Increase the storage size in the startup parameters using the -s option, and make sure the host has the physical memory to back it.

-s malloc,2G

5
Purge the cache and set a sane TTL

Corrupt or stale cached objects can keep serving a broken response. Flush the Varnish cache, then set time to live and invalidation rules so old content clears out on its own instead of piling up until storage fills.

6
Test the VCL before you deploy

A broken VCL, like a director that cannot connect or a syntax slip, is a frequent trigger. Compile and test the config before it goes live, ideally in staging. Then reload Varnish and watch the log.

varnishd -C -f /etc/varnish/default.vcl

What is error 54113 on a Varnish cache server?

It is the code Varnish shows when it cannot deliver a page. It means either Varnish could not reach the backend web server, which is a backend fetch failure, or it ran out of storage space for cached files.

I am just a visitor. How do I get past it?

Reload and wait a minute, clear your browser cache and cookies for that site, and try a private window or another browser. If only you see it, flush your DNS or switch to a public resolver. If it persists everywhere, the site owner has to fix the server.

What is the most common cause for admins?

A backend that is down or pointed at the wrong host and port. Varnish tries to fetch from the origin server, gets no usable answer, and returns 54113. Confirm the backend is up and that the VCL address matches where it actually listens.

Does error 54113 mean my server was hacked?

No. It is an operational error about caching and backend connectivity, not a security breach. It usually points to configuration, memory or a backend that stopped responding, not an intrusion.

How do I stop error 54113 coming back?

Test every VCL change in staging before deploying, monitor CPU, memory and disk so you catch pressure early, set sensible TTL and cache invalidation, and scale resources ahead of known traffic spikes.

Why does curl work but the browser shows 54113?

That usually means the site relies on a redirect that curl follows but your browser session is not handling cleanly, often tangled with cached data or DNS. Clear the site cache and cookies, try a private window, and reach the address through its correct redirect.