Heck yes, love this @guillaume . We’re in the early planning stages for tags, providing every level (provider, reseller, tenant) to tag all objects in their respective tiers. I obviously can’t give any indicative times but just know we are totally on board with tags!

MultiPortal Community Guidelines

Welcome to the MultiPortal Community - a space for service providers, homelabbers, IT pros, and infrastructure folks to connect, share knowledge, and help each other get the most out of MultiPortal.

These guidelines keep things running smoothly. They’re pretty common sense, but worth spelling out.

---

The Short Version

Be helpful. We’re all here to solve problems and learn from each other.

Be decent. Treat people the way you’d want to be treated.

Stay on topic. This is a place for MultiPortal and infrastructure talk. If you want to talk about something random, keep it to the General Discussions forum.

---

The Details

Keep It Respectful

• Everyone’s welcome here, whether you’re in a massive telco or just getting started in your MSP.
• Disagree with ideas, not people. Healthy debate is fine - being a jerk isn’t.
• No harassment, discrimination, or personal attacks. Zero tolerance.
• Don’t be dismissive of questions that seem basic to you. We all started somewhere.

Keep It Useful

Asking for help?

• Search first - there’s a good chance someone’s already solved your problem.
• Use the templates in each forum - they exist to help you get better answers faster.
• Include the details: versions, error messages, what you’ve already tried.
• Post in the right category.

Helping out?

• Be patient, especially with newcomers.
• Give practical advice, not just “RTFM” or a link with no context.
• If you’re not sure about something, say so. Bad advice is worse than no advice.

Keep It Clean

• Don’t share passwords, API keys, or other secrets - even accidentally in logs or screenshots.
• Redact customer info and IP addresses before posting.
• Found a security issue? Email security@multiportal.io - don’t post it publicly.

Keep It Legal

• No piracy, license hacks, or anything that circumvents licensing.
• Respect copyright. Quote and attribute when appropriate.

Keep It On Topic

• Stick to MultiPortal, Proxmox, virtualization, and related infrastructure topics.
• General tech chat goes in Community → General Discussion.
• Save the politics and hot takes for somewhere else.

---

Forum-Specific Notes

Support Forums

• One problem per post. Don’t bundle unrelated issues.
• Mark your topic as solved when you get an answer - it helps others find solutions.
• Don’t bump repeatedly. Add new info if you have it, otherwise be patient.
• This is peer-to-peer support. For guaranteed response times, contact MultiPortal Support directly.

Feedback & Ideas

• Check if someone’s already requested your feature - add your voice to existing threads instead of duplicating. Use the topic voting feature.
• Focus on the problem you’re trying to solve, not just the solution you want.
• Not every request will be built. That’s just how it goes.

Beta Programs

• Beta content is confidential. Don’t share builds, screenshots, or unreleased features outside the beta forums.
• Give honest feedback - that’s why you’re here.
• Don’t run beta software in production. Seriously.

Partner Zone

• Partner info stays in the Partner Zone.
• Follow your Partner Agreement.

---

What Happens If Someone Breaks the Rules

We’d rather not police things, but when needed:

1. Heads up — Most issues get resolved with a quick note.
2. Warning — Repeated issues may get a formal warning.
3. Timeout — Continued problems can lead to a temporary suspension.
4. Ban — Serious or persistent violations mean permanent removal.

We aim to be fair and consistent. The moderators have final say.

---

Getting Help

Community questions: Post in the right forum.

Official support: For production issues or guaranteed response, contact MultiPortal Support.

Report a problem: Use the Report button or message a moderator.

Questions about these guidelines: Post in General Discussion or ask a mod.

---

Thanks for Being Here

This community works because people like you show up, share what you know, and help each other out. We’re glad you’re part of it.

~ The MultiPortal Team

---

Last updated: May 2026

MultiPortal 1.1.3 Release Notes

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

Absolutely, 100% agree with you! Which is why we’re performing a ground-up rewrite of our authentication and authorisation system which will deliver excellent granularity and control over per-tier API endpoints. The current target is this year :)

Hi everyone,

MultiPortal 1.2.0 is now live, and it is one of the biggest releases we have shipped. It brings finer control over storage and virtual disk performance, support for importing QinQ networks straight from Proxmox, full white-label branding across your whole channel, and self-service file-level restore for tenants, on top of a wide band of security, reliability, and usability work.

Here is the short version. Three big features lead the release: per-disk storage tuning, QinQ network import, and white-label branding. Around them sit dozens of smaller improvements, a stack of bug fixes, and a change Community edition users have been asking for. If you are upgrading, take a database backup first; everything else runs as part of the standard upgrade.

What’s new

Storage policy and virtual disk properties

