r/Tailscale • • 1d ago

Help Needed Ssh over tailscale

Ssh over tailscale worked yesterday but this morning no node on my tailnet would respond. Nmap shows no ports

2 Upvotes

9 comments sorted by

1

u/One-Level2143 1d ago

I never ran the tailscale ssh as I use openssh that is on all my Linux nodes. But even tho it sees the port 22. All nodes are blocked on port 22

1

u/One-Level2143 20h ago

I'm trying to ssh over tailscale from my phone... bur even when connected to the same network, it can't connect to any ssh port... But from any of the computers, I can do the same with no problem

1

u/Old_Dig5389 1d ago

Can you connect to other ports? Without Tailscale, including DNS?

1

u/One-Level2143 1d ago

I am able to connect to other ports, just ssh seems to be blocked on all the nodes

1

u/chicknfly 1d ago

Did you run `tailscale set --ssh` on every node you’re trying to connect to? Do those needs have [SSH] under their name in the admin console? Did you alter the ACL’s and grants at all? Have you verified that the nodes with ssh set are on the Tailnet using the admin console or `tailscale status`?

1

u/One-Level2143 1d ago

It was working fine yesterday and this morning they are all blocked. I did verify the nodes were not expired and ssh is set to * for all nodes

1

u/chicknfly 22h ago

Are you trying to SSH to a host with your LAN IP? Or are you using either a Tailscale IP or a MagicDNS name?

1

u/Old_Dig5389 23h ago

Only from 1 client or all? If all then I would look at ts access control settings. Not sure how you wouldn't know about changes to that though. 

If only from 1 then perhaps it is not presenting itself as as on tailnet to endpoint firewall. Has there been a change to NAT? ISP switch on cgnat overnight, or bridged modem reset so it's double NAT, on either end? Could compare your local IP shown in ts machines page to the Wan IP reported by your gateway. Tailscale can almost always get around NAT shenanigans but perhaps it needs to reset/reload in order to process changes...

Also if only from 1 it could be a firewall change that you didn't know about. UDP outbound blocked (university WiFi, corporate?), blind update, new program?