SSD Nodes Learn Hosting plans →
How to do am Matt ConnorBy Matt Connor

How to Fix Tailscale Install Error for Ubuntu

If apt dey fail with a release codename, signing keyring, or status code error, check the exact message and fix Tailscale repository setup for Ubuntu.

Why Tailscale install errors for Ubuntu na apt errors

Tailscale install errors for Ubuntu almost always happen before any Tailscale code run. Na apt errors. When dem check am against Ubuntu package archive for October 2026, no tailscale package dey there: na only Go helper libraries and python3-tailscale match. So normally, the daemon dey come from Tailscale own apt repository for pkgs.tailscale.com. Canonical still dey maintain Tailscale snap, and we cover am with the other fallback options near the end.

When you add that repository, e dey write two files. One file tells apt where the packages dey. The other one holds the public key wey apt uses to check the signature for the repository index. Almost every failure below happen because one of those two files no correct, or because one device between apt and the repository dey reject the request.

These na the commands Tailscale publishes for Ubuntu 24.04:

sudo mkdir -p --mode=0755 /usr/share/keyrings
curl -fsSL https://pkgs.tailscale.com/stable/ubuntu/noble.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null
curl -fsSL https://pkgs.tailscale.com/stable/ubuntu/noble.tailscale-keyring.list | sudo tee /etc/apt/sources.list.d/tailscale.list
sudo apt-get update && sudo apt-get install tailscale

noble na the codename for Ubuntu 24.04, and e dey appear for both URLs. The second command writes one comment line and one deb line inside /etc/apt/sources.list.d/tailscale.list, while cat shows you exactly wetin enter there.

cat /etc/apt/sources.list.d/tailscale.list

Read that deb line as an address wey get four fields: the bracketed option [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg], then the repository base, which be pkgs.tailscale.com/stable/ubuntu wey apt reaches through https, then the suite noble, and lastly the component main. apt joins the base and the suite into one URL and fetches am: https://pkgs.tailscale.com/stable/ubuntu/dists/noble/InRelease. If you fetch that URL by hand, e tests that request; e no prove say apt own request go succeed.

Read the apt error before you change anything

Run the update by itself so nothing go scroll the error comot.

sudo apt update

A failed third-party repository fit look like this. The codename and the IP address go different for your machine.

E: Failed to fetch https://pkgs.tailscale.com/stable/ubuntu/dists/wilma/InRelease  404  Not Found [IP: 203.0.113.9 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.

Two things for that output decide wetin you go do next: the status code, and the complete URL for the E: Failed to fetch line. No guess from the summary line for the bottom. Copy the URL and ask the server yourself.

curl -sS -o /dev/null -w '%{http_code}\n' https://pkgs.tailscale.com/stable/ubuntu/dists/noble/InRelease

That go print 200 for a codename wey Tailscale publishes for. We check am for October 2026, and noble return a signed index wey carry Origin: Tailscale and Codename: noble. Replace noble with the codename from your own error and run am again. If curl receive 200 where apt get fetch error, the repository answer curl request, but that one no prove say apt configuration dey wrong: filtering for the service or anywhere along the path fit separate requests based on headers like the user agent. A 200 only prove say the download work, though: apt still check the signature for that index after e download am, and key problem go fail for that stage. The keyring section below cover that one.

Wetín the status code dey tell you

  • 404 Not Found mean say the server no find file for that path, or e no wan reveal say the file dey there. For pkgs.tailscale.com, wey dey serve files without credentials, na almost always the codename for the URL.
  • 403 Forbidden mean say something answer and refuse the request. A 403 by itself no show whether na proxy, filtering appliance, or firewall between your server and Tailscale cause the refusal, or whether na the service itself cause am. AWS document say CloudFront distribution fit return 403 from its own side too, for example because of firewall rule or the origin server.
  • 407 Proxy Authentication Required mean say proxy require authentication for this request: either apt no send proxy credentials, or e send credentials wey proxy reject as invalid or incomplete. 401 Unauthorized different: na challenge for credentials to the requested resource itself, and e dey send with a WWW-Authenticate header. By itself, e no show say proxy dey involved. This repository dey serve its files without credentials, so 401 usually mean say another thing answer for that URL, like an intercepting gateway. The debug command for the proxy section go show which host apt actually reach.
  • Connect error or name resolution error mean say no HTTP conversation happen at all. Go the IPv6 section.

