[Bug]: T3 Connect fails to establish a Cloudflare tunnel and intermittently times out during environment linking
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- macos, typescript
- Domínio
- desktop, networking
Direção de pesquisa
Start in the apps/desktop area named in the issue and trace the environment-link challenge request to https://relay.t3.codes/v1/client/environment-link-challenges, then inspect managed Cloudflare tunnel registration and its readiness diagnostics. Correlate the supplied trace IDs and timeout logs with relay and tunnel events. Done means environment linking completes and the tunnel registers with a reachable HTTPS endpoint; the root cause is still unknown, so this requires maintainer investigation.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
- Launch T3 Code Desktop (Beta v0.1.10) on macOS.
- Open Settings → Sharing & access.
- Keep Network access disabled.
- Enable T3 Connect.
- Wait for the managed Cloudflare tunnel to establish a connection.
- Repeat the test using a different network, such as a mobile hotspot.
The issue persists across multiple attempts, including home Wi-Fi and mobile data.
Expected behavior
T3 Connect should successfully link the local environment, establish the managed Cloudflare tunnel, and provide a reachable public HTTPS endpoint.
External MCP clients, including ChatGPT, should be able to connect to the environment through the /mcp endpoint using OAuth authentication, without requiring an additional third-party tunnel.
Actual behavior
T3 Connect fails at two different stages.
Scenario 1: Environment linking succeeds, but the Cloudflare tunnel fails to register
The UI displays:
"cloudflared has not connected to Cloudflare yet."
The managed connector repeatedly fails with registration timeouts. Local diagnostics recorded 34 connector starts, 31 registration timeouts, and zero successful registrations. The connector readiness endpoint returns HTTP 503 with readyConnections=0.
Scenario 2: Environment linking itself times out.
The request to https://relay.t3.codes/v1/client/environment-link-challenges fails with:
"Relay environment link challenge timed out. Your DNS or firewall may be blocking T3 Connect."
The issue has been reproduced across home Wi-Fi and a mobile hotspot. Changing DNS resolvers and VPN endpoints did not resolve it.
The local MCP server and OAuth discovery endpoints work correctly. As a temporary workaround, OpenAI Secure MCP Tunnel successfully connects ChatGPT to the same local T3 Code instance.
The precise root cause remains unknown.
Impact
Major degradation or frequent failure
Version or commit
T3 Code Beta v0.1.10
Environment
macOS 15.7.8 (arm64), Apple Silicon M1 Pro, T3 Code Desktop Beta v0.1.10, managed cloudflared v2026.10.4. Network access disabled. Local MCP server: 127.0.0.1:3773. Tested on home Wi-Fi, mobile hotspot, and multiple VPN endpoints.
Logs or stack traces
Sanitized diagnostic timeline — November 19, 2026 (UTC):
14:51:38 — Environment linking and local activation succeeded on the home network.
14:51:43 — Cloudflare tunnel registration failed:
Register tunnel error from server side: context deadline exceeded
By 15:05:14:
- Connector starts: 34
- Registration timeouts: 31
- Successful registrations: 0
- Connector readiness: HTTP 503
- readyConnections: 0
15:11:49–15:12:12 — Another environment activation succeeded, but tunnel registration failed again. Network used for this particular attempt was not confirmed.
Subsequent environment-link challenge requests timed out:
POST https://relay.t3.codes/v1/client/environment-link-challenges
15:12:38.784 UTC
Duration: 10.110 s
Trace ID: c2d27a9b32f0ee0cba2510647c41fc04
15:12:59.581 UTC
Duration: 10.009 s
Trace ID: 878fb6dba9b1cc9670950d4f9b3382c1
15:13:18.815 UTC
Duration: 10.007 s
Trace ID: 867e2b188b89c49f777806c8bb3d17de
Additional diagnostic results:
- DNS SRV resolution: successful during the latest tests
- TCP port 7844: reachable
- TLS 1.3 connectivity to Cloudflare edge: successful during the latest standalone tests
- Local MCP endpoint: HTTP 401 (authentication required, as expected)
- OAuth discovery endpoints: HTTP 200
- No successful "Registered tunnel connection" events observed
Could the maintainers check whether the relay received the challenge requests associated with these trace IDs and correlate the registration timeouts with the managed tunnel's edge events?
Thank you for your help.
Screenshots, recordings, or supporting files
Снимок экрана 2026-11-19 в 19.12.10.png
Снимок экрана 2026-11-19 в 19.12.44.png
Снимок экрана 2026-11-19 в 19.12.07.png
Снимок экрана 2026-11-19 в 19.13.23.png
Workaround
OpenAI Secure MCP Tunnel works successfully with the same local T3 Code MCP server.
ChatGPT can authenticate via OAuth, retrieve project information, send tasks to agents, and receive their results.
However, this workaround requires a separate tunnel-client process, an OpenAI API key, and additional startup configuration. Native T3 Connect would be preferable.
- Linguagem predominante
- TypeScript
- Estrelas
- 24.8k
- Forks
- 6.4k
- Merge médio
- 4h 29min
- PRs com merge (30d)
- 488
Preparar o ambiente
Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de pingdotgg/t3code
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
Mantenedores costumam responder em até 1 dia
-
needs more info
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
pingdotgg/t3code#39400 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panelTalvez já em andamento @iamdatvt94 assumiu há 1 dia. Abertabug needs-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia
-
bug needs-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 73/100
Mantenedores costumam responder em até 1 dia
Todas as issues de pingdotgg/t3code
Issues semelhantes
-
area:plugins kind:bug priority:p2 ready
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 90/100
Mantenedores costumam responder em até 1 dia
-
Escaped `*` followed by `*` (`\**`) never matchesTalvez já em andamento @bardrop assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 71/100
editorconfig/editorconfig-core-js#172 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
vega/vega-webgpu#40 ·
-
Adjust break point sizingAbertatype: bug 🐛
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 63/100
puckeditor/puck#1929 ·
Mantenedores costumam responder em até 1 dia
-
compression() compresses every response at Brotli quality 11Talvez já em andamento @staylor assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia