T3 CONNECT — real CLI proof | commit 1f698f01d9 Linux · fresh isolated data · test relay · same steps on both commits Account authorized with connect login --headless; connect link completed. Paths and test-account identity omitted from displayed command output. $ t3 serve Starting the real server and waiting for a reachable tunnel... $ t3 connect status T3 Connect Exposure: enabled Authorization: stored credential Environment link: provisioned Relay: https://relay-factory.t3.codes Publish agent activity: disabled Relay client: available via managed install Path: Version: 2026.10.4 ✓ Other devices can reach this machine · Tunnel connected · 2 connections · QUIC Revoking this test environment through relay DELETE /v1/client/environment-links/ Relay response: HTTP 500 {"_tag":"RelayInternalError","code":"internal_error","reason":"upstream_unavailable","traceId":"f01728802914d90af96c18a93cf4da66"} AFTER REVOCATION | commit 1f698f01d9 $ t3 connect status T3 Connect Exposure: enabled Authorization: stored credential Environment link: provisioned Relay: https://relay-factory.t3.codes Publish agent activity: disabled Relay client: available via managed install Path: Version: 2026.10.4 ✕ T3 Connect is NOT reachable from other devices The T3 Connect address answered with HTTP 530 (Cloudflare error 1016). Fix: Restart T3 Code. If it stays, run `t3 connect` again. More info: https://github.com/pingdotgg/t3code/blob/main/docs/user/t3-connect-troubleshooting.md#the-tunnel-works-but-t3-code-does-not-answer $ stop server; t3 serve Following the restart advice once... AFTER ONE RESTART | commit 1f698f01d9 $ t3 connect status T3 Connect Exposure: enabled Authorization: stored credential Environment link: removed from T3 Connect Relay: https://relay-factory.t3.codes Publish agent activity: disabled Relay client: available via managed install Path: Version: 2026.10.4 ✕ T3 Connect is NOT reachable from other devices The T3 Connect address answered with HTTP 530 (Cloudflare error 1016). Fix: Restart T3 Code. If it stays, run `t3 connect` again. More info: https://github.com/pingdotgg/t3code/blob/main/docs/user/t3-connect-troubleshooting.md#the-tunnel-works-but-t3-code-does-not-answer Next: Run `t3 connect link --base-dir ` to link this environment again.