Codename wey dey for URL na one Tailscale no publish

Tailscale dey build separate directory for every Ubuntu codename. If you request codename wey no dey there, you go get 404, because server no get dists/<codename> to serve. Vendor listing for pkgs.tailscale.com/stable show the ones wey dey available. For October 2026, the list dey from 16.04 reach stonking, wey be Ubuntu 26.10, with resolute, wey be Ubuntu 26.04, directly under am.

The usual way wrong codename dey enter na when you run lsb_release -cs for distribution wey base on Ubuntu but no be Ubuntu. For Linux Mint 22, that command print wilma, wey be Mint own codename, and Tailscale no publish anything for am. Read the Ubuntu base instead.

. /etc/os-release
echo "$VERSION_CODENAME $UBUNTU_CODENAME"

For Ubuntu, both values dey the same. For derivative, VERSION_CODENAME na the derivative name and UBUNTU_CODENAME na the Ubuntu release wey e build on. Use UBUNTU_CODENAME for both URLs.

The second way na release upgrade. Ubuntu upgrade tool dey disable third-party sources when e dey run, so after upgrade Ubuntu 24.04 to 26.04 you go find /etc/apt/sources.list.d/tailscale.list either commented out or still dey name noble for machine wey don become resolute. Fix am by running the two curl commands again with the new codename; dem go overwrite both files. If the upgrade stop halfway, so dpkg dey complain about half-configured packages and no be only this repository, recover the failed release upgrade first, because no fix to tailscale.list go hold for system wey apt no fit finish configuring.

The third way na timing. If you install for new Ubuntu release before Tailscale add its codename, you go get the same 404. That period often short or no dey at all: Tailscale tracking issue for Ubuntu 24.04 install support close as completed for January 2024, months before that release ship. For Ubuntu 26.10, checked on 24 October 2026, dists/stonking/InRelease return signed index wey carry Origin: Tailscale and Codename: stonking, so if you see 404 for stonking earlier, fetch am again before you use workaround. If you enter that period, pointing the file to previous LTS codename normally go install, because these packages get few dependencies, but selecting that repository no automatically select Ubuntu-release-specific build: Tailscale deb builds target Linux architectures like amd64 and arm64. Check wetin you actually get with apt policy tailscale, and move the file back once the real codename appear.

Keyring empty, and the command wey write am no talk anything

This one quiet, and na where plenty of these problems dey end. Look the keyring command again:

curl -fsSL https://pkgs.tailscale.com/stable/ubuntu/noble.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null

Shell dey build the whole pipeline before any of the two programs run, so sudo tee go open the keyring path and truncate am to zero bytes immediately. If curl later fail, and -f make am fail for any HTTP error, curl no go write anything and e go exit with nonzero status. The file go remain at zero bytes. Pipeline exit status na the status of the last command, wey be tee, and e succeed. Nothing go print, and you go move to the next command thinking say the key don install.

Check the file, no be the command wey create am.

ls -l /usr/share/keyrings/tailscale-archive-keyring.gpg
gpg --show-keys /usr/share/keyrings/tailscale-archive-keyring.gpg

Healthy keyring go print a pub line and a uid line wey name Tailscale. File wey get zero bytes go print gpg: no valid OpenPGP data found. and nothing else. File wey catch HTML error page go print the same thing, and head -c 80 on top am go show the beginning of a web page instead of binary key data.

If keyring no hold any usable key, sudo apt update go download the index and then reject am. You go see a W: GPG error line wey name the Tailscale repository and its suite, the text The following signatures couldn't be verified because the public key is not available: NO_PUBKEY followed by a 16 character key id, and underneath an error wey talk say the repository no get signature. Pay attention to wetin apt dey tell you: e download the index well, but e no fit check the signature. Na key problem be that, no be network problem. If keyring file no dey at all, the message go different again, and e go name the path directly with Could not open file /usr/share/keyrings/tailscale-archive-keyring.gpg.

Write the key in two steps, so failed download no fit damage a working keyring.

