The Tailscale App Did Not Have a Separate Web Dashboard
A user installed Tailscale from the ZimaOS App Store on version 1.4.3. Clicking the app opened another browser window, but that window returned to the ZimaOS home page. Jellyfin launched normally, so the user assumed Tailscale itself had failed.
The reply clarified that this behavior did not mean the installation was broken. The Tailscale package did not expose a normal application interface through the ZimaOS tile. Its useful state was whether the ZimaOS host had authenticated and appeared inside the user's tailnet.
An Authentication Key Was Still Required
The missing step was configuring a Tailscale Auth Key. Without that credential, the installed service had not joined the user's network. The author generated a key by following the community Tailscale authentication setup and then confirmed that the connection worked.
Verify the Result in the Tailnet Device List
After the key is applied, check the Tailscale administration view rather than waiting for a ZimaOS-hosted dashboard. The expected result in this thread was that the ZimaOS machine appeared as a device in the tailnet.
The discussion does not document the exact App Store field name or whether later Tailscale packages use the same activation flow. It confirms only that the missing Auth Key explained this user's ZimaOS 1.4.3 behavior.
FAQ
Is Tailscale broken if its ZimaOS tile opens the home page?
Not in this case. The package had no separate dashboard to display, and the real missing step was tailnet authentication.
How did the user confirm the fix?
They generated and configured an Auth Key, then reported that Tailscale worked.
