tailscale: `tailscale up` indefinitely hangs on Debian Bookworm, Tailscale version 1.62.1

What is the issue?

tailscale up indefinitely hangs on Debian Bookworm, Tailscale version 1.62.1. I expect tailscale up to work like normal.

journalctl -u tailscaled.service and systemctl status tailscaled log output:

Apr 03 11:28:08 shitbook tailscaled[1906]: control: LoginInteractive -> regen=true
Apr 03 11:28:08 shitbook tailscaled[1906]: control: doLogin(regen=true, hasUrl=false)
Apr 03 11:28:13 shitbook tailscaled[1906]: Received error: fetch control key: Get "https://controlplane.tailscale.com/key?v=88": context deadline exceeded

Ignore my hostname, I’m actually running this on a Chromebook (shouldn’t be the problem as it worked before).

Steps to reproduce

  1. Run the install script
  2. Run sudo tailscale up
  3. Hangs infinitely until I press ctrl+c. The output given when pressing ctrl+c is context canceled.

Are there any recent changes that introduced the issue?

I have no idea. I do know that I’m installing on a fresh machine. Tailscale worked fine on the previous install. I had never updated the package so this could be why I’m experiencing this now. sudo tailscale login also hangs indefinitely. I had removed my last install’s machine removed from the admin panel, and since I’m not logged in, that wouldn’t help anyways.

OS

Linux

OS version

Debian Bullseye

Tailscale version

1.62.1

Other software

I do not have any extra software.

Bug report

BUG-70f373e33198105f37a0c5547e166ee0d4ea0ee480add064d13a7af56f428398-20240403162538Z-c3cf4b4356b6ca23

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 6
  • Comments: 38

Most upvoted comments

I encountered the same issue on Ubuntu 22.04.4 LTS, then ran

sudo service packagekit restart

It works now

I don’t think that’s the problem, after all even as today IPv6 adoption globally is estimated around 45% and 47% in USA. So requiring an IPv6 address for tailscale to work it not a smart move. Specially if it has been working for years just fine using IPv4.

In my case I encountered this problem first a month ago in the managed network in my workplace and in college. But in my home that uses IPv4 behind double NAT because the ISP hasn’t started the adoption process of IPv6 yet, it still working just fine.