curl -fsSL https://pkgs.tailscale.com/stable/ubuntu/noble.noarmor.gpg -o /tmp/tailscale.gpg
gpg --show-keys /tmp/tailscale.gpg
sudo install -m 0644 -o root -g root /tmp/tailscale.gpg /usr/share/keyrings/tailscale-archive-keyring.gpg

The middle line na the gate: if e no print a Tailscale uid, stop and no copy the file. Mode 0644 matter because apt dey switch to the unprivileged _apt user to fetch and verify, so keyring wey only root fit read na keyring apt no fit use.

Both .list and .sources file fit describe the same repository

Ubuntu move its own sources go deb822 format for Ubuntu 24.04 LTS, where /etc/apt/sources.list become /etc/apt/sources.list.d/ubuntu.sources. Tailscale still dey publish the one line format. When dem check am for October 2026, the matching .sources URL for pkgs.tailscale.com return 404. If your machine get both tailscale.sources and tailscale.list wey describe the same repository, apt don get that repository described two times.

The mild version na warning for every update:

W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/tailscale.list:1 and /etc/apt/sources.list.d/tailscale.sources:1

The serious version happen when the two files name different keyring paths, because apt no fit decide which key go control the repository. E print E: Conflicting values set for option Signed-By regarding source, then the repository and its suite, then the two keyring paths with != between dem, and then e refuse to continue:

E: The list of sources could not be read.

That one block every apt command, no be only the update, until one of the files comot. The same failure dey show for Ubuntu own repositories, and the duplicate apt source error after deb822 migration explain the general case.

Find every file wey mention Tailscale before you delete anything.

grep -RIn tailscale /etc/apt/sources.list /etc/apt/sources.list.d/

Keep one file. To disable the other without losing am, rename am: apt dey read only files wey end with .list or .sources, so tailscale.list.bak go skip am and e go remain for disk as reference.

How to write the deb822 source file correctly

If you prefer the newer format, convert the file wey you already get instead of typing the repository address again, because na typo there dey cause the errors above. Recent apt releases get a converter wey dey rewrite .list files into deb822 stanzas and move the signed-by option across as Signed-By.

apt modernize-sources --help
sudo apt modernize-sources

Ubuntu 24.04 ship with apt wey older than that subcommand, so the help line go tell you quickly whether your own get am. If e no get am, build the stanza from the line wey already dey for disk, so the base go come from the vendor file instead of your keyboard.

. /etc/os-release
{
  echo 'Types: deb'
  echo "URIs: $(awk '/^deb /{print $3}' /etc/apt/sources.list.d/tailscale.list)"
  echo "Suites: $UBUNTU_CODENAME"
  echo 'Components: main'
  echo 'Signed-By: /usr/share/keyrings/tailscale-archive-keyring.gpg'
} | sudo tee /etc/apt/sources.list.d/tailscale.sources
sudo rm /etc/apt/sources.list.d/tailscale.list

That command go print the stanza wey e write, so you fit read the fields again before the next apt update. Four of dem important to understand well, because each one fit fail for different way:

  • URIs stops for the repository base. If you paste the dists/noble part inside am, e go give 404, because apt dey append dists/<suite> by itself and ask for dists/noble/dists/noble.
  • Suites na the codename, exactly the value wey dey for the middle of the one-line format.
  • Signed-By takes absolute path to a keyring file. E also accepts armored key wey you put directly underneath am, where every key line get one space indentation and each blank line inside the key dey written as one dot.
  • Enabled: no switches source off without deleting am. This one easier to undo than renaming the file, and easier to explain to the next person.

Keep one stanza for each file for third-party repositories. If you keep several together, put blank line between the stanzas. The repository index lists amd64 and arm64 among its architectures, so ARM VPS no need extra Architectures field.

Proxy wey dey middle dey return 403

403 mean say dem refuse the request, but e no show where the refusal happen: device wey dey between your server and Tailscale, or filtering for the service, fit return am. Start with apt own configuration, because proxy wey you set there go apply to apt, but e no go apply to your interactive curl.

grep -RIn -i proxy /etc/apt/apt.conf.d/ /etc/apt/apt.conf
sudo apt-config dump | grep -i 'acquire::http'

