Integrations

Tailscale

Configure the widget with OAuth and distinguish between the widget, remote access, and auth key.

Three different use cases are often confused:

Use caseRequired identifierWhere to configure
Display tailnet devices in the widgetOAuth Client ID + OAuth Client SecretNasDash, shared integration connection
Access NasDash remotely via TailscaleNo secret in NasDashTailscale client on each machine
Automatically enroll a new machineTailscale auth keyOn that machine, not in the widget

Create the widget identifier

  1. Open the OAuth client console.
  2. Generate a client with only required device read permissions, such as devices:core:read.
  3. Copy its Client ID and secret immediately.
  4. Save a Tailscale connection in Settings → Integrations, entering tailnet, Client ID and secret.
  5. All Tailscale widgets use the Tailscale or Headscale connection saved last; save the desired connection last. There is no per-widget selector.

The tailnet can be its DNS name or the identity shown in your console. OAuth clients and their scopes are explained in the official Tailscale documentation.

Do not paste an auth key into the widget

A key typically starting with tskey-auth- is used to connect a machine to the tailnet. The widget expects an OAuth client secret, usually presented as tskey-client-..., along with its Client ID.

Access NasDash via Tailscale

  1. Install Tailscale on the host running NasDash and on the client machine.
  2. Connect both to the same tailnet.
  3. Keep the NasDash port accessible on the Tailscale IP or use a private reverse proxy.
  4. Open http://IP_TAILSCALE:2504.

This method does not require enabling the widget. Still, protect NasDash with strong passwords and appropriate Tailscale ACLs.

Rotation

Create a new OAuth client, replace the secret in NasDash, verify the widget, and then revoke the old client. A backup of /app/data contains the encrypted configuration; protect it as a secret.

Headscale

Create a Headscale connection in Settings → Integrations with its server URL and API key. Saving it last makes every Tailscale widget use it. Remote access to NasDash remains a separate network setup.