tailscale: Raspberrypi 4: tailscaled.sock: connect: no such file or directory

Hi,

No luck getting tailscale to work on my Raspberrypi 4.

The same error below goes for stable vs unstable builds, tried both.

Here is the latest unstable build attempt. Has not changed in days.

Installs fine, but when I try to then run it:

sudo tailscale up
[sudo] password for pi: 
logtail started
Program starting: v0.97-38-ga4b33970: []string{"tailscale", "up"}
LogID: ddb9dc397b87fb08f7820212323fa79386499adf91dd1840978f138d682ed272
Failed to connect to connect to tailscaled. (safesocket.Connect: dial unix /var/run/tailscale/tailscaled.sock: connect: no such file or directory)

To Reproduce Steps to reproduce the behavior:

Following guide @ https://tailscale.com/kb/1043/install-raspbian-buster
Errors out @ Step 4

Expected behavior Expected for tailscale to run and give the url for first time login

Version information:

Raspberrypi 4
Linux raspberrypi 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux
Tailscale v0.97-38-ga4b33970

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 2
Comments: 19 (9 by maintainers)

Most upvoted comments

I ran into this issue today. My issue was that I forgot that I disabled the tailscaled.service a while back.

sudo systemctl enable tailscaled.service
sudo systemctl start tailscaled.service

smplman on Jun 4, 2021

I ran into this with a missing tun device after an initial install (PLUS an apt ugprade) I think that during the apt upgrade it upgraded the kernel (and perhaps moved the DKMS modules) so it couldn’t find the tun module. After a reboot (and now using the new kernel), everything is happy! Just hoping this helps someone else!

drasch on Dec 4, 2020

Mac being unable to ping itself is a known quirk of how mac implements VPN support (basically our network engine runs in a little sandboxed universe managed by macOS, and macOS is in charge of the routing between the OS and that sandbox… And for some reason self-pings don’t work). It’s on our list to figure out if we can work around it, but for now that’s “working as designed” from macOS’s POV.

Glad to hear it’s all working now! We definitely made huge improvements to connectivity in the last few weeks, so I’m not surprised upgrading the older nodes helped a bunch.

I’ll open a new bug for the Windows about screen and version stuff. I wouldn’t be surprised to find a // TODO in there about that, we got popular a little ahead of schedule and have been catching up since.

danderson on Mar 28, 2020