Then monitor wetin apt actually dey send.

sudo apt -o Debug::Acquire::http=1 update

This one go print the request line, the headers wey apt send, and the proxy wey e connect through, if any. Compare am with plain curl to the same URL. If curl return 200 and apt return 403, compare the request headers together with the proxy settings; filtering for the service or along the path fit tell the difference based on user agent:

curl -sS -o /dev/null -w '%{http_code}\n' -A 'Debian APT-HTTP/1.3' https://pkgs.tailscale.com/stable/ubuntu/dists/noble/InRelease

If that one return 403 while the default curl return 200, the response dey differ based on the user agent, but the test no show where the filter dey. Check filtering rules for your network, and report the different responses to Tailscale if those rules no explain dem. If every request from your server dey get 403, run the same curl from a machine for another network: 200 there show say the refusal depend on the client or network, but service-side rules like geographic restrictions fit also cause that difference. Check Tailscale status page too; 403 from both networks no by itself show where the block dey. Corporate proxy wey dey inspect TLS behave differently again: apt go report certificate verification failure if your server no trust the proxy's issuing certificate authority. Cloud egress firewall wey only allow the Ubuntu mirrors na the other common source, and for that case, the fix na to allow pkgs.tailscale.com for the firewall.

IPv6-only egress, and the errors wey no be status codes

If apt no ever receive HTTP response, test each protocol separately.

curl -4 -sS -o /dev/null -w 'v4 %{http_code}\n' https://pkgs.tailscale.com/stable/ubuntu/dists/noble/InRelease
curl -6 -sS -o /dev/null -w 'v6 %{http_code}\n' https://pkgs.tailscale.com/stable/ubuntu/dists/noble/InRelease

When IPv4 dey answer and IPv6 hang or report Network is unreachable, IPv6 test don fail, but that one alone no explain why apt fail. APT 2.8 already dey alternate address families and start another connection attempt after default 250 milliseconds. Force one run use IPv4 to test whether e go change apt result:

sudo apt -o Acquire::ForceIPv4=true update

If that update succeed, make the change permanent.

echo 'Acquire::ForceIPv4 "true";' | sudo tee /etc/apt/apt.conf.d/99force-ipv4

Make we talk true about the opposite case. For VPS wey no get IPv4 address at all, forcing IPv4 no go fix anything, because no IPv4 route dey to force traffic through. If repository no reachable over native IPv6, you need NAT64 with DNS64 from your provider, or a proxy wey get IPv4 address. A connect error wey name IPv6 address show say IPv6 connection attempt fail; use the curl -6 line to test that path separately.

The fallbacks, and wetin each one go cost

The vendor install script. curl -fsSL https://tailscale.com/install.sh | sh na the command wey Tailscale dey advertise. If you read the script, e go detect your distribution from /etc/os-release, then e go write the same two paths wey this guide don dey fix, /usr/share/keyrings/tailscale-archive-keyring.gpg and /etc/apt/sources.list.d/tailscale.list, from the same URLs. This matter because e set the correct expectation: e no go bypass repository wey proxy dey block. E go fail the same way, but e go show less output. If you pipe downloaded script enter shell as root, na trade you dey make, no be solution, because you dey trust anything wey server return at that moment, and you no keep copy of wetin run. If you choose this trade, make you understand the risk well:

curl -fsSL https://tailscale.com/install.sh -o install.sh
less install.sh
sh install.sh

The static binaries. The same server dey publish plain tarballs under the static binaries section of pkgs.tailscale.com/stable. As of 3 November 2026, the stable release na 1.104.5, wey dem release on 2 November, and the 64 bit x86 file na tailscale_1.104.5_amd64.tgz. The page still get link to older versions. You go place the tailscale client and tailscaled daemon by yourself, and you go supervise the daemon by yourself, so no apt upgrade path dey available; version 1.104.5 support updating static installation with sudo tailscale update by downloading replacement tarball. E make sense for air gapped host, or when you must pin one exact version.

