Compute & VMs

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

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]

Hey MikeD, thanks for the post! We’re aware of this bug and we’re already investigating it.

Hey @southwalesowl, Adding the 127.0.0.1 multiportal.calligo.cloud hosts entry just allows MultiPortal and the console server to talk to each other locally, however, the error you now have ECONNREFUSED 127.0.0.1:443 means the console server cannot reach MultiPortal locally on port 443. That loopback shortcut only works when MultiPortal is handling its own traffic directly on the server. Can you please confirm: MultiPortal was installed using the automated script? Is an SSL configured on the box, or are you using a Load Balancer for MultiPortal? Confirm the system is reporting on port 443 sudo ss -ltnp | grep ':443' You should see something like ⎿ LISTEN 0 4096 *:443 *:* users:(("caddy",pid=4140634,fd=7)) Can you also comment out that hosts entry you added to your MultiPortal server, restart the console server, and try connecting again? Let me know if the old error comes back after you regenerated the new API key. Matt

I performed an additional test by running: php yii vm-post-task/process The command returns: Unable to get status for Proxmox task UPID:iaas-pve-s1-002:001E1CD9:01149D63:6A2D92BF:qmclone:103:multiportal@pve!ertyfghj: Proxmox task UPID:iaas-pve-s1-002:001E1CD9:01149D63:6A2D92BF:qmclone:103:multiportal@pve!ertyfghj: is still running, skipping... However, the clone operation has already completed successfully in Proxmox and the VM exists and is fully created. It appears that MultiPortal is unable to correctly determine the final status of the Proxmox clone task and continues to consider the UPID as running. This may also explain why the post-clone task never completes. Regarding the network issue, I can confirm that the network adapter is requested during deployment from the template, but it is never added to the VM. The network interface is missing not only in MultiPortal, but also in the VM configuration directly in Proxmox. As a result, the deployed VM is created without any network device attached. Could there be an issue with task status polling or UPID tracking in MultiPortal when used with Proxmox VE 9.2.3? One additional point that may be relevant: this is a brand new MultiPortal installation deployed in an offline environment behind a proxy. The documentation is not very explicit regarding offline deployments and proxy requirements, so I am not completely sure whether my installation is fully operational or if there are additional configuration steps required for this type of environment. Could you advise on how I can verify that the installation is healthy and fully functional? Are there any specific services, connectivity checks, background workers, queue processors, or diagnostic commands that should be validated after an offline installation behind a proxy? I would like to rule out any installation or connectivity issues before investigating the cloning and post-clone task problems further.

@heky said: But now in 1.1.3 there is another error Error: Validation failed: {“ciuser”:[“Username is required when any cloud-init field is set.”]} So probably you need to address this. Creation VM from template is not possible.[image: 1779944432275-screenshot-2026-05-28-at-07.00.08-resized.png] @heky Can you please see my message I incorrectly directed to Twallace-armor.