Error guide / 504 Gateway Timeout

504 Gateway Timeout: The Server Waited Too Long

504 Gateway Timeout appears when one server waited for a response from another and did not get it in the allotted time. Unlike 502, the response is not broken, it simply arrived too late. It usually signals that something on the site is running far too slowly.

What causes it

The usual cause is a slow backend: heavy database queries, long-running scripts, an overloaded server, or an external service that answers with a delay.

How to fix it

1. Refresh after a minute; a one-off timeout can come from a temporary load spike.
2. Find the slow spots: heavy database queries, large imports, or loops in the code.
3. Disable heavy plugins one by one to see which one drags out the response.
4. Turn on caching (pages and database) to cut the load on the server.
5. Check external calls such as APIs or payment gateways; if they hang, response time grows.
6. If needed, raise max_execution_time, but fix the real cause of the slowness first.

Related errors

• 403 Forbidden 403 Forbidden: Access to This Page Is Denied
• 404 Not Found 404 Error: The Page Could Not Be Found
• 500 Internal Server Error 500 Internal Server Error: Something Broke on the Server
• 502 Bad Gateway 502 Bad Gateway: The Server Got a Bad Response