This can happen in either of the following two scenarios.
1. nginx proxy
The proxy_read_timeout value needs to be adjusted appropriately.
location/{
…
proxy_read_timeout 300;
…
location/{ …}
2. nginx as other upstream services such as php-fpm
In this case, adjust the fastcgi_read_timeout option value appropriately.
location ~ .+\.php($|/) {
…
fastcgi_pass unix:/var/run/php5-fpm.sock;
fastcgi_read_timeout 300;
…
}
The relevant configurations for the server section are.
large_client_header_buffers 4 16k;
client_max_body_size 30m;
client_body_buffer_size 128k;
#proxy_connect_timeout 300;
#proxy_read_timeout 300;
#proxy_send_timeout 300;
#proxy_buffer_size 64k;
#proxy_buffers 4 32k;
#proxy_busy_buffers_size 64k;
#proxy_temp_file_write_size 64k;
fastcgi_connect_timeout 75;
fastcgi_read_timeout 300;
fastcgi_send_timeout 300;
fastcgi_buffer_size 64k;
fastcgi_buffers 4 32k;
fastcgi_busy_buffers_size 64k;
fastcgi_temp_file_write_size 64k;
Choose the above configuration depending on the proxy or fastcgi used by your server.
Similar Posts:
- Nginx an upstream response is buffered to a temporary file,nginx502 Error
- Fix Nginx 502 Error:upstream sent too big header while reading response header from upstream
- [Solved] Nginx proxy Timeout: upstream timed out (110: Connection timed out)
- nginx: client intended to send too large body
- [Solved] When PostgreSQL writes data to Excel, there is a failure your, nginx error handling
- Nginx Timeout Error: upstream timed out (110: Connection timed out) while reading response header from ups…
- How to Solve Chrome Error: “net::ERR_INCOMPLETE_CHUNKED_ENCODING”
- [Solved] nginx upstream timed out (110 connection timed out)
- 413 errors are reported in the service exposed by ingress