affine/pathfinder-containers
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

go back to defaults for some of these ridiculous timeouts
All checks were successful
build and push / build (push) Successful in 3m23s
Details

Browse source 
Signed-off-by: Ava Affine <ava@sunnypup.io>
This commit is contained in:
Ava Apples Affine 2026-02-04 10:26:30 -08:00
parent 7d7fe4ce66
commit 40478898ff
2 changed files with 10 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

16
static/nginx/nginx.conf
View file

@ -65,31 +65,31 @@ http {
# Timeouts ==================================================================================================================
# 'Body' and 'Header' max response timings. If neither a body or header is sent, the server will issue a 408 error or Request time out. (Default: 60s)
client_body_timeout 12;
client_header_timeout 12;
client_body_timeout 25;
client_header_timeout 25;
# Assigns the timeout for keep-alive connections with the client.
# Simply put, Nginx will close connections with the client after this period of time.(Default: 65)
keepalive_timeout 20s;
keepalive_timeout 40s;
# Finally, the send_timeout is established not on the entire transfer of answer, but only between two operations of reading;
# if after this time client will take nothing, then Nginx is shutting down the connection.
send_timeout 10s;
send_timeout 50s;
# Sets a timeout for name resolution. (Default: 30s)
resolver_timeout 5s;
resolver_timeout 30s;
# Timeout period for connection with FastCGI-server. It should be noted that this value can't exceed 75 seconds. (Default: 60s)
fastcgi_connect_timeout 5s;
fastcgi_connect_timeout 60s;
# Amount of time for upstream to wait for a fastcgi process to send data.
# Change this directive if you have long running fastcgi processes that do not produce output until they have finished processing.
# If you are seeing an upstream timed out error in the error log, then increase this parameter to something more appropriate. (Default: 60s)
fastcgi_read_timeout 40s;
fastcgi_read_timeout 60s;
# Request timeout to the server. The timeout is calculated between two write operations, not for the whole request.
# If no data have been written during this period then serve closes the connection. (Default: 60s)
fastcgi_send_timeout 15s;
fastcgi_send_timeout 60s;
# WebSockets ===============================================================================================================