ProxCenter v1.4.7 Release
Two authentication fixes, disaster recovery failback, and sturdier migrations
ProxCenter v1.4.7 is a security release. It fixes two authentication issues reported through private disclosure, adds revocable sessions, and completes the disaster recovery cycle with failback.
Upgrading is recommended for every installation.
🔒 Security
Dotted API paths no longer skip authentication
The middleware treated any path containing a dot as a static asset and answered before the session check. Proxmox node names accept dots and the guest routes carry the node name, so a cluster named with an FQDN exposed guest notes and task data to unauthenticated callers.
First-run setup is bounded
The setup endpoint now enforces a rate limit, accepts an optional PROXCENTER_SETUP_TOKEN, and decides that no user exists inside a serializable transaction, so two concurrent bootstraps cannot both create an administrator.
Sessions and API tokens
Sessions are tracked server side and can be revoked, from a management screen for your own and from the admin view for someone else's. New pxc_ read-only tokens cover aggregated public endpoints for dashboards and external monitoring.
🛟 Disaster Recovery
Failback
A plan that has failed over can now come home: a reverse incremental sync brings the source up to date, then an operator-driven cutover switches back, with per-VM rollback and re-protect.
Safer failovers
- Source fencing on a real failover, so the same guest never runs on both sides
- Boot screenshots captured during a test failover, so you see what a guest actually booted into
- Point-in-time recovery and configurable retention on replication plans
- The orchestrator survives the loss of its node and keeps the IP of a node that stops answering
📦 Migration
- vSphere snapshots are waited out instead of failing at 120 seconds, which blocked warm migrations of multi-terabyte guests
- Pre-migration check for HA affinity rules
- Warm migrations warn before falling back to CBT and show real progress during pre-zero and copy
- Windows guests boot from SATA, i440fx is sent as
pc, and custom CPU models are handled - Optional qcow2 conversion, and jobs orphaned by a restart now fail cleanly
✨ Also in this release
| Area | What's new |
|---|---|
| 🏢 Multi-tenant | Several vDCs per tenant, with a global vDC context |
| 👁️ RBAC | Tag and pool scoped users see their inventory again |
| 💾 Backups | vzdump archives listed in a guest's Backups tab |
| 📄 Reports | White label carried into the compliance PDF export |
| 🛡️ Compliance | CIS Controls v8.1 card in the Frameworks tab |
| 🔥 Firewall | Security groups on guests and rule log level exposed |
| 🤖 Assistant | Answers in the language of the interface |
Plus clearable numeric fields, snapshot rows that follow the Proxmox task, a tenant selector on the storage overview, a broadcastable maintenance banner, and seventeen dependency updates.
⬆️ Upgrading
docker compose pull && docker compose up -d
No migration step beyond the image pull. Three optional settings are new and unset by default: PROXCENTER_SETUP_TOKEN, SESSION_IDLE_TIMEOUT and SESSION_ABSOLUTE_TIMEOUT.
Thank you to everyone who reported issues and tested this release.