Skip to content

Networking

What your controllers manage often lives in your network: a Proxmox host, a database, an internal API. A tunnel lets them reach it: your side connects out to ctrlplane, so nothing is opened inbound, and it works behind NAT. Without one, controllers reach the public internet only.

Connector Tailscale or Headscale
You run One Docker container on a machine in your network Nothing new, if you already use a tailnet
It reaches Everything that machine can reach What your subnet routers advertise

Turn one on under Network in the site.

Run the command the site shows on a machine in your network. It contains your tunnel’s key: treat it like a password.

Create a reusable, ephemeral auth key and paste it in Network (for Headscale, also its URL). The tunnel joins your tailnet as ctrlplane-<control plane>; limit it with ACLs.

Controllers get HTTPS_PROXY and HTTP_PROXY pointing at the tunnel. Most HTTP clients honour them, and names resolve on your side, so https://proxmox.home.lan:8006 works.

Database drivers, SSH and some SDKs ignore HTTPS_PROXY. Add a forward as name=host:port:

postgres=db.home.lan:5432

Controllers then connect to postgres:5432, with no proxy settings.

Changes restart your controllers to pick them up. Turn off removes the tunnel.