504 api network_error ai_generated partial

504 网关超时：上游响应超时

504 Gateway Timeout: upstream response timeout

ID: api/http-504-gateway-timeout-upstream

其他格式: JSON · Markdown 中文 · English
80%修复率
89%置信度
1证据数
2023-08-15首次发现

版本兼容性

版本状态引入弃用备注
Nginx 1.25.0 active — — —
AWS API Gateway (2024) active — — —
Kong 3.6.0 active — — —
HAProxy 2.9.0 active — — —

根因分析

API 网关或反向代理（如 Nginx、AWS API Gateway）在等待上游服务响应时超时，通常由于处理缓慢或网络问题。

English

An API gateway or reverse proxy (e.g., Nginx, AWS API Gateway) timed out while waiting for the upstream service to respond, typically due to slow processing or network issues.

generic

官方文档

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/504

解决方案

  1. Increase the upstream timeout in the gateway configuration. For Nginx, add to the location block: `proxy_read_timeout 60s; proxy_connect_timeout 30s;`. Then reload: `nginx -s reload`.
  2. Optimize the upstream service's response time by adding caching, database query optimization, or asynchronous processing. For example, use Redis caching for frequent queries.
  3. Implement a retry mechanism with exponential backoff in the client, but ensure idempotency. Example in Python: `requests.get(url, timeout=10); time.sleep(2**attempt)`.

无效尝试

常见但无效的做法:

  1. 90% 失败

    The timeout occurs at the gateway, not the client; client-side changes are irrelevant.

  2. 70% 失败

    Restarting resets the service but does not address underlying performance bottlenecks like slow queries or resource leaks.

  3. 80% 失败

    Removing timeouts allows slow requests to accumulate, potentially crashing the service.