MultiPortal v1.1.3 – Several Issues Encountered with Proxmox VE 9.2.3

[Guillaume]

MultiPortal v1.1.3
Proxmox VE 9.2.3
Single Node

Hello,

I have been testing MultiPortal v1.1.3 with Proxmox VE 9.2.3 and I have encountered several issues that prevent normal usage.

1. Clone Function Failure

When I clone a VM from MultiPortal, the cloning process is actually performed successfully on the Proxmox side and the VM is created correctly.

However, the job status in MultiPortal ends with an error:

Error: Failed To Create VM from Template: Failed to clone Proxmox VM. Source VM data not found for VM ID: 110

Even though the VM exists and has been cloned successfully in Proxmox, MultiPortal reports the operation as failed.

2. Cloud-Init Requirement Cannot Be Met

MultiPortal requires templates to have Cloud-Init configured.

However, when creating a template from a VM that was originally created through MultiPortal, there does not appear to be a way to add or configure Cloud-Init before converting the VM into a template.

As a result, it is difficult or impossible to meet the Cloud-Init prerequisite when using VMs created directly from MultiPortal.

3. Network Interface Not Added from Template Configuration

Another issue concerns VM templates.

When creating a VM from a template in MultiPortal, I configure a network interface during the deployment process. However, the network card is never actually added to the resulting VM in Proxmox.

In addition, a post-clone task remains active indefinitely and never seems to complete.

Environment

• MultiPortal: v1.1.3
• Proxmox VE: 9.2.3

Has anyone experienced similar issues, or is there a known workaround for these problems?

Thank you.

[woody]

Hey @guillaume

Thanks for the report:

#1 (clone “Source VM data not found”): Yes, that error message is a bit misleading. From what you’re describing, the Proxmox-side clone has actually completed fine, and what’s failing is MultiPortal’s post-clone bookkeeping, where it tries to copy the template’s row into the local proxmox_vm_stats table to seed the new VM’s row. It looks like that lookup isn’t finding template vmid 110. To dig in a bit further, could you share:

• runtime/logs/vm-clone.log and runtime/logs/VirtualMachine.log around the failure time
• Was template 110 created in MultiPortal, or imported/converted directly in Proxmox? Was it ever migrated between nodes?

The easiest way to get these logs to me is to export them from MultiPortal. The process is documented here: https://docs.multiportal.io/reference/log-files/#multiportal-application-error-logs. That produces a zip; email it to support@multiportal.io and it’ll open a ticket, and I’ll review the logs from there.

#2 (Cloud-Init on self-created templates): Correct, at the moment MultiPortal doesn’t have a UI to attach a cloud-init disk to a VM before converting it to a template. Workaround for now is to add the cloud-init drive in Proxmox directly. I’ve raised this internally to discuss adding that functionality within MultiPortal.

#3 (network not added / post-clone task never completes): The network attach is done asynchronously by a queue processor (vm-post-task/process) that runs from MultiPortal’s cron dispatcher. If the host-level cron isn’t invoking php yii cron/index, the queue will never drain and the task stays “active”, which matches what you’re seeing. Could you check:

• Your host crontab has an entry like * * * * * cd /path/to/multiportal && php yii cron/index >/dev/null 2>&1
• In Cron Task Management (MultiPortal admin UI), vm-post-task/process is listed, enabled, and Last Run is updating
• Please run php yii migrate --interactive=0 so it applies any pending migrations without prompting. If anything errors out, send the output through to support@multiportal.io and I’ll take a look.
• As a quick test, run php yii vm-post-task/process manually. If the network gets attached and the lingering task closes, scheduling is the only thing missing.
• It’s also worth running ./yii cron/index manually once everything else is in place, just to confirm the dispatcher itself runs cleanly and to surface any errors that might be stopping it from progressing under cron.

[Guillaume]

Thank you for your response.

Regarding issue #1, I performed several tests using different types of source VMs:

• A VM imported directly into Proxmox and then converted into a template.
• A template created from within MultiPortal.
• A VM created directly from MultiPortal and then converted into a template.

In all cases, I get the same result. The VM is successfully cloned on the Proxmox side, but MultiPortal reports the following error:

Error: Failed To Create VM from Template: Failed to clone Proxmox VM. Source VM data not found for VM ID: 104

This seems to indicate that the issue is not related to how the template was created, since the behavior is identical across all tested scenarios.

Regarding issue #3, I checked my crontab and I currently have:

* * * * * cd /path/to/multiportal && php yii cron

I also ran:

php yii migrate --interactive=0

and received:

Your system is up-to-date.

So there are no pending migrations.

I will also check the Cron Task Management section and test running:

php yii vm-post-task/process

manually to see if the network interface gets attached and if the pending post-clone task completes.

I will send the requested logs as soon as possible for further investigation.

[Guillaume]

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.