Nginx emerges with a 504 Gateway Time-out solution

Little scum · Posted on 2025-7-4 16:46:07

Requirements: Nginx reverse proxy to dotnet interface application, due to the special situation of one interface, the response takes about 90 seconds, and the client calls the Nginx interface will report a 504 gateway time-out error.

The process is as follows:

fastcgi_connect_timeout:fastcgi connection timeout, default 60 seconds
fastcgi_send_timeout:nginx process sends a timeout time for the request process to the fastcgi process, the default value is 60 seconds
fastcgi_read_timeout:fastcgi process sends the timeout time for the output process to the nginx process, the default value is 60 seconds

Vernacular explanation:

proxy_connect_timeout 1800s; #nginx跟后端服务器连接超时时间 (Proxy connection timeout)
proxy_send_timeout 1800s; #后端服务器数据回传时间 (proxy send timeout)
proxy_read_timeout 1800s; #连接成功后, backend server response time (proxy receiving timeout)

The solution is as follows:

Login is visible.

Configure according to your actual situation.

[Web] Nginx emerges with a 504 Gateway Time-out solution

Related Posts