🚧 In development — ProxDR is coming soon. You're viewing an early preview.

ProxDR
📚 Browse docs

CLI basics

The web UI covers day-to-day work, but the proxdr binary is also a full CLI — handy for headless setup, automation, and recovery. Run proxdr help for the full list.

Running the daemon

proxdr serve [--listen ADDR]

serve runs the daemon and the web UI together (the single-binary model). Common flags:

FlagDefaultPurpose
--listen:8443Web UI / API address (HTTPS). The installer binds :443 in production.
--peer-listen:8444Peer-link (mTLS) address.
--peer-advertise(auto)host:port peers use to reach this instance. Defaults to the detected LAN IP + the peer-listen port.
--web-advertise(derived)This site’s web-console base URL, shared with peers.
--tlstrueServe HTTPS with a self-signed cert. Use --tls=false behind a TLS-terminating proxy.
--tls-cert / --tls-keySupply your own certificate (e.g. your PKI or Let’s Encrypt).

Global: the data directory

--data-dir PATH     # env PROXDR_DATA_DIR; default ~/.proxdr

All ProxDR state — the controller database and keys — lives here. The systemd service installed by install.sh uses /var/lib/proxdr. Point every command at the same data dir.

Version

proxdr version

See CLI tasks for the quality-of-life commands: resetting the admin password, backup/restore, licensing, and managing remotes and pairs from the shell.