You can now edit Proxmox LXC config web UI in Stashboard without ever opening the Proxmox VE console or dropping to an SSH shell. The Config tab on each LXC card turns a container’s parameters into real form fields, and two companion tabs put live diagnostics right beside them — a browser console and a streaming log view. This deep how-to covers exactly how to edit Proxmox LXC config web UI (V6.5 and V6.9), what the single Save really commits, and how the V6.6 console and the V6.12 Logs tab work — field by field, gate by gate.
New here? Start with the Stashboard self-hosted homelab dashboard overview, and read the manage Proxmox from a web dashboard pillar guide for the whole surface. If you have already set up Proxmox LXC update monitoring and learned to create a Proxmox LXC from the web UI, editing an existing container is the natural next step. 🧩
Prerequisites: an API token, plus SSH for the console
To edit Proxmox LXC config web UI you need only the connection you already use elsewhere on the Proxmox page: a node added by its host URL and a Proxmox API token of the form user@realm!tokenid=secret — the recommended credential. The token alone is enough to read and write container config — every scalar and structured edit on the Config tab goes through the Proxmox REST API.
Optional SSH credentials (host, username, private key) on the same connection unlock the browser console, which runs pct exec on the host. SSH is not required to edit config or to read logs — only the console depends on it. ⚠️ Treat that SSH key like a root key: it can exec into any container on the node.
Edit Proxmox LXC config web UI: the Config tab scalars
The Config tab is where you edit Proxmox LXC config web UI for the parameters you change most often. It exposes them as plain form fields:
- Hostname — the container’s name.
- Cores — the CPU core count.
- Memory and Swap — RAM and swap in MiB.
- Start at boot (
onboot) — whether the guest comes up with the node. - Description — the free-text note Proxmox shows on the guest.
- Tags — the coloured Proxmox guest tags.
Here is the important part: the form tracks what you actually changed. When you press the single Save, Stashboard sends only the keys you edited to the Proxmox API — never the whole config. Touch only memory, and only memory is written. That keeps the call minimal, avoids clobbering a value something else changed, and maps cleanly onto the pct set semantics Proxmox expects. One Save covers the whole tab — you do not save each field on its own.
Network interfaces and mount points: structured add, update, remove
Scalars are the easy half. The more powerful half of how you edit Proxmox LXC config web UI is the structured editors for network interfaces and mount points — the parts that are miserable to hand-edit as Proxmox’s packed net0=… and mp0=… strings.
Network interfaces. Each interface (net0, net1, …) is shown as a row you can add, update, or remove. Behind a row are the same fields Proxmox uses: the interface name (eth0), the bridge (vmbr0), an optional VLAN tag, the MAC, IPv4 as DHCP or a static CIDR with a gateway, the IPv6 equivalents, a rate limit, and a per-interface firewall toggle. Stashboard composes these back into the exact netN string Proxmox stores, so what you set is what the container gets.
Mount points. Likewise, each mount point (mp0, mp1, …) is a row you add, update, or remove: the volume or host path, the mount path inside the container, the size, and options. ⚠️ Mount-point and rootfs changes deserve the most care — a wrong bind path can hide or expose data — so review the row before you Save. As with the scalars, when you edit Proxmox LXC config web UI the single Save commits only the interfaces and mount points you actually changed.
The browser console: pct exec in xterm, token-safe (V6.6)
The Console tab is the first of the two live-diagnostics tabs that sit beside where you edit Proxmox LXC config web UI. Open it and Stashboard gives you a real interactive shell inside the container — an xterm.js terminal in the browser wired to a pct exec <vmid> -- … PTY that runs over your SSH connection to the host. No terminal app, no separate SSH client — you are root-shell-deep in the guest from the same page where you edited its config.
It is triple-gated, and every gate is OFF by default:
- A server-wide master switch — Settings → LXC console.
- A per-host opt-in — Allow console on the individual Proxmox connection.
- SSH configured on that connection — the console is the one feature that cannot run on the API token alone.
⚠️ Until all three are on, the Console tab simply isn’t offered — the capability does not exist.
Crucially, the SSH credential never reaches the browser. The terminal talks to a server-side relay over a WebSocket; Stashboard holds the SSH key, opens the pct exec PTY on the server, and streams only the raw terminal bytes to and from xterm.js. The browser is handed a short-lived session, not a secret — so opening a console never exposes your host credentials to the client. And like every other action, each console session is written to a console audit row.
The live Logs tab (V6.12)
The second diagnostics tab is Logs. Added in V6.12, it streams the container’s log output live into the browser — a tailing view you can watch without opening the console or starting an SSH session at all. It is the read-only companion to the console: when something looks off after you edit Proxmox LXC config web UI, the Logs tab is the fastest place to read the guest’s own output and confirm a service came back cleanly. Because it only reads, it has no mutating gate — if you can see the guest, you can read its logs.
How to verify each piece works
- Config scalars — the heart of how you edit Proxmox LXC config web UI: change one value (say memory), Save, then SSH to the host and run
pct config <vmid>. Only the key you edited should differ, confirming the changed-keys-only commit. - Network / mount points — add an interface or mount point, Save, and check the same
pct config <vmid>output for the newnetN/mpNline; remove it and confirm it disappears. - Console — with all three gates on, open the Console tab and run something like
hostnameorapt list --upgradable; you should get a live response. With any gate off, the tab should not appear at all. - Logs — open the Logs tab on a running container and watch new lines arrive as the service writes them.
Every config write and every console session also lands on the Audit page, so you have a who-changed-what-when trail to cross-check.
⚠️ Risks and gates worth knowing
- Config writes are real, immediately. A bad cores or memory value, or a malformed
netN, is rejected by Proxmox and surfaced verbatim — but a valid change applies at once. Some keys (memory, cores) take effect live; others need a container restart to take hold. - Mount points and rootfs are the dangerous fields. A wrong bind path or size can hide data or fill a disk. Review before Save, and snapshot first if the data matters.
- The console SSH key is powerful. It can
pct execinto every container on the node. Scope and protect it, and leave the LXC console master switch off until you need it. - Everything mutating is gated and audited. To edit Proxmox LXC config web UI, the config write is governed by the same per-host trust model as the rest of the Proxmox surface, and the console stacks its own triple gate on top.
Bottom line
Stashboard lets you edit Proxmox LXC config web UI end to end from a single card: change hostname, cores, memory, swap, onboot, description, and tags with one Save that commits only what you touched; add, update, or remove network interfaces and mount points through structured rows; drop into a token-safe pct exec console; and watch a live Logs stream — all without leaving the dashboard. For the complete picture of the Proxmox surface, read the manage Proxmox from a web dashboard pillar guide; for the disk-health side of the same containers, pair it with Scrutiny SMART monitoring on a Proxmox LXC. 🚀
Stashboard is open source — you can find the full source code on GitHub and pull the ready-to-run image directly from Docker Hub. Issues, PRs, and stars are always welcome. 🙌