Skip to content

fix(services): stop relay log spam with cloudflared 2026.11.1 - #153

Open
0libote wants to merge 2 commits into
dizys:mainfrom
0libote:fix/cloudflared-relay-min-version
Open

0libote wants to merge 2 commits into
dizys:mainfrom
0libote:fix/cloudflared-relay-min-version

Conversation

@0libote

@0libote 0libote commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

T3 Code containers built from this image spam their logs (~645 lines per 15 minutes on a live deployment) with an endless loop of:

  • ERROR: T3 Connect is NOT reachable from other devices — The tunnel client (cloudflared) is not running
  • WARN: T3CODE_CLOUDFLARED_PATH must point to cloudflared 2026.10.3 or newer

…and the relay tunnel never starts, so the machine is unreachable from other devices.

Why it happens

After the October 2026 Cloudflare certificate compromise, T3 Code requires a relay client ≥ 2026.10.3 and checks the version reported by the executable at T3CODE_CLOUDFLARED_PATH. In this image that path is the on-demand shim, whose --version comes from the build-time catalogue (/opt/t3-services/catalogue.json) — pinned to 2026.5.2 via ARG CLOUDFLARED_VERSION.

Because the shim is the configured override, T3 Code also never falls back to downloading its own managed client. Both paths are blocked, so it retries forever and the error loop spams the logs.

The fix

  • Bump the image pin 2026.5.2 → 2026.11.1 (latest stable, published 2026-11-17) in the Dockerfile ARG and the service-catalogue.mjs generator default. No checksum changes needed — the catalogue sha256 is computed at build time from the downloaded bytes.
  • Harden the smoke test: cloudflared_matches_t3 only compared the image against its own Dockerfile pin, which would pass for any stale version. It now also fails when the pin drops below T3 Code's 2026.10.3 floor, so this regression can't come back unnoticed.

Validation

  • Unit suites pass: 42/42 (service-packages, connect, services-recovery).
  • bash -n clean; floor logic verified: 2026.11.1 pass, 2026.10.3 pass, 2026.5.2 fails as intended.
  • End-to-end confirmation from the live deployment that motivated this: after the same version bump was applied to a running v0.28.7 container, t3 connect status reported the tunnel up (4 QUIC connections to the edge) and the log spam stopped.

T3 Code requires a relay client >= 2026.10.3 and rejects the image's
2026.5.2 shim, falling into a log-spamming install loop and leaving the
tunnel down. Pin 2026.11.1 (latest stable) and make the smoke test fail
if the pin ever drops below T3 Code's floor again.
0libote added a commit to 0libote/t3code-docker that referenced this pull request Nov 21, 2026
0.1.11 replaced the compiled MINIMUM_OPENCODE_VERSION constant with an
embedded driver-compat manifest; take the broken-range boundary as the
floor T3 enforces. 1.14.19 stays the floor, so the catalogue and the
installed 1.19.6 still meet it. Also carry the cloudflared 2026.11.1
bump from dizys#153: the newer bundled runtime enforces its 2026.10.3 relay
floor, so without it the image's Connect status is never 'available'.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant