Repository navigation
pvewarden 0.1.5
Clearer install, from the first production install:
- The root password of the server container is described as what it is: console and
pct enter
only. Debian refuses root passwords over SSH; the wizard now says so and points to SSH keys. - Reaching the server through a VPN: the wizard explains the two addresses (LAN for the guests, VPN
for the agents). A VPN address that is not up yet at the end of the install is the next step, not
a failure: the summary says what to do, and the server starts by itself within 10 s once the
address exists. New guide: docs/wireguard.md (also in Czech). pvewarden-setup renew-certswitches an install made with plain HTTP to HTTPS on the same address
(certificate signed by the Proxmox CA; tokens stay). With a VPN address, the wizard now defaults
to HTTPS too: some MCP clients (NanoClaw) refuse a remote server over plain HTTP.- Enrolling: VMs whose QEMU guest agent does not answer are no longer offered (and skipped with
--yes); the wizard lists them with the steps to add the agent, including the power cycle. - New
pvewarden-setup doctor [-v]: the server's self-check from the host, withoutrunuserand
full paths. "run as root" now sayssudo -i. - Automatic updates: the wizard says what on and off mean; doctor lists the guests where they are
on as one[INFO]line with how to turn them off, instead of a note on every guest. - Docs: checking the downloaded script is optional (pvewarden-setup checks what it downloads);
the upgrade steps no longer require it.