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 :)

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

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