pingdotgg / pingdotgg/t3code

[Bug]: Tailscale HTTPS - Show the "Serve is not enabled on your tailnet." error in GUI.

Open
#2,830 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs-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 am describing a concrete problem or use case, not just a vague idea.
Area

apps/desktop

Problem or use case

When enabling Tailscale HTTPS in T3 Code, doesn't report that the tailscale serve command is failing because HTTPS certificates need to be enabled on Tailscale

What happened:

I enabled Tailscale HTTPS from T3 Code Nightly.

The screen hangs with seemingly nothing happening, or the app restarts with seemingly no effect (inconsistent behaviour).
No visible errors were seen. (This is the key issue)

I verified that tailscale serve --bg --https=**** **** has error:

Serve is not enabled on your tailnet.
To enable, visit:

https://login.tailscale.com/f/serve?node=...

Proposed solution

User Fix:
Login to Tailscale and enable Tailscale HTTPS Certificates

T3 Code Fix:
Show the Tailscale error:

Serve is not enabled on your tailnet.
To enable, visit:

https://login.tailscale.com/f/serve?node=...

Additionally cancel the restart of T3 code if error occurs. (If possible)

Why this matters

The user doesn't know how to fix the problem without seeing the error.

Smallest useful scope

A toast/notification showing that an error occurred.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution
  • I would be open to helping implement this.

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 the Tailscale HTTPS enable flow under apps/desktop and reproduce the failure from tailscale serve --bg --https=.... Trace how the command error and restart are handled; done means the Serve-not-enabled message is visible in a toast or notification and the app does not restart after the error.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.