Release Version: 1.1.3
Release Date: May 26, 2026

MultiPortal 1.1.3 is a patch release that resolves several issues identified after the 1.1.2 release. We recommend upgrading at the next available maintenance window, particularly for environments using cloud-init VM templates, the REST API for VM provisioning, or PAYG reporting.

Bug Fixes

• VM creation from cloud-init templates restored. Fixed an issue introduced in 1.1.2 that prevented VMs from being deployed from templates when cloud-init was used, both with and without an SSH key supplied. Cloud-init template deployments now work as expected on both Proxmox 8 and Proxmox 9.
• REST API network attachment fixed. The POST /api/v1/virtual-machine/{id}/network endpoint no longer returns an HTTP 500 error when attaching a network adapter. Inline network configuration passed during VM creation is now applied correctly.
• Reseller access to console. Reseller Users can access the console without receiving a 403 Forbidden error.
• Operator safety control for the backup auto-disable cron. Added an optional environment-level kill switch that lets operations teams temporarily place the VDC backup auto-disable cron into a report-only mode, where it continues to detect and log issues but does not modify backup states. This provides a fast mitigation path in the event of transient or inaccurate capacity readings.
• PAYG storage usage reporting accuracy. PAYG reports now correctly sum the capacity of all disks attached to a VM. Previously, only the largest disk was included in the report total, which understated usage for multi-disk VMs.
• Storage policy usage accuracy via API. The VDC usage API now reports the correct current usage for storage policies after disks have been deleted or moved between policies. API and GUI values are now consistent.
• VM Migration while powered on Virtual Machine migration tool has been fixed to work with powered on machines
• Proxy fix for release checks: the updater now correctly handles environments where a proxy is configured for internet access.

Upgrade Notes

• This patch release includes a database migration. Please take a backup of your database prior to upgrading; the migration will run as part of the standard upgrade procedure.
• No breaking API changes.
• Default behaviour for the backup auto-disable cron is unchanged. The new operator safety control is opt-in.
• We recommend regenerating storage usage aggregates after upgrade to clear any pre-existing stale values from the storage usage API.

For assistance with upgrading, please post in the forums