Guide
14 min readAug 06, 2026

Tailscale Proxmox Setup: Host, LXC or VM — Pick the Safe Path

Install Tailscale on Proxmox with the right isolation. Compare host, unprivileged LXC, and VM paths, then generate commands for remote UI or subnet access.

Quick answer

For Proxmox web UI access only, installing Tailscale on the host is the shortest path. For a Tailscale subnet router, use an unprivileged LXC or dedicated VM so routing stays isolated from the hypervisor. Do not expose port 8006 publicly; connect to the host's Tailscale IP or an approved private subnet route.

No public ports

Keep port 8006 off the internet

3 placements

Compare host, LXC, and VM

Ready commands

Generate a setup you can copy

Interactive setup planner

Tailscale Proxmox placement planner

Choose what you want to reach. The planner recommends the safer placement, builds commands, and highlights when your preferred location adds unnecessary risk.

Where were you planning to run Tailscale?
What needs remote access?

Used only when the plan advertises a subnet route.

Recommendation
Safer placement differs

Use an unprivileged LXC subnet router

The routing role stays outside the hypervisor while one approved route can reach Proxmox and other LAN services.

Shell
curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up
printf 'net.ipv4.ip_forward = 1\n' | sudo tee /etc/sysctl.d/99-tailscale.conf
sudo sysctl -p /etc/sysctl.d/99-tailscale.conf
sudo tailscale set --advertise-routes=192.168.1.0/24

Then: Approve the advertised route in the Tailscale admin console, then test one LAN address.

Architecture decision

Proxmox host vs LXC vs VM for Tailscale

Google’s results surface the same unresolved tradeoff repeatedly: convenience on the host versus isolation in a guest. The safest default is the narrowest placement that meets the access goal.

PlacementIsolationWhat it reachesBest forTradeoff
Proxmox hostLowestHost UI and host servicesThe shortest path to :8006Adds software to the hypervisor
Unprivileged LXCGoodContainer plus approved LAN routesSubnet router and shared accessNeeds /dev/net/tun and forwarding
Dedicated VMStrongestVM plus approved LAN routesStrict separation and easy rollbackUses more RAM and storage
Install paths

How to install Tailscale on Proxmox

Use the host only for host-level access. For a Proxmox Tailscale subnet router, put routing in an unprivileged LXC or dedicated VM so the hypervisor stays focused on virtualization.

Path A: Proxmox host

Fastest route to the web UI and host shell.

  1. 1. Install: run the official Linux installer from the Proxmox shell.
  2. 2. Authenticate: run tailscale up and open its login URL.
  3. 3. Connect: visit the node’s 100.x address on port 8006.
Shell
curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up
tailscale ip -4

Path B: unprivileged LXC

Better isolation for subnet routing and shared access.

  1. 1. Create: use a small Debian LXC with a reserved LAN address.
  2. 2. Expose TUN: confirm /dev/net/tun exists inside the stopped-then-restarted container.
  3. 3. Advertise: enable forwarding, advertise the LAN CIDR, and approve it.
Shell
curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up
sudo tailscale set --advertise-routes=192.168.1.0/24

Verify the Tailscale Proxmox connection

Test from a device outside the Proxmox LAN. A successful local test alone cannot prove remote routing works.

1

Node is online in tailscale status

2

tailscale ping returns a peer path

3

https://100.x.y.z:8006 loads

4

One approved LAN service responds

Tailscale Proxmox troubleshooting

Start with the layer that failed: daemon, TUN device, route approval, firewall, or name resolution.

Questions people ask

Tailscale Proxmox FAQ

Continue learning

Related remote-access guides

Tailscale without port forwarding

Choose private access, Serve, or Funnel without exposing the wrong service.

Build a Tailscale exit node

Route internet traffic through an approved home server or VPS.

Remote access without open ports

Compare safer ways to reach a private network from outside.

Check whether you are behind CGNAT

Confirm why inbound router rules cannot reach your network.

Official references

Confirm current platform details before changing a production hypervisor.

Share this article