Reverse proxy WebSocket dropouts and 502 errors on long-lived connections - Help - Caddy Community = 40rem)" rel="stylesheet" data-target="chat_desktop" /> = 40rem)" rel="stylesheet" data-target="discourse-reactions_desktop" /> = 40rem)" rel="stylesheet" data-target="poll_desktop" /> = 40rem)" rel="stylesheet" data-target="desktop_theme" data-theme-id="1" data-theme-name="caddy custom"/> Reverse proxy WebSocket dropouts and 502 errors on long-lived connections Help brian9 (Brian) July 31, 2026, 7:11pm 1 Hi, I am configuring Caddy as a reverse proxy in front of an external node application that handles real-time WebSocket traffic. While testing persistent connections across background endpoints, such as a free script testing tool, Caddy closes idle HTTP/2 streams after roughly 60 seconds and returns a 502 Bad Gateway response to the client. Has anyone configured custom transport timeouts inside the reverse_proxy directive to keep long-polling WebSocket sessions alive, and is there a recommended flush_interval setting in Caddyfile to prevent upstream disconnects without causing high CPU usage?