From 4fbaac9b4d71fc5bed3e241a53a563e2d4eec88d Mon Sep 17 00:00:00 2001 From: David Montero Date: Mon, 4 May 2026 15:15:11 +0200 Subject: [PATCH] =?UTF-8?q?fix(nginx):=20bump=20/api/=20proxy=5Fread=5Ftim?= =?UTF-8?q?eout=20300s=20=E2=86=92=20600s=20for=20ESP-IDF=20builds?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cold ESP-IDF compiles (esp32, esp32-cam, etc.) can legitimately take 5–10 minutes — first time the project is built, ninja has to compile the entire IDF + Arduino-ESP32 component graph from scratch. Nginx was cutting the connection at 5 min, which surfaced as 'No response from server' in the frontend even though the build was still progressing. Worse, since the backend doesn't cancel the compile on client disconnect, repeated user clicks pile up parallel ninja jobs that saturate CPU and slow every concurrent build further. 10 min covers cold builds with comfortable margin. Long-term we should make compile a job (POST → job_id, GET status) and cancel duplicates server-side, but the timeout bump unblocks users today. Co-Authored-By: Claude Opus 4.7 (1M context) --- docker/nginx.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker/nginx.conf b/docker/nginx.conf index 6f560421..33ca0d00 100644 --- a/docker/nginx.conf +++ b/docker/nginx.conf @@ -53,7 +53,7 @@ server { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; - proxy_read_timeout 300s; + proxy_read_timeout 600s; proxy_connect_timeout 75s; }