Connect over Tailscale
Your machine reaches a box on your tailnet as it reaches any SSH host, and everything devlanes mirrors travels inside that one SSH connection, so nothing needs Tailscale Serve or Funnel.
::example{slug="remote-ssh-box"}
Name the box
Section titled “Name the box”Use the box’s full MagicDNS name, which ends in your tailnet’s ts.net domain.
Host my-vps HostName my-vps.example.ts.net User youAllow SSH in the tailnet policy
Section titled “Allow SSH in the tailnet policy”The default policy already allows traffic between your devices. With a policy of your own, let your devices reach port 22 on the box.
{ "grants": [ { "src": ["autogroup:member"], "dst": ["autogroup:self"], "ip": ["tcp:22"] } ]}Keep your key in an SSH agent, then pair and connect as Connect to a box describes.
If the box uses Tailscale SSH
Section titled “If the box uses Tailscale SSH”Tailscale SSH signs you in by your tailnet identity instead of a key. Turn it on in the box’s Tailscale client, and add an ssh rule with the accept action, so connects and reconnects need nobody at the keyboard.
$ tailscale set --ssh{ "ssh": [ { "action": "accept", "src": ["autogroup:member"], "dst": ["autogroup:self"], "users": ["you"] } ]}If the rule asks for a check
Section titled “If the rule asks for a check”A rule with the check action, which a new tailnet uses by default, asks for a browser sign-in your daemon cannot show you. Change it to accept, or pass the check in a terminal and connect within the check period.
$ ssh my-vps true$ devlanes remote connect my-vps