Consoles
Proxploy gives you console access from the page a target already belongs to: a text terminal for containers and nodes, and a graphical console for VMs.
CT terminal and VM console
Section titled “CT terminal and VM console”Opening a console mints a single-use ticket bound to that one target, good for one connection, short-lived, and worthless to anyone who intercepts it after use. The browser connects over WebSocket using only that ticket; there’s no cookie or session on the console connection itself, because the ticket already proves you’re allowed to be there. If the connection drops, closing the console and reopening it mints a fresh ticket rather than trying to resume the old one.
CT and node consoles are a real text terminal talking Proxmox’s own console protocol underneath. VM consoles are a full graphical console (noVNC), useful for guests without SSH configured or a booted-but-unreachable network stack.
Node shell needs its own opt-in
Section titled “Node shell needs its own opt-in”A node shell is effectively a root shell on the Proxmox host, broader than anything else on this page, so it stays off by default. It only becomes available for a host that has the node-shell option turned on for it specifically, in addition to the console permission itself. Turning it on is a separate action from adding the host or authorizing SSH, precisely because for this one console type, “opening a shell” and “having root on the node” are the same thing.