From 5eaebdc12425d0f7447e9729b059c1fef96c2bf5 Mon Sep 17 00:00:00 2001 From: jameskimmel <17176225+jameskimmel@users.noreply.github.com> Date: Mon, 6 Oct 2025 13:27:07 +0200 Subject: [PATCH] timeout NGINX Signed-off-by: jameskimmel <17176225+jameskimmel@users.noreply.github.com> Update comments on timeout settings for clarity Signed-off-by: jameskimmel <17176225+jameskimmel@users.noreply.github.com> Adjust proxy timeouts Signed-off-by: jameskimmel <17176225+jameskimmel@users.noreply.github.com> NGINX proxy timeouts Signed-off-by: jameskimmel <17176225+jameskimmel@users.noreply.github.com> --- reverse-proxy.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/reverse-proxy.md b/reverse-proxy.md index 56e42fe3..f9bf7e82 100644 --- a/reverse-proxy.md +++ b/reverse-proxy.md @@ -427,7 +427,10 @@ server { client_max_body_size 0; client_body_buffer_size 512k; # http3_stream_buffer_size 512k; # uncomment to enable HTTP/3 / QUIC - supported on nginx v1.25.0+ - proxy_read_timeout 86400s; + + proxy_read_timeout 3610s; + # The default NEXTCLOUD_MAX_TIME value is 3600 seconds. By setting it 10 seconds higher than that, we make sure that always Nextcloud times out and not NGINX. + # If you increased NEXTCLOUD_MAX_TIME, increase this timeout accordingly. server_name ;