Skip to content

devlanes is in beta and not ready for production use.Report an issue

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"}

Use the box’s full MagicDNS name, which ends in your tailnet’s ts.net domain.

~/.ssh/config
Host my-vps
HostName my-vps.example.ts.net
User you

The default policy already allows traffic between your devices. With a policy of your own, let your devices reach port 22 on the box.

tailnet policy file
{
"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.

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.

on the box
$ tailscale set --ssh
tailnet policy file
{
"ssh": [
{
"action": "accept",
"src": ["autogroup:member"],
"dst": ["autogroup:self"],
"users": ["you"]
}
]
}

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.

on your machine
$ ssh my-vps true
$ devlanes remote connect my-vps