Sorry, it took a bit longer to check. I redeployed a MP instance and this time bootstrap worked just fine. But i can assure last time i tried, it gt blocked by cloudflare.

OK @kth can I get you to raise a support ticket and submit your support bundle with it? We’ll check this out

Environment MultiPortal Version: 1.2.1 Proxmox VE Version: 9.2.6 Deployment Type: HA Cluster Description When we create a virtual datacenter via the API, the “reseller” and “tenant” variables in the Proxmox resource pool do not appear to be populated. However, when a datacenter is created via the GUI, the reseller and tenant names do appear there. Datacenter Name (GUI): Reseller_XYZ.Kunde_ABC.vdc.9672ec9c-4199-43b0-b258-f2ce4135673c [image: 1789050383346-c9b07b78-ffda-4468-94d9-79dc8577eca3-image.jpeg] Datacenter Name (API): reseller.tenant.vdc.bbfa10c2-7c52-4d6e-986f-d6c0c156fd80 [image: 1789050397348-670ac32b-19c1-4eed-8c5d-9bf26def9e41-image.jpeg] I also checked the swagger documentation but couldn’t find a way to change this behavior. Expected Behavior The ressource pool on Promox includes the reseller and tenant names also when created via api. Actual Behavior The ressource pool on Proxmox only includes the id of the virtual datacenter, and doesn’t include the showname of the reseller and tenant when created via api.

Ooo point one is a good bug spot, thanks! I’ll get that raised. Point two is a great suggestion, I’ll add that in as well. Thanks!

Hi, The main Community and Multiportal Support headings don;t link to their sub forums like the others. Mike

Environment MultiPortal Version: 1.2.1 Proxmox VE Version: 9.2.6 Deployment Type: HA Cluster Description We have only 1 specific CPU Model enabled at datacenter level. While we add new nodes to our cluster, then the new host have enabled 71 CPU Models on the database. On the WebUI there are likely random things enabled / disabled while we flip through the sites. Steps to Reproduce (if applicable) Disable all CPU Models and enable some / one CPU Model(s). Add new nodes to the cluster. Some CPU Models you previously disabled becomes randomly enabled. Expected Behavior New nodes in the cluster get the CPU Models from the existing Nodes. Actual Behavior New nodes become 71 default enabled CPU Models

Interesting suggestion, are you able to DM me the name of the ITSM solution?

Hey @gavin.beukes sadly no, we don’t have a definitive answer yet. I’ve been working on re-tooling our test suites and labs to include DRBD storage types as we dont have that currently (which explains why you’re hitting this bug).

Environment MultiPortal Version: 1.2.1 Proxmox VE Version: 9.2.4 Deployment Type: HA Cluster Browser (if UI issue): Firefox & Chrome Description I have created a new Tenant Role. All available rights is on. Assigned user is not able to create new VM in the tenants VDC. Error message in UI when selcting “New Virtual Machine”: Error. Error loading content. (“From Template” seems to be ok.) If I switch the user to “Tenant Administrator (System Role)”, everything is ok. Steps to Reproduce Create a new Tenant Role with all rights Assign the new role to a tenant user Log on with the tenant user and try to create a new VM Expected Behavior UI steps for New VM should appear. Actual Behavior Error. Error loading content. Logs/Screenshots [Attach relevant logs or screenshots]

Thanks, Stellios! I’m glad you like the idea. I look forward to hearing from you about it.

Hey Anders We’re aware of this and it’s being addressed in preparation for a patch release soon :) Stay tuned

Environment MultiPortal Version: 1.2.1 Proxmox VE Version: 9.2.11 Deployment Type: [Single Node / HA Cluster] HAcluster Browser (if UI issue): Description Hi team, I recently added a second node to my cluster, but I’m running into an issue regarding how virtual machines are provisioned. Whenever I create a new VM, it is always automatically deployed on Node 1, and never on Node 2. Could you please explain how VM placement or scheduling works once a cluster is set up? Specifically: Is there a way to manually target/steer a new VM creation to Node 2? Does multiportal handle automatic load balancing or resource-based placement across cluster nodes, or do I need to configure something specific? Thanks for your help! Best regards,[image: 1787244288635-capture-d-x27-%C3%A9cran-2026-08-20-184403.png]

