Tailscale Exit Node: Setup, Fixes & VPS Guide
Learn what a Tailscale exit node does, set one up on Linux, fix missing-node and no-internet errors, and choose an always-on server.
Quick answer
A Tailscale exit node routes a client's general internet traffic through one approved tailnet device, so websites see that device's public IP and location. On Linux, enable IP forwarding, run sudo tailscale set --advertise-exit-node, approve Use as exit node in the Admin Console, then select it on each client. A home PC works, but it must stay awake, shares the residential uplink, and provides only the home location. A small VPS gives you an always-on Linux exit node, stable public IP, selectable region, remote administration, and an easy path to add another regional exit.
What is a Tailscale exit node?
A Tailscale exit node is a tailnet device that forwards a client’s general internet traffic. After a laptop or phone selects it, websites see the exit node’s public IP address and location. Traffic to the rest of the tailnet still follows Tailscale’s private routing.
Your client
A laptop, phone, or tablet selects one approved exit node for internet traffic.
Encrypted tailnet path
Traffic crosses the Tailscale connection until it reaches the chosen exit device.
Public internet
Websites see the exit node’s public IP and location instead of the client’s.
An exit node changes the default internet route
Tailscale exit node vs subnet router vs regular tailnet
These three routes solve different jobs. Match the route to the traffic you need instead of enabling every feature on the same machine.
| Route | Traffic sent through it | Public IP behavior | Best use |
|---|---|---|---|
| Regular tailnet connection | Traffic to another Tailscale device or service | The client keeps its normal public IP | Private SSH, remote desktop, NAS, and app access |
| Subnet router | Selected private LAN subnets behind another device | The client keeps its normal public IP for websites | Reaching printers, cameras, or servers that cannot install Tailscale |
| Exit node | General internet traffic through the selected device | Websites see the exit node’s public IP | Using a trusted egress point, stable address, or chosen server region |
How to set up a Tailscale exit node on Linux
Ubuntu Server, Debian, Raspberry Pi OS, and most Linux VPS deployments follow the same sequence: install, enable forwarding, advertise, approve, then select.
- 1
Install Tailscale on the host
Install Tailscale on the Linux host, sign it into the same tailnet as the client devices, and confirm it appears on the Machines page.
- 2
Enable Linux IP forwarding
Enable IPv4 and IPv6 forwarding so Linux can pass traffic between the Tailscale interface and the public network.
- 3
Advertise the exit node
Run sudo tailscale set --advertise-exit-node on the host. This publishes its ability to route internet traffic but does not select it on clients.
- 4
Approve the route in the Admin Console
In the Tailscale Admin Console, open Machines, find the host, choose Edit route settings, enable Use as exit node, and save.
- 5
Select the node on each client
Select the approved node on each client. On Linux, pass its 100.x Tailscale address to sudo tailscale set --exit-node=<exit-node-ip>.
echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf
sudo sysctl -p /etc/sysctl.d/99-tailscale.conf
sudo tailscale set --advertise-exit-node
# Run on a Linux client after admin approval
sudo tailscale set --exit-node=<exit-node-ip>Windows, macOS, iOS, Android, and tvOS can use exit nodes
How to choose and use an exit node
Run tailscale status to find the node’s 100.x address, select it on the client, and compare the public IP before and after. Choose the nearest useful region when latency matters.
Keep local LAN access
Add --exit-node-allow-lan-access=true when the client still needs its current printer, router, or local service.
Change exit location
Select a different approved node from the client. A new server region changes the egress point without rebuilding the tailnet.
Return to the normal route
Choose None in the app or run sudo tailscale set --exit-node= on Linux to stop using an exit node.
Why run a Tailscale exit node on a VPS?
A home computer is useful when the goal is specifically to exit through home. A VPS is the practical upgrade when the node should stay online, keep one public address, offer a chosen region, and avoid competing with the residential connection. The server becomes a small, independently managed internet gateway for approved tailnet devices.
Old setup pain
A home PC must stay awake
Sleep, reboots, power cuts, and a closed laptop end the route while you are away.
A small cloud server keeps the Linux exit node running independently around the clock.
Old setup pain
The route shares a residential uplink
Uploads, backups, games, and everyone else at home compete with traffic returning through the same connection.
A VPS supplies dedicated cloud bandwidth and a stable public egress address for the tailnet.
Old setup pain
One home gives one exit location
Every remote client must route back through that single city even when another region would be closer.
Deploy another small node in a useful region and let each device select the better exit.
Tailscale exit node VPS sizing and location
Exit-node performance is usually shaped more by network throughput and distance than memory. Start small, select a region near the clients or destination, then resize from measured CPU and transfer speed.
| Use | Practical starting size | Good fit |
|---|---|---|
| One or two light-use devices | 1 vCPU · 1 GB RAM | Browsing, admin access, and occasional travel use |
| Several active clients | 2 vCPU · 2 GB RAM | Concurrent browsing, calls, downloads, and background sync |
| Heavier or multi-region setup | 2–4 vCPU · 4 GB RAM | Higher throughput, more users, monitoring, or extra services |
Best VPS options for a Tailscale exit node
Choose Vultr first for a broadly located exit node with a straightforward growth path. Choose DMIT when Pacific-route placement is the main reason for the server. Both give the Linux access needed to install Tailscale, advertise the route, and manage the node directly.
Vultr
- Official networking guides document Tailscale and Headscale deployments
- Terraform, Ansible, and cloud-init examples support repeatable nodes
- Published hourly billing includes a monthly cap
- Public status history is organized by service and region
DMIT
- Cloud locations include Los Angeles, Hong Kong, and Tokyo
- Published infrastructure uses AMD EPYC processors and NVMe storage
- Los Angeles network capacity is listed at 3.8 Tbps across Tier-1 providers
- Snapshots and automated backups are available in the self-service platform
Tailscale exit node troubleshooting
Start with the exact point where the route stops: advertisement, approval, client selection, Linux forwarding, or the server’s outbound network.
Exit node is not showing
Run the advertise command on the host, then approve Use as exit node in the Admin Console. Advertising and approval are two separate steps.
Use as exit node is greyed out
Confirm the host is online, advertised, approved, and permitted to route to autogroup:internet when the tailnet uses a custom access policy.
Internet is blocked after connecting
Confirm Linux IP forwarding is active, then inspect the host firewall and outbound path. Clear the selection with sudo tailscale set --exit-node= while fixing the host.
Local devices disappear
Select the node with --exit-node-allow-lan-access=true when the client should keep direct access to printers, routers, or other devices on its current LAN.
The exit node feels slow
Choose a node closer to the client or destination and compare its CPU and network throughput. Every internet request now includes the route through that exit.
A phone loses battery as the host
Move the exit role to an always-on Linux device or VPS so the phone only acts as a client and does not forward traffic for other devices.
Tailscale exit node FAQ
Continue your Tailscale and server setup
Official Tailscale references
These official references cover exit-node behavior, platform setup, CLI flags, and direct or relayed Tailscale connections.