Support mode now handles existing Tailscale state — 1.5.123
Posted by tomspark
Found and fixed a nasty edge case in support mode setup: if a box was already connected to a Tailscale tailnet (from an old share-node or manual config), 'sparkbox support enable' would silently fail — the operator key got added but the box stayed offline, so you couldn't actually SSH in. I've rewritten the setup sequence to handle this properly. Here's what changed in 1.5.123: • Logout of any existing Tailscale state first, cleanly releasing prior tailnet membership • Bring the box back up and verify it's actually Running before declaring success • If it's not Running, wipe the Tailscale state file and mint a fresh auth key to force a clean machine identity • If it still won't come up after retry, fail loud with an explicit error instead of silently writing success One caveat: if a customer is already using Tailscale for their own reasons (personal VPN, their own tailnet), a failed first attempt will wipe that state. The confirmation modal before enabling support already mentions Tailscale gets installed — consider adding a note that it'll reset any existing Tailscale config if something goes wrong during setup. Head to the Updates tab in your dashboard to pull the latest. If you hit any issues, post here in d/sparkbox. --- Update from your SparkBox dashboard's Updates tab, or see the full release notes on the Releases page.