Hi, I have noticed that in the latest version of MP you cant use the tenant search field in the add External Network wizard (Accessibility tab). (Unable write anything in the search field) The same goes for when you try to update an External Network. [image: 1787084411077-d199c2e5-2df4-410f-a606-e3fb0aa9144c-image.jpeg] Cheers!

Environment MultiPortal Version: v1.2.1 Proxmox VE Version: 9.1.1 Deployment Type: Single Node Description There is no documented way (in the Swagger API or somewhere else) to obtain the Guest Agent Information like the current IP Adress of a VM. I have found a Workaround by analysing the GET Requests my Browser does but this does not seem like a viable and futureproof solution. I have also found out that there is no way to create/list/revert/delete Snapshots of a VM via the API. I have done the same thing with the workaround via the get requests (even tho its a little bit harder to do) but its also no futureproof solution. It would be good to have api endpints for this (or they already exist and I havent found them yet), especially for deployment automations and data retrieval. Expected Behavior API Endpoints for Snapshot Management and Guest Agent Information Actual Behavior No Documented API endpoints in the Swagger API Documentation or somewhere else. No good way to implement it other than using the endpoints the browser uses and reverse enginnering those. Thank you in advance for the Help! Kind Regards, Fabio

Excellent suggestion @miked I’ll get this added to our backlog for sure.

Hey @Stell, thanks a lot for the info! I think this is all what I need to know for now - we will work with that and we’ll keep our fingers crossed that everything goes according to plan.

@Bolder You are correct, manual update states incorrect details that are miss leading. I’ve updated the docs and they should be published shortly to now properly reflect the manual update and also the offline update process. For those behind Proxy, you can follow the https://docs.multiportal.io/kb/article/0000050/. Just a heads up, at this stage if you have used the offline-update, there is no method currently to update the installation via the automatic process. Woody

MultiPortal has published security advisory MPSA-2026-001, a stored cross-site scripting issue in user and resource name fields. Severity: High (CVSS v3.1 base 8.7) Affected: MultiPortal Core 1.1.2, 1.1.3, and 1.2.0 Fixed in: 1.2.1 If you run an affected version, upgrade to 1.2.1 at your next maintenance window. The fix needs no data cleanup: existing names are made safe when they are displayed. Read the full advisory, including impact, remediation, and workaround: MPSA-2026-001 on docs.multiportal.io The fix ships in the 1.2.1 release. To report a vulnerability privately, see Reporting security issues.

Environment MultiPortal Version: 1,2.0 Proxmox VE Version: 9.2 Deployment Type: HA Cluster] Browser (if UI issue): Edge Description When creating a new user and assigning a role at creation, the role is not applied. The user is created successfully with no error shown, but the role field is blank in the users list. The failure only surfaces later when the account is used. Editing the same user afterwards and assigning the role works correctly. This may share a root cause with the existing thread “Suspected Bug: User Permissions Not Updated After Role Changes” — that one describes create working and later role changes not propagating; this is the inverse on the create path. Steps to Reproduce (if applicable) Create a new user and select the Service Provider Administrator role. Save. User is created, no error displayed. Users list shows the role field blank. Impersonate the user - Forbidden (#403). Edit the same user, assign Service Provider Administrator, save. Role now applies correctly and impersonation works Expected Behavior The role selected at creation is persisted and applied to the user. If it cannot be applied, an error is surfaced at creation rather than the user being created in a broken state. Actual Behavior The role is silently dropped. The user is created without permissions and no error is shown. The only signal is a 403 at point of use. Logs/Screenshots [[image: 1784206469866-39a43383-7712-4277-a140-b8caa926472d-image.jpeg] ]

Thanks for letting us know @guillaume , we’ll take a look at this for sure