What does 504 Gateway Timeout mean?

It means a gateway or proxy, such as nginx, a load balancer or Cloudflare, waited for the server behind it and did not get a response within its time limit. The request may still be running, but the gateway has already given up and shows the error.

What is the difference between a 502 and a 504 error?

A 502 means the upstream server sent an invalid response or none at all, often because it crashed. A 504 means it was still working but did not answer in time. Crashed or refused is a 502, too slow is a 504.

What is the difference between a 504 and a Cloudflare 524 error?

Both are timeouts. A 524 is Cloudflare’s own code for a connection that was made, but where your server did not answer within about 100 seconds. A 504 is the standard code for any gateway that timed out waiting for its upstream.

Why do I get a 504 only on some pages or in the admin area?

Because those pages do the most work: big reports, searches, imports or bulk edits. They run longer than the gateway’s timeout, while light pages answer well within it. The slow query or script behind that page is what needs fixing.

Can raising max_execution_time fix a 504?

Sometimes as a stop-gap, but it rarely solves the real problem. The gateway has its own timeout, so you may need to raise that too, and a request that takes 90 seconds is still a bad experience. Finding and speeding up the slow part is the lasting fix.

Can a slow database cause a 504 Gateway Timeout?

Yes, it is one of the most common causes. Missing indexes, bloated tables and heavy queries make PHP wait for the database, and the gateway gives up first. The MySQL slow query log shows which queries are responsible.

How much does it cost to fix a 504 Gateway Timeout?

A clearly defined 504 problem starts at €295 excl. VAT, with a fixed price agreed after the free diagnosis and before any work begins. If the slow part is outside our reach, such as a third-party API, we tell you and you pay nothing for that.

HTTP error 504

504 Gateway Timeout: what it means and how to fix it

The short answer

Nothing has necessarily crashed. Something is just too slow, and the server in front stopped waiting before your site could answer.

Get it fixed

Backup before every change
Fixed price before we start
Remote, anywhere in the world
Free diagnosis

A 504 is a timing problem, and every layer has its own stopwatch. By default nginx waits 60 seconds for PHP, PHP stops a script after 30 seconds (max_execution_time), and Cloudflare reports its own 524 when your server takes longer than 100 seconds. Whichever stopwatch runs out first decides which error you see.

Sound familiar?

What a 504 Gateway Timeout looks like

A page that says “504 Gateway Timeout” or, on nginx, “Gateway Time-out”
A Cloudflare page with “Error 524: A timeout occurred”
Only certain pages fail: search, reports, checkout, an import or the admin area
A page spins for 30 to 60 seconds and then fails
It got worse as your database or traffic grew, or after a new plugin or import

Causes

Common reasons for a 504 Gateway Timeout

Slow database queries

A query that scans a large table without an index can take many seconds. As your data grows, a page that used to load quickly slides over the timeout.

Slow scripts or heavy pages

Page builders, big product listings, image processing or reports that do too much work in a single request.

External API calls that hang

If your site waits for a payment provider, shipping service or another API that does not answer, the page waits too, until the gateway gives up.

Heavy imports, backups or cron jobs

A job that runs during business hours takes workers and database capacity away from visitors.

Timeout limits that do not match

If the gateway’s timeout is shorter than the time PHP is allowed to run, the gateway always loses. The limits must fit the work a page really does.

The upstream server is overloaded

When PHP workers or the database are busy with other requests, new ones wait in line until the timeout hits.

Try it yourself

Quick checks for a 504 Gateway Timeout

Safe things to check first. Raising limits is the last step, not the first.

1 Note which URLs fail. If only a few do (search, checkout, one admin page), the cause is a heavy page and not the whole server.
2 Check what runs at the same time: a backup, an import, a search re-index or a cron job. Pause it and retry.
3 Look at the logs. In nginx, “upstream timed out (110: Connection timed out) while reading response header from upstream” confirms the wait; PHP’s slow log shows which script was running.
4 On WordPress, rename wp-content/plugins to plugins-off for a moment. Backup, security-scan, related-posts and page-builder plugins are common culprits.
5 Ask your host whether the MySQL slow query log can be enabled. It lists exactly which queries take seconds. Make a backup before cleaning or optimising any tables.
6 Only then raise the timeout, for example max_execution_time or fastcgi_read_timeout, as a temporary measure. A page that needs 90 seconds still frustrates visitors.

Our approach

How we resolve a 504 Gateway Timeout

1

We find the slow request

We trace which page, query or call takes the time, using the web server, PHP and database logs, so we fix the slow part rather than the symptom.
2

Backup before any change

A full copy of files and database comes first, so every change can be undone.
3

Cause, fixed price, your OK

The diagnosis is free. You get the cause in plain language, a fixed price and a time estimate. Nothing starts without your yes.
4

Speed up, test and report

We make the slow part faster, set timeouts that fit the work, check the pages that failed and send a short report.

What we need

What we need from you

Access to your hosting panel or SSH, including the web server and PHP logs
Database access, or the ability to enable the slow query log
An admin login for your CMS or application, if there is one
Which pages or actions fail, when it began and what changed before

We ask for the least access that does the job, use a separate key per client, and you can revoke it the moment we are done.

What we cannot fix

We cannot fix a 504 caused by a slow third-party service that we do not control, or by a hosting plan that is simply too small for the work. In those cases we tell you after the free diagnosis, show you where the time goes, and advise on the realistic options.

Price

Price and what happens next

1

Free diagnosis

We find the cause and tell you what is wrong.
2

Fixed price

You get a price and a time estimate. Nothing starts without your yes.
3

Fixed and reported

We repair it, test it and send a short report.

From €295 excl. VAT

Fixed price, agreed before we start

Is it urgent? Say so in the form or in the chat. We start as soon as we can and give you a realistic time estimate with the quote. If priority work costs extra, you see that in the quote before you agree.

Get it fixed

Questions?

FAQ about the 504 Gateway Timeout

Also see

Tell us what is wrong

Answer a few short questions. You get a fixed price before we do anything.

Step 1 of 5

On which platform are you experiencing the problem?

Website App Software

504 Gateway Timeout: what it means and how to fix it

What a 504 Gateway Timeout looks like

Common reasons for a 504 Gateway Timeout

Slow database queries

Slow scripts or heavy pages

External API calls that hang

Heavy imports, backups or cron jobs

Timeout limits that do not match

The upstream server is overloaded

Quick checks for a 504 Gateway Timeout

How we resolve a 504 Gateway Timeout

We find the slow request

Backup before any change

Cause, fixed price, your OK

Speed up, test and report

What we need from you

What we cannot fix

Price and what happens next

Free diagnosis

Fixed price

Fixed and reported

FAQ about the 504 Gateway Timeout

Related problems

HTTP error 502

HTTP error 503

Database connection error

Tell us what is wrong