Ubuntu own package. When dem check am for October 2026, the archive no get tailscale deb, so sudo apt install tailscale without the vendor repository end for E: Unable to locate package tailscale. Canonical dey publish snap, and you fit install am with sudo snap install tailscale. Because e come from Snap Store, e dey avoid every apt error wey we don mention above. When dem check am on 3 November 2026, the 1/stable channel carry 1.102.3, wey old pass Tailscale current 1.104.5. The listing talk say Canonical dey maintain am, and upstream developers no necessarily endorse am. E dey update according to snapd schedule. How to control snap updates for Ubuntu Server explain how to manage am. If wetin you really want na coordination server wey you control instead of Tailscale hosted one, na separate decision be that: How to run Headscale as your own control server cover am, while The comparison between Tailscale and plain WireGuard explain whether you need any of this machinery.

Package don install, but tailscaled no go start

Once apt dey okay, na daemon failure go start show.

systemctl status tailscaled
sudo journalctl -u tailscaled -n 50

For VPS wey dey use container virtualisation and share host kernel, like LXC or OpenVZ, if log show say /dev/net/tun no dey, e mean say container no get TUN device available. Daemon need TUN device to create tailscale0 interface, but container never get one. Ask your provider make dem enable TUN for the container, or move to KVM plan wey give you your own kernel. For KVM, guest still need tun kernel module; Tailscale Linux documentation talk say make you load am with sudo modprobe tun if e no dey.

After that, sudo tailscale up go print login URL, and tailscale status suppose list your machine with address for 100.64.0.0/10 range. Machine wey appear there na machine wey you fit build on, whether na advertise private subnet from your VPS or use the VPS as exit node.

FAQ

Why apt dey talk say the Tailscale repository no get signature?

Na because apt download the repository index but e no fit verify the signature against /usr/share/keyrings/tailscale-archive-keyring.gpg. The common reason na say the keyring get zero bytes: sudo tee cut the file short before curl fit download anything, and the pipeline report success because tee succeed. Run gpg --show-keys /usr/share/keyrings/tailscale-archive-keyring.gpg. A working keyring go print one pub line and one uid line wey name Tailscale, while empty or corrupt one go print gpg: no valid OpenPGP data found. Download the key go temporary file, check am there, then copy am enter the correct place with mode 0644 so _apt user fit read am.

Which Ubuntu codename I suppose put for the Tailscale URLs?

Use the value of UBUNTU_CODENAME from /etc/os-release. The value na noble for Ubuntu 24.04, resolute for Ubuntu 26.04, and stonking for Ubuntu 26.10. No use lsb_release -cs for distribution wey derive from Ubuntu. For Linux Mint 22, e print wilma, Tailscale no publish anything under that name, and apt report 404 for dists/wilma/InRelease. Confirm your choice before you edit anything by fetching the index by hand with curl -sS -o /dev/null -w '%{http_code}\n' against https://pkgs.tailscale.com/stable/ubuntu/dists/<codename>/InRelease.

E safe to run the Tailscale install script piped into shell?

Na trade-off wey you suppose choose deliberately. The script come from Tailscale, and e do the same things as the manual steps: e read /etc/os-release, write the same keyring and the same /etc/apt/sources.list.d/tailscale.list, then install the package. The cost be say you run anything wey the server return at that moment, with root, and you no keep any record of am. Download am with -o install.sh, read am, then run am if you want the convenience without the blind spot. E still no fit help with blocked repository, because e use the same URLs wey already fail.

How I fit install Tailscale for Ubuntu without the apt repository?

You get two options. The first one na the snap wey Canonical maintain, sudo snap install tailscale. As of 3 November 2026, e carry 1.102.3 for 1/stable channel, and Tailscale no necessarily endorse am. The second one na static tarballs wey dem publish for pkgs.tailscale.com. As of 3 November 2026, dem dey version 1.104.5, with an amd64 file wey dem name tailscale_1.104.5_amd64.tgz. With the tarballs, na you go install the tailscale and tailscaled programs, and na you go run the daemon under systemd. No apt package dey to pull new version, but version 1.104.5 support sudo tailscale update for static installations. When dem check am for October 2026, Ubuntu archive no get any tailscale deb of its own. So sudo apt install tailscale for machine wey no get the vendor repository stop for E: Unable to locate package tailscale.

Dis article help you?