Connect your devices with Tailscale

Put an agent server on your own Tailscale tailnet so your devices reach its gateway privately, with no public ports.

What it does

If you use Tailscale, you can put an agent server on your own tailnet. Your devices, such as an OpenClaw node host on your network or a home-automation box, then reach the server's gateway privately on port 18789. No public ports are opened.

It is opt-in per server. Nothing changes unless you add the key below.

Set it up

  1. In the Tailscale admin console, create an auth key. Make it Tagged (for example tag:associates; define the tag under tagOwners in your ACL first) and Pre-approved. Do not make it ephemeral. A single-use key is fine for one server, because the server keeps its Tailscale identity across refreshes. Use a reusable key if you plan to set it for every server.
  2. Save the key as a secret named TAILSCALE_AUTH_KEY. See Secrets & egress.
    • For one server, add it on that server's main agent on the Secrets tab.
    • For every server, add it as a company secret.
    • You don't need to set allowed hosts.
  3. Deploy the server. Secret changes are a full refresh, so use Deploy (or Deploy this server in Review changes). See Deploys & pending changes.

After the refresh, the server appears in your Tailscale admin console as oc-<company>-<server>. Connect to it at ws://<that name or its 100.x address>:18789, using your gateway token. A new node still needs pairing approval before it can do anything.

What the server will and won't do

  • It accepts only the gateway port, and only from your tailnet.
  • It never connects out to your other devices.
  • It doesn't use your Tailscale DNS settings or routes.
  • Tailscale SSH is off.

Your Tailscale ACLs decide which of your devices can reach it.

Remove it

Delete the TAILSCALE_AUTH_KEY secret, deploy the server, then remove the device in your Tailscale admin console.

Troubleshooting

If the server doesn't appear in your admin console after the refresh, check that:

  • the key hasn't expired or already been used (single-use keys work once, so create a new one);
  • the key is Pre-approved, if device approval is turned on for your tailnet;
  • the key's tag exists and is owned in your ACL's tagOwners;
  • the secret name is exactly TAILSCALE_AUTH_KEY, and you deployed after saving it.

Build your team.

Your first AI Teammate, working by end of day.

Get product updates by email

What we shipped and what we learned.

Product updates, a few times a quarter. Unsubscribe any time. Privacy

Protected by reCAPTCHA. Privacy · Terms