Skip to content

fix(server): idle /ws connections behind a reverse proxy no longer drop every 60s - #40932

Merged
juliusmarminge merged 1 commit into
mainfrom
factory/issue-40927
Nov 22, 2026
Merged

juliusmarminge merged 1 commit into
mainfrom
factory/issue-40927

Conversation

@juliusmarminge

@juliusmarminge juliusmarminge commented Nov 22, 2026 •

Copy link
Copy Markdown
Member

An idle connection to a T3 Code server behind a reverse proxy (nginx's default 60s proxy_read_timeout, AWS ALB) was closed every 60 seconds whenever the app was backgrounded or the machine slept, because the server's /ws socket only answered client messages and never sent anything on its own. The server now sends a small heartbeat frame on every /ws connection every 20 seconds, as its server-sent event streams already do.

  • withSocketHeartbeat (new, apps/server/src/socketHeartbeat.ts) writes {"_tag":"Pong"} on an interval for as long as the connection's writer is open.
  • /ws in ws.ts wraps every upgraded socket with it, alongside the existing large-frame splitting.
  • Clients already treat any frame as proof the server is alive and ignore unsolicited pongs, so no client change is needed and older clients keep working.

Fixes #40927

Reproduction on main

Commit 2c4310e (origin/main). Ran node apps/server/src/bin.ts serve --mode web --host 127.0.0.1 --port 47927 --base-dir <fresh scratch dir> --no-browser with T3CODE_DEV_SEED=0. In front of it ran a Node TCP proxy on :47928 that, like nginx proxy_read_timeout 60s, closes a connection after 60s with no bytes from upstream (https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/6e599f9d3e987467/idleproxy.mjs). A Node client (https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/6e76642ceabceda1/silentclient.mjs) paired with the startup token via POST /api/auth/browser-session, took a ticket from POST /api/auth/websocket-ticket/rpc, opened /ws?wsTicket=…&orchestrationProtocol=2 through the proxy, then sent nothing, modelling a suspended app or a sleeping Mac. Observed: open at +0.1s, zero server frames, closed with code 1006 at +60.1s; the proxy logged 'upstream silent 60000ms, closing (lived 60.0s)' (log: https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e0fd2751e5b59e04/silent-run.log). The multi-minute reconnect was not reproduced: on main, a session that lasted at least BACKOFF_RESET_AFTER_MS (30s) resets the retry ladder, and the first loss of a live session retries after about 250ms (SESSION_LOSS_RETRY_DELAY_MS). The reported delays are likely the client being suspended by the OS, which needs a real macOS and iOS device to observe.

Evidence

Started each real server with fresh data, paired a silent Node WebSocket client through a TCP proxy enforcing a 60s upstream idle timeout, and observed it for up to 150s. The client sent no WebSocket frames. Images and videos below are labeled transcript replays of the actual runtime logs, not app screenshots.

Before After
2c4310eb06 7aa8b51e95
Before: socket closes at 60.1s with zero server frames After: seven heartbeats and socket still open at 150s
Timed transcript replay · Raw log Timed transcript replay · Raw log

Drivers: TCP proxy, silent client, comparison runner, transcript renderer.

The head log also shows an unused HTTP keepalive connection timing out; the WebSocket continues receiving heartbeats and remains open.

Not shown:

  • Permanent blocker: real macOS sleep/wake behavior requires a macOS machine outside the device pool, unavailable to this worker.
  • iOS background suspension and the reported multi-minute reconnect delay were not exercised; this comparison proves the server-side idle-heartbeat behavior using the supplied silent-client reproduction.
  • Actual nginx and AWS ALB deployments were not exercised; the supplied TCP proxy enforced their cited 60-second upstream idle timeout.

Tests

  • vp test run src/socketHeartbeat.test.ts (apps/server): 1 passed
  • vp run check:changed: lint, knip, graphql, typecheck (3 packages) and tests (3 files, 37 tests) passed. Format failed on the new file; fixed with vp fmt, and the pre-commit vp fmt, lint and knip then passed
  • Runtime: the reporter's silent client against node apps/server/src/bin.ts serve --mode web on a fresh base dir, connecting directly with no proxy, 45s per side: base had 0 server frames; the fix had a heartbeat at +20.1s and +40.1s
  • CI on 7aa8b51: all 38 checks passed

Not in this change

  • The multi-minute reconnect delays in the report were not reproduced. They likely come from the OS suspending the client, which needs a real macOS or iOS device to observe.
  • The 20s interval is defined separately from the SSE HEARTBEAT_INTERVAL in eventStreamResponse.ts rather than shared, because the two have different stated reasons.

Who did the work

  • Written by Claude Opus 5.5, in Claude Code
  • Reviewed by GPT-6.1 Sol, in Codex, and by Claude Opus 5.5, each on its own
  • Proof captured by GPT-6.1 Sol and checked by Claude Opus 5.5

Run by the t3code factory in T3 Code.

…op every 60s

The /ws RPC socket only answered client frames, so a suspended client that
stopped pinging lost its socket to any proxy with a 60s idle timeout. The
server now writes a heartbeat frame every 20 seconds on each /ws socket.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added vouch:trusted Author is trusted by repo permissions or the VOUCHED list. size:M 30-99 changed lines (additions + deletions). labels Nov 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider Metric Main baseline This PR Impact PR ceiling
Codex Total thread wire 5.0 KiB 5.0 KiB 0 B (0.0%) 6.8 KiB ✅
Codex Thread snapshot wire 3.8 KiB 3.8 KiB 0 B (0.0%) 4.9 KiB ✅
Codex Live turn WebSocket wire 1.2 KiB 1.2 KiB 0 B (0.0%) 2.0 KiB ✅
Codex Live turn WebSocket decoded 21.5 KiB 21.5 KiB 0 B (0.0%) 24.4 KiB ✅
Codex Live turn messages 1 1 0 (0.0%) 8 ✅
Claude Total thread wire 5.0 KiB 5.0 KiB 0 B (0.0%) 6.8 KiB ✅
Claude Thread snapshot wire 3.8 KiB 3.8 KiB 0 B (0.0%) 4.9 KiB ✅
Claude Live turn WebSocket wire 1.2 KiB 1.2 KiB 0 B (0.0%) 2.0 KiB ✅
Claude Live turn WebSocket decoded 21.9 KiB 21.9 KiB 0 B (0.0%) 24.4 KiB ✅
Claude Live turn messages 1 1 0 (0.0%) 8 ✅

Other scenarios

All 64 scenario measurements match main.

All 64 scenario measurements
Provider Scenario Metric Main baseline This PR Impact PR ceiling
Codex short turn resume WebSocket decoded 10.5 KiB 10.5 KiB 0 B (0.0%) 12.7 KiB ✅
Codex short turn resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Codex long turn running, cold open HTTP decoded 281.7 KiB 281.7 KiB 0 B (0.0%) 302.7 KiB ✅
Codex long turn running, cold open rows 75 75 0 (0.0%) 75 ✅
Codex long turn running, history page HTTP decoded 92.4 KiB 92.4 KiB 0 B (0.0%) 107.4 KiB ✅
Codex long turn running, history page rows 75 75 0 (0.0%) 75 ✅
Codex long turn finished, cold open HTTP decoded 381.5 KiB 381.5 KiB 0 B (0.0%) 410.2 KiB ✅
Codex long turn finished, cold open rows 151 151 0 (0.0%) 151 ✅
Codex long turn finished, socket cold open WebSocket decoded 381.6 KiB 381.6 KiB 0 B (0.0%) 410.2 KiB ✅
Codex long turn finished, socket cold open WebSocket messages 2 2 0 (0.0%) 2 ✅
Codex long turn finished, socket cold open rows 151 151 0 (0.0%) 151 ✅
Codex long turn finished, work page HTTP decoded 186.2 KiB 186.2 KiB 0 B (0.0%) 200.2 KiB ✅
Codex long turn finished, work page rows 150 150 0 (0.0%) 150 ✅
Codex idle thread resume WebSocket decoded 65 B 65 B 0 B (0.0%) 200 B ✅
Codex idle thread resume WebSocket messages 1 1 0 (0.0%) 1 ✅
Codex fleet shell snapshot HTTP decoded 42.4 KiB 42.4 KiB 0 B (0.0%) 53.7 KiB ✅
Codex fleet shell snapshot rows 27 27 0 (0.0%) 27 ✅
Codex fleet shell subscribe WebSocket decoded 65 B 65 B 0 B (0.0%) 200 B ✅
Codex fleet shell subscribe WebSocket messages 1 1 0 (0.0%) 1 ✅
Codex fleet shell resume check HTTP decoded 18 B 18 B 0 B (0.0%) 100 B ✅
Codex fleet shell resume check rows 0 0 0 0 ✅
Codex stale shell reload HTTP decoded 42.4 KiB 42.4 KiB 0 B (0.0%) 53.7 KiB ✅
Codex stale shell reload rows 27 27 0 (0.0%) 27 ✅
Codex stale shell resume WebSocket decoded 140 B 140 B 0 B (0.0%) 400 B ✅
Codex stale shell resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Codex stale todo list cold open HTTP decoded 72.4 KiB 72.4 KiB 0 B (0.0%) 83.0 KiB ✅
Codex stale todo list cold open rows 75 75 0 (0.0%) 75 ✅
Codex stale todo list cold open nodes 2 2 0 (0.0%) 4 ✅
Codex stale todo list cold open subagents 2 2 0 (0.0%) 4 ✅
Codex stale todo list cold open plans 1 1 0 (0.0%) 2 ✅
Codex stale todo list cold open providerTurns 1 1 0 (0.0%) 2 ✅
Codex stale todo list cold open checkpoints 1 1 0 (0.0%) 2 ✅
Claude short turn resume WebSocket decoded 10.6 KiB 10.6 KiB 0 B (0.0%) 12.7 KiB ✅
Claude short turn resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Claude long turn running, cold open HTTP decoded 283.3 KiB 283.3 KiB 0 B (0.0%) 302.7 KiB ✅
Claude long turn running, cold open rows 75 75 0 (0.0%) 75 ✅
Claude long turn running, history page HTTP decoded 93.4 KiB 93.4 KiB 0 B (0.0%) 107.4 KiB ✅
Claude long turn running, history page rows 75 75 0 (0.0%) 75 ✅
Claude long turn finished, cold open HTTP decoded 384.2 KiB 384.2 KiB 0 B (0.0%) 410.2 KiB ✅
Claude long turn finished, cold open rows 151 151 0 (0.0%) 151 ✅
Claude long turn finished, socket cold open WebSocket decoded 384.3 KiB 384.3 KiB 0 B (0.0%) 410.2 KiB ✅
Claude long turn finished, socket cold open WebSocket messages 2 2 0 (0.0%) 2 ✅
Claude long turn finished, socket cold open rows 151 151 0 (0.0%) 151 ✅
Claude long turn finished, work page HTTP decoded 188.1 KiB 188.1 KiB 0 B (0.0%) 200.2 KiB ✅
Claude long turn finished, work page rows 150 150 0 (0.0%) 150 ✅
Claude idle thread resume WebSocket decoded 66 B 66 B 0 B (0.0%) 200 B ✅
Claude idle thread resume WebSocket messages 1 1 0 (0.0%) 1 ✅
Claude fleet shell snapshot HTTP decoded 43.0 KiB 43.0 KiB 0 B (0.0%) 53.7 KiB ✅
Claude fleet shell snapshot rows 27 27 0 (0.0%) 27 ✅
Claude fleet shell subscribe WebSocket decoded 66 B 66 B 0 B (0.0%) 200 B ✅
Claude fleet shell subscribe WebSocket messages 1 1 0 (0.0%) 1 ✅
Claude fleet shell resume check HTTP decoded 18 B 18 B 0 B (0.0%) 100 B ✅
Claude fleet shell resume check rows 0 0 0 0 ✅
Claude stale shell reload HTTP decoded 43.0 KiB 43.0 KiB 0 B (0.0%) 53.7 KiB ✅
Claude stale shell reload rows 27 27 0 (0.0%) 27 ✅
Claude stale shell resume WebSocket decoded 140 B 140 B 0 B (0.0%) 400 B ✅
Claude stale shell resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Claude stale todo list cold open HTTP decoded 73.4 KiB 73.4 KiB 0 B (0.0%) 83.0 KiB ✅
Claude stale todo list cold open rows 75 75 0 (0.0%) 75 ✅
Claude stale todo list cold open nodes 2 2 0 (0.0%) 4 ✅
Claude stale todo list cold open subagents 2 2 0 (0.0%) 4 ✅
Claude stale todo list cold open plans 1 1 0 (0.0%) 2 ✅
Claude stale todo list cold open providerTurns 1 1 0 (0.0%) 2 ✅
Claude stale todo list cold open checkpoints 1 1 0 (0.0%) 2 ✅

Baseline: 2c4310e · PR result: 7aa8b51 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

  • Codex decoded thread snapshot: 108.5 KiB
  • Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

@coderabbitai

coderabbitai Bot commented Nov 22, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The server now writes a heartbeat frame every 20 seconds on upgraded WebSocket connections. The heartbeat runs in the writer’s scope and is applied whether or not large-frame splitting is enabled.

Changes: WebSocket heartbeat

Layer / File(s) Summary
Heartbeat writer and test
apps/server/src/socketHeartbeat.ts, apps/server/src/socketHeartbeat.test.ts
Adds a 20-second heartbeat frame writer that runs in a scoped effect and ignores heartbeat errors. The test checks two writes across two intervals and confirms that writes stop after the scope closes.
WebSocket upgrade integration
apps/server/src/ws.ts
Applies the heartbeat wrapper to upgraded sockets. The splitFrames parameter continues to control large-frame splitting.

Estimated code review effort: 2 (Simple) | ~12 minutes

Change: Bug fix · Severity of issue fixed: High

Sequence Diagram(s)

sequenceDiagram
  participant WebSocketUpgrade
  participant splitLargeSocketFrames
  participant withSocketHeartbeat
  participant SocketWriter
  participant HeartbeatEffect
  WebSocketUpgrade->>splitLargeSocketFrames: wrap socket when splitFrames is enabled
  WebSocketUpgrade->>withSocketHeartbeat: wrap resulting socket
  withSocketHeartbeat->>SocketWriter: forward original write
  SocketWriter-->>withSocketHeartbeat: report successful write
  withSocketHeartbeat->>HeartbeatEffect: start scoped repeating effect
  loop every 20 seconds
    HeartbeatEffect->>SocketWriter: write Pong frame
  end
Loading

Possibly related PRs

  • pingdotgg/t3code#23758: Changes the client-side socket activity contract for split large frames, which is also relevant to WebSocket frame handling in ws.ts.

Suggested labels: bugfix

Suggested reviewers: macroscopeapp

Merge Risk: Minimal · up to 7aa8b

This adds a 20-second server heartbeat on WebSocket connections so idle sessions survive proxies with 60-second timeouts. It is additive, and older clients are reported to ignore the extra frames. No merge-blocking risk was identified.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the main change: a server-side fix so idle /ws connections behind a reverse proxy no longer drop every 60 seconds. It follows the conventional commit form and matches the heartbeat add…
Linked Issues check Passed Issue #40927 asks that idle direct /ws connections survive reverse-proxy idle timeouts, or that clients reconnect promptly. Its suggested fix 1 is a server-side WebSocket heartbeat every 20-30s on /ws…
Out of Scope Changes check Passed The changes are the new socketHeartbeat.ts module, its unit test socketHeartbeat.test.ts, and the ws.ts change that wraps /ws sockets with withSocketHeartbeat. Each change serves the heartbeat objecti…
Description check Passed The description is thorough and follows the template. It has a clear problem statement with reproduction details, a change section that explains the server-side heartbeat and why no client change is n…
Full details: Title check

Explanation

The title names the main change: a server-side fix so idle /ws connections behind a reverse proxy no longer drop every 60 seconds. It follows the conventional commit form and matches the heartbeat added in socketHeartbeat.ts and ws.ts. It is specific and clear.

Full details: Linked Issues check

Explanation

Issue #40927 asks that idle direct /ws connections survive reverse-proxy idle timeouts, or that clients reconnect promptly. Its suggested fix 1 is a server-side WebSocket heartbeat every 20-30s on /ws. The PR implements that option. socketHeartbeat.ts (head) defines SOCKET_HEARTBEAT_INTERVAL = 20s and withSocketHeartbeat, which writes '{"_tag":"Pong"}' on a forked, scoped loop while the writer is open. The PR summary states ws.ts applies this wrapper to every upgraded /ws socket. The import of withSocketHeartbeat is present at head. The runtime comparison in the PR reports no server frames on base and heartbeats at +20.1s and +40.1s on the fix, which is consistent with this code. Not addressed: the multi-minute client reconnect delays (fix 2). The issue lists either fix as sufficient, and the PR author states those delays were not reproduced. Limits of this assessment: the ws.ts diff could not be read (changed blobs unavailable in the checkout), so the wiring was verified from the import and the PR summary only. The claim that existing clients ignore the unsolicited Pong frame was not verified against client code. The before/after evidence section is still pending, but it is not a coding requirement.

Full details: Out of Scope Changes check

Explanation

The changes are the new socketHeartbeat.ts module, its unit test socketHeartbeat.test.ts, and the ws.ts change that wraps /ws sockets with withSocketHeartbeat. Each change serves the heartbeat objective of #40927. The summary says ws.ts now applies the heartbeat to all upgraded sockets, including those without the splitFrames parameter. This is required for every /ws connection to receive heartbeats, so it is in scope. The separate 20s constant (not shared with SSE HEARTBEAT_INTERVAL) is explained in the PR. No unrelated changes were identified in the available evidence. The ws.ts diff could not be read directly, so this verdict relies on the PR summary for that file.

Full details: Description check

Explanation

The description is thorough and follows the template. It has a clear problem statement with reproduction details, a change section that explains the server-side heartbeat and why no client change is needed, a scope statement that links issue #40927 as the bug report, a verification section with focused tests, runtime comparison and clear notes on what was not checked, and a section naming the model and harness that did the work. The Scope section is written as a bug report link, which fits the template's requirement to link the issue showing the bug. The PR is a fix, not a feature. Remaining gaps are minor: the template's title guidance is not checked here, and the Verification section relies on a large set of external links that cannot be confirmed from the description alone.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Recent review info

Run configuration

Commits

Reviewing files that changed from the base of the PR and between 2c4310e and 7aa8b51.

Files selected for processing: 3

  • apps/server/src/socketHeartbeat.test.ts
  • apps/server/src/socketHeartbeat.ts
  • apps/server/src/ws.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 4 remain after this review.

@juliusmarminge
juliusmarminge merged commit ad44645 into main Nov 22, 2026
39 checks passed
@juliusmarminge
juliusmarminge deleted the factory/issue-40927 branch November 22, 2026 16:33
github-actions Bot added a commit to omarcresp/t3code-flake that referenced this pull request Nov 22, 2026
**v0.1.12-nightly.20261122.5111** · 30 changes from 10 contributors

- **Multi-file diffs.** Open diff now shows every file in a multi-file Codex patch.
- **Mixed-content paste.** Pasting a message with text and a picture now keeps both.
- **Queued attachments.** Edit a queued message without losing its image or file attachment chips.
- **Pull request checks.** Agents watching a pull request can recognize checks that already passed instead of waiting indefinitely.
- **Notebook outputs.** Saved HTML outputs now appear when you scroll them into view.

### Plus 24 more bug fixes and performance improvements.

<details>
<summary>Full changelog</summary>

## What's Changed
* perf(mobile): keep image bytes outside draft JSON by @t3dotgg in pingdotgg/t3code#9727
* fix(server): watch_pull_request says when checks already passed by @juliusmarminge in pingdotgg/t3code#40866
* fix(codex): Open diff shows every file of a multi-file patch by @Abhiram-745 in pingdotgg/t3code#40874
* fix(server): ACP startup gives up when the agent never answers the handshake by @juliusmarminge in pingdotgg/t3code#40864
* fix(server): a branch prefixed with another remote's name publishes under its full name by @Abhiram-745 in pingdotgg/t3code#40877
* fix(server): list open delegated tasks when task_status or task_cancel finds no match by @Project516 in pingdotgg/t3code#40886
* fix(gitlab): find merge requests opened from a fork by @Abhiram-745 in pingdotgg/t3code#40894
* fix(web): pasting a chat message with text and a picture keeps both by @juliusmarminge in pingdotgg/t3code#40909
* fix(antigravity): bound silent post-settle background command holds by @Lokkuchakreshkumar in pingdotgg/t3code#40858
* fix(desktop): WSL is not offered or started when only the Windows install stub exists by @juliusmarminge in pingdotgg/t3code#40918
* fix(server): idle /ws connections behind a reverse proxy no longer drop every 60s by @juliusmarminge in pingdotgg/t3code#40932
* fix(server): thread reads no longer attribute T3 Code's compact-before-send /compact to the user by @juliusmarminge in pingdotgg/t3code#40934
* fix(web,mobile): @-file mentions show by name in message previews, not as raw links by @tiliakoos in pingdotgg/t3code#40924
* fix(web): tool calls stay grouped after a usage-limit pause again by @matthew-waters in pingdotgg/t3code#40905
* fix(server): t3 doctor no longer reports a database just under 1 GiB as "1024.0 MiB" by @tiliakoos in pingdotgg/t3code#40952
* fix(web): show clone failure after progress is dismissed by @StiensWout in pingdotgg/t3code#40951
* Invalidate pending theme imports when a replacement is too large by @StiensWout in pingdotgg/t3code#40965
* fix(mobile): show linked thread history page errors by @StiensWout in pingdotgg/t3code#40973
* fix(client-runtime): skip waiting for lower-priority linked addresses by @StiensWout in pingdotgg/t3code#40989
* fix(web): navigate Excel sheets from the focused tab by @StiensWout in pingdotgg/t3code#41008
* fix(mobile): bound app-owned composer attachment filenames by @StiensWout in pingdotgg/t3code#40991
* fix(web): prioritize visible saved notebook outputs by @StiensWout in pingdotgg/t3code#40998
* fix(web): editing a queued message keeps its attachment chips resolved by @smirea in pingdotgg/t3code#40945
* fix(server): unlinking an environment ends its session on the other machine by @juliusmarminge in pingdotgg/t3code#41005
* fix(mobile): scope Git result banners to their originating thread by @StiensWout in pingdotgg/t3code#41015
* fix(web): keep the conversation when a pairing tab closes by @StiensWout in pingdotgg/t3code#41025
* fix: restart linked thread reads when trying again by @StiensWout in pingdotgg/t3code#41020
* fix(client-runtime): count ambiguous projects in chat file links by @StiensWout in pingdotgg/t3code#40986
* fix(mobile): keep media actions on each sent image page by @StiensWout in pingdotgg/t3code#41018
* perf(server): a run's provider turn lookup is linear, not quadratic by @navidnadali in pingdotgg/t3code#38791

## New Contributors
* @Lokkuchakreshkumar made their first contribution in pingdotgg/t3code#40858
* @matthew-waters made their first contribution in pingdotgg/t3code#40905

**Full Changelog**: pingdotgg/t3code@v0.1.12-nightly.20261122.5098...v0.1.12-nightly.20261122.5111

</details>


Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.1.12-nightly.20261122.5111
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M 30-99 changed lines (additions + deletions). vouch:trusted Author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Direct connections behind a reverse proxy drop every 60s while idle and the apps take minutes to reconnect: /ws has no server-side heartbeat

1 participant