Nginx Proxy-Pass Truncate Connection After 60S Even With Suggested Config Top 17 Latest Posts

When using NGINX as a proxy server, it’s important to configure the appropriate timeouts to ensure that connections are properly maintained. If you’re experiencing truncated connections after 60 seconds despite configuring the suggested settings, there could be a few different factors at play.

Firstly, make sure that you’ve configured the relevant timeout settings in NGINX. Specifically, you may want to adjust the proxy_read_timeout and proxy_send_timeout values to ensure that they’re set to a high enough value to accommodate your use case. For example, you could try setting them both to 5 minutes (300 seconds) with the following configuration:

javascript
location / {
    proxy_pass http://backend;
    proxy_read_timeout 300s;
    proxy_send_timeout 300s;
}

If you’ve already configured these settings but are still experiencing truncated connections, it’s possible that there’s a separate issue at play. For example, the backend server you’re proxying to may be terminating the connection after 60 seconds. In this case, you may need to adjust the relevant timeout settings on the backend server itself.

Another possibility is that there’s a network device or firewall between NGINX and the backend server that’s terminating the connection after 60 seconds. If this is the case, you may need to adjust the relevant timeout settings on that device as well.

Finally, it’s possible that there’s a bug or configuration issue with NGINX itself that’s causing the truncated connections. In this case, you may want to check the NGINX error logs for any relevant messages and consider upgrading to the latest version of NGINX to see if the issue has been resolved.

The default proxy pass timeout for NGINX is 60 seconds.

This means that if a response is not received from the upstream server within 60 seconds, NGINX will close the connection and return an error to the client.

However, this timeout can be changed by modifying the “proxy_connect_timeout”, “proxy_send_timeout”, and “proxy_read_timeout” directives in NGINX configuration. These directives control the timeout for establishing a connection to the upstream server, sending a request to the upstream server, and reading a response from the upstream server, respectively.

To increase the proxy read timeout in NGINX, you need to modify the proxy_read_timeout directive in the NGINX configuration file.

Here are the steps:

1. Open the NGINX configuration file using a text editor. The configuration file is usually located in /etc/nginx/nginx.conf.

2. Locate the http block in the configuration file.

3. Inside the http block, add the proxy_read_timeout directive followed by the desired value in seconds.

For example, if you want to increase the timeout to 5 minutes, you can add the following line:

http {
  ...
  proxy_read_timeout 300s;
  ...
}

1. Save the configuration file and reload NGINX to apply the changes. You can do this by running the following command:

sudo systemctl reload nginx

That’s it! NGINX will now use the new proxy read timeout value.

proxy_pass is a directive in the NGINX configuration file that is used to forward client requests to a backend server.

When a client sends a request to an NGINX server, the proxy_pass directive instructs NGINX to forward the request to a specified backend server, which is usually located on a different machine or port. This is useful when NGINX is used as a reverse proxy, load balancer or gateway for multiple backend servers.

Here is an example configuration that uses proxy_pass:

javascript
location / {
  proxy_pass http://backend-server:8080;
}

This configuration instructs NGINX to forward all requests received on the / path to the backend server running on http://backend-server:8080. The backend server will then process the request and send a response back to NGINX, which will then forward the response back to the client.

There are other directives that can be used in conjunction with proxy_pass, such as proxy_set_header to set headers for the request being forwarded, and proxy_redirect to modify the URL in the response before sending it back to the client.