Upgrade to v1.4
ProxCenter v1.4.0 moves the application backend from SQLite to PostgreSQL. This is a breaking change for installations created with v1.3.x or earlier.
v1.4.0 does not ship an automatic SQLite-to-PostgreSQL data migration. Do not run a blind docker compose pull && docker compose up -d on an existing v1.3.x stack expecting the application to reuse the old SQLite database.
What Changes
| Area | Before v1.4 | v1.4 and later |
|---|---|---|
| Database | SQLite file inside the deployment volume | PostgreSQL 15+ |
| Startup | App opens the SQLite database directly | App connects to PostgreSQL and runs schema migrations |
| MSP features | Limited tenant metadata | Tenant, vDC, IPAM, PBS namespace, report and quota data stored in PostgreSQL |
| Upgrade path | In-place Docker image update | Planned cutover with backup and re-bootstrap |
Recommended Upgrade Strategy
For production systems, treat the upgrade as a controlled cutover:
- Freeze configuration changes in the current v1.3.x environment.
- Back up the existing Docker project directory and volumes.
- Export operational information you need to recreate in v1.4, such as users, connections, tenants, notification settings, report schedules and RBAC assignments.
- Deploy a fresh v1.4 stack with PostgreSQL.
- Create the first admin account and reconfigure platform settings.
- Reconnect Proxmox VE and Proxmox Backup Server instances.
- Recreate tenants, vDCs, quotas, backup bindings and users where applicable.
- Validate inventory, backups, reports, alerts, events and tenant visibility before opening the instance to users.
Keep the old v1.3.x stack stopped but available until the v1.4 instance has been validated.
Pre-Upgrade Checklist
- Confirm that you are currently running v1.3.x or earlier.
- Record the current ProxCenter version and Docker image tags.
- Back up the deployment directory,
.envfile and Docker volumes. - Export or document API token names used for Proxmox VE and PBS connections.
- Verify that Proxmox API tokens still exist and that their secrets are available.
- Record license information and Enterprise feature usage.
- List tenant assignments, custom roles, notification channels and report schedules.
- Schedule a maintenance window if users rely on ProxCenter for daily operations.
Deploying v1.4
Use the current installer from the ProxCenter website, or update your Docker Compose stack so that it includes:
- The ProxCenter frontend container.
- The ProxCenter orchestrator container.
- A PostgreSQL 15+ database.
- The WeasyPrint sidecar if you use scheduled PDF reports.
- Persistent Docker volumes for PostgreSQL and application data.
After startup, open the web interface and complete the bootstrap flow.
http://your-server-ip:3000
Post-Upgrade Validation
Validate the following areas before declaring the upgrade complete:
| Area | What to check |
|---|---|
| Login | First admin account can sign in and access Settings |
| Connections | PVE and PBS connections test successfully |
| Inventory | Clusters, nodes, VMs, containers, storage and pools are visible |
| Backups | PBS archives and PVE backup jobs are visible |
| Tenants | Tenant users see only their assigned resources |
| vDCs | Quotas, networks, IPAM reservations and PBS bindings work as expected |
| Reports | On-demand PDF generation works; scheduled reports require the WeasyPrint sidecar |
| Alerts | Thresholds and event rules reflect the expected edition and tenant scope |
| Audit | Administrative changes are recorded |
Rollback
If validation fails, stop the v1.4 stack and restart the old v1.3.x deployment from its backed-up directory and volumes. Do not point v1.3.x containers at the PostgreSQL database created for v1.4.
Investigate the issue on the v1.4 stack, adjust the deployment or configuration, then repeat validation.