pingdotgg / pingdotgg/t3code

[Bug]: Tailscale connect completely broken after recent nightly update

Open
#9,869 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce

I can't really give a clear reproduction of this, because I don't know what is causing it. It was working perfectly since the remote environments were released, then randomly today I had a nightly update and when it finishes all my remote environments were stuck on "Finalizing Update".

Expected behavior

It should connect and work like it previously did.

Actual behavior

It doesn't connect via the T3Code app.

I manually updated the server on the remote environments, but now when I try and connect T3Code just gives this error "Failed to fetch remote environment endpoint http://domain/.well-known/t3/environment (HttpClientError: Transport error (GET http://domain/.well-known/t3/environment))."

Strange part is, if I copy the URL and paste it into a browser on my client instead of the T3Code app, it works fine.

I've attempted completely uninstalling on both client and server, and it is refusing to work anymore.

Impact

Blocks work completely

Version or commit

No response

Environment

No response

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in apps/web by tracing the T3Code app request to the remote environment endpoint at /.well-known/t3/environment. Compare the app's failed request with the same URL in a browser, and consider the issue resolved when the app connects to remote environments after a nightly update.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.