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
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.
Used only when the plan advertises a subnet route.
Use an unprivileged LXC subnet router
The routing role stays outside the hypervisor while one approved route can reach Proxmox and other LAN services.
Review your Proxmox host choice
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/24Then: Approve the advertised route in the Tailscale admin console, then test one LAN address.
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.
| Placement | Isolation | What it reaches | Best for | Tradeoff |
|---|---|---|---|---|
| Proxmox host | Lowest | Host UI and host services | The shortest path to :8006 | Adds software to the hypervisor |
| Unprivileged LXC | Good | Container plus approved LAN routes | Subnet router and shared access | Needs /dev/net/tun and forwarding |
| Dedicated VM | Strongest | VM plus approved LAN routes | Strict separation and easy rollback | Uses more RAM and storage |
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. Install: run the official Linux installer from the Proxmox shell.
- 2. Authenticate: run tailscale up and open its login URL.
- 3. Connect: visit the node’s 100.x address on port 8006.
curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up
tailscale ip -4Path B: unprivileged LXC
Better isolation for subnet routing and shared access.
- 1. Create: use a small Debian LXC with a reserved LAN address.
- 2. Expose TUN: confirm /dev/net/tun exists inside the stopped-then-restarted container.
- 3. Advertise: enable forwarding, advertise the LAN CIDR, and approve it.
curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up
sudo tailscale set --advertise-routes=192.168.1.0/24Approve routes; do not expose the Proxmox web port
Verify the Tailscale Proxmox connection
Test from a device outside the Proxmox LAN. A successful local test alone cannot prove remote routing works.
Node is online in tailscale status
tailscale ping returns a peer path
https://100.x.y.z:8006 loads
One approved LAN service responds
Tailscale Proxmox troubleshooting
Start with the layer that failed: daemon, TUN device, route approval, firewall, or name resolution.
Tailscale Proxmox FAQ
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.