配置NGINX超时

proxy_connect_timeout设为5–10秒，确保快速失败；2. proxy_send_timeout设为10–30秒，适应慢速上传；3. proxy_read_timeout匹配应用最长响应时间，避免504错误；4. 若负载均衡，可设proxy_next_upstream_timeout限制重试时长——正确配置这些值能显着减少网关超时、提升用户体验，并需结合实际日志和监控持续调优。

When setting up Nginx as a reverse proxy (eg, for Node.js, Python apps, or upstream services), timeout configuration is critical —especially under slow network conditions, long-polling, or when your backend is temporarily unresponsive.

If timeouts aren't configured properly, users may see:

• 504 Gateway Timeout errors
• Stuck requests
• Poor user experience during high load or maintenance

Here's how to properly configure Nginx timeouts:

1. proxy_connect_timeout

How long Nginx waits to connect to the upstream server .
Default: 60s
Recommended: 5–10s for most apps

 proxy_connect_timeout 10s;

Use shorter values if your backend is on the same network—fail fast if the service is truly down.

2. proxy_send_timeout

How long Nginx waits between sending data chunks to the backend .
Default: 60s
Recommended: 10–30s

 proxy_send_timeout 30s;

This isn't total request time—it's the max time between writes. If your app sends data slowly (eg, large file uploads), increase this.

3. proxy_read_timeout

How long Nginx waits for the backend to send a response .
Default: 60s
Recommended: Match your app's longest expected response time

 proxy_read_timeout 60s;

For long-polling APIs or slow reports, set this higher (eg, 300s).
⚠️ If your app takes longer than this, Nginx will kill the connection → 504 error.

4. Optional: proxy_next_upstream_timeout (if load balancing)

Limits how long Nginx tries to find a working upstream server.

 proxy_next_upstream_timeout 5s;

Full Example (Common Setup)

 location / {
    proxy_pass http://localhost:3000;
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;

    proxy_connect_timeout 10s;
    proxy_send_timeout 30s;
    proxy_read_timeout 60s;
}

Pro Tips:

• ? Test with curl -v or browser dev tools to see if 504s happen after a fixed time (eg, 60s = likely proxy_read_timeout )
• ? If your backend restarts or deploys often, shorter timeouts (like 10s) help Nginx fail faster and retry
• ? Monitor 504 errors in Nginx logs ( /var/log/nginx/error.log ) to fine-tune

Timeouts aren't one-size-fits-all—they depend on your app behavior. Start conservative, then adjust based on real usage.

Basically, set them, test them, and don't forget them.

以上是配置NGINX超时的详细内容。更多信息请关注PHP中文网其他相关文章！