Skip to content

PR evidence: Tailscale HTTPS setup feedback (#30005)

Pre-release
Pre-release

Choose a tag to compare

@voltcrash voltcrash released this 03 Nov 07:58
abc8a9e

PR pingdotgg#30005: web client evidence

Head: abc8a9e
Baseline: cefb544
Host: Linux arm64. T3 built-in Browser panel, isolated worktree server/state.

The backend ran the actual server implementation with an isolated fake tailscale CLI. No real tailnet changes or HTTPS routing occurred.

web-before.png is a controlled UI reversion: ConnectionsSettings.tsx and SavedEnvironmentRows.tsx came from baseline; backend, contracts and fixture state remained at head. The access panel gave no Tailscale setup diagnostic. Both components were restored byte-for-byte to HEAD afterward; git status is clean.

web-after.png uses the final head components. The same denied setup is visible in Sharing & access with host-side operator permission guidance. The app remains usable on local HTTP. The server only advertises HTTPS after a successful reachability check; the fake CLI does not establish a route.

browser-observations.json records the actual browser text for denied, unknown and recovered setup. Unknown failure shows generic guidance without the fixture secret/device stderr strings. A successful fake setup followed by the normal server restart clears the warning. A no-DNS denied fixture also retained the diagnostic in the web client.

Limitations: these captures prove the real web/server flow. They do not prove Electron IPC/relaunch, desktop toggle behavior, native mobile UI, or live Tailscale HTTPS routing. Device panel verification was attempted; T3 reports that Agent device access is disabled for this environment. No alternate automation system was used.

Created with GPT-6.1 Sol in Codex through T3 Code.