You can now tune the disk-level settings that matter most for performance and compatibility, directly from your storage policies and per virtual disk. That covers disk cache mode, IO threads, AIO mode, discard, SSD emulation, and the recommended SCSI controller. MultiPortal applies these settings consistently when virtual machines and disks are created, and keeps them in place when disks are migrated between different Proxmox storage types.

The platform now tracks the SCSI controller and disk bus for each VM and disk, and validates your choices in the interface before you submit them, so you stop running into avoidable errors after the fact. When a storage policy does not suit a particular disk or controller, you get a clear warning, and you can dismiss the ones you have consciously chosen to accept.

QinQ network import

MultiPortal can now import QinQ (802.1ad) zones and VNets that already exist in your Proxmox SDN, bringing double-tagged, carrier-grade networks under management. A guided wizard discovers your QinQ zones, validates them, and assigns them to a reseller or a tenant, who then just sees a standard external network with none of the QinQ machinery underneath.

We wrote this one up in full, including the three-step import wizard and what it means for each tier. For the complete walkthrough, see QinQ zone import.

White-label branding

Make the portal your own, at every level of your channel. Service providers, resellers, and tenants can each set their own colours, font, logo, favicon, and login page, with every parent deciding how much freedom the level below it gets. Resellers and tenants can also serve the portal from their own custom domain, secured with an SSL certificate they upload or one issued automatically.

Branding cascades down the channel, too: a tenant inherits from its reseller and a reseller from you, and each parent decides whether the level below can override.

File-level restore

Tenants can now restore individual files from their backups themselves, using Proxmox’s file-level restore. There is no longer any need to restore a whole machine just to recover a single file.

Proxmox VE 9.2 support

MultiPortal 1.2.0 is tested against Proxmox VE 9.2. We have not built on any of the new 9.2 capabilities yet, but we have run our integration against the 9.2 APIs and confirmed that nothing you rely on today is lost, so you can move your hosts to 9.2 and keep managing them through MultiPortal exactly as before.

Security and access

This release tightens isolation and login handling across the board:

• Stronger tenant data isolation. Resources now stay correctly scoped to the tenant they belong to, closing paths where information could be seen outside its intended scope.
• Template sharing scoped correctly. Sharing a converted VM template now applies only to the intended scope, rather than being exposed more widely within a datacentre.
• More reliable single sign-on. SP-initiated SAML login has been hardened, including correct role assignment for newly provisioned users.
• Service Provider login isolation. Service Provider administration can now be restricted to its own dedicated login URL.
• Single session per user. You can now enforce a single active session per user.

Reliability and performance

• Faster usage synchronisation. Usage sync is now quicker and more reliable on larger environments, so usage data keeps pace with your reporting intervals.
• Leaner reporting. Reports take fewer resources to generate, and pay-as-you-go usage history is now kept after a virtual machine is deleted, so past usage stays available for billing and review.
• Accurate storage usage. Storage now totals correctly on VDC summaries, multiple storage policies are no longer added together by mistake, and total ISO usage is reported accurately. A VDC storage policy can be removed after a disk migration between Proxmox storages, and VDC deletion no longer stalls part-way through.

Also in 1.2.0

• Community edition limits removed. The caps on the number of resellers, tenants, and VDCs are gone from the Community edition. The 4-socket and feature restrictions stay.
• Japanese language support. Japanese joins the list of supported portal languages.
• Interface refinements. A range of interface and dark-mode improvements across the portal.

Upgrading

1.2.0 includes automatic database migrations that run as part of the standard upgrade. Please back up your database before you upgrade. We also recommend reading the documentation for anything new to your environment, particularly the storage disk properties and QinQ import, before you roll them out in production. Step-by-step instructions are in the upgrade guide, and the full notes will be in the 1.2.0 release notes: [TODO: release notes link once published].

Thanks, and what’s next

Thank you to everyone who told us what they needed in this release. A lot of 1.2.0, QinQ import and white-label branding especially, came straight from operators telling us how they run and sell. If you want to see where things are heading next, take a look at our roadmap for 1.2, 1.3 and 1.4.

If you have already upgraded, let us know how it went. Questions, bug reports, and feature requests are all welcome in the usual categories!

Hey @r.balboni

I’ve got this on the roadmap for 1.3.0. I’m literally reviewing roadmap items and timings (along with specifications) now, and it’ll definitely be in :)

Thanks

Hey @peconi ! Yes, branding supports custom login pages for each tier. login page is derived from the custom domain if one is set.

I’ve also just had confirmation from dev’s that we’ll be supporting PVE 9.2 on this release! So I’ll go through and update our release notes and announcements everywhere to reflect that.

Totally agree - this is something I’ll be working on