HI
The offline version isn’t available?
Best regards
Guillaume
Posts
-
[RELEASE] MultiPortal 1.2.1 is now available -
Suspected Bug: User Permissions Not Updated After Role ChangesHi
Environment- MultiPortal Version: 1.2.0
- Proxmox VE Version: 9.2.3
- Deployment Type: [Single Node ]
Description
We have identified what appears to be an issue with user role and permission management in MultiPortal.
When a role is created and assigned to a user, the user receives the expected permissions. However, if the role is later modified (permissions added or removed), the user’s effective permissions do not appear to change.
Additionally, even when assigning a different role to the same user, the user seems to retain the permissions that were initially granted, rather than inheriting the permissions of the newly assigned role.
Sincelery
-
**Feature Request: Proxy Support**Hi
Currently, the manual installation process requires direct internet access, which prevents deployments in environments where outbound connections must go through a proxy. This is a significant limitation for organizations with strict security policies.We would also like the license validation/check to be able to use the configured proxy instead of requiring direct internet access.
Providing full proxy support for the installation process and all external communications, including license verification, would greatly simplify deployments in secured and restricted environments.
sincelery
-
Feature Request: Support for VM Tags and Labels in MultiPortalHi
We would like to request the addition of tags for virtual machines in MultiPortal.
The ability for VM users to add and manage tags on their own virtual machines would make it much easier to organize, identify, and filter resources.
This feature would improve day-to-day VM management and help users better categorize their workloads according to their own needs.
sincelery
-
**Feature Request: Allow QCOW2 Disk Format for UEFI Boot Disk in MultiPortal**We would like to request an enhancement to MultiPortal regarding VM provisioning.
Currently, when a VM is created with UEFI boot, the boot disk is automatically created in RAW format. This causes an issue when the storage backend is an LVM LUN, as RAW disks do not support snapshots in this configuration.
Requested enhancement:
Please add an option to specify the disk format (for example, QCOW2) for the UEFI boot disk during VM creation.Benefits:
- Enable snapshot support for VMs stored on LVM-backed storage.
- Provide greater flexibility in storage configuration.
- Allow administrators to choose the most appropriate disk format based on their storage backend and operational requirements.
Current behavior:
- UEFI boot disk is always created in RAW format.
- Snapshot creation is not possible when the VM is stored on an LVM LUN.
Expected behavior:
- Allow administrators to select the boot disk format (RAW or QCOW2) when provisioning a UEFI VM.
- Ensure QCOW2 can be used as the boot disk format to support snapshots where applicable.
-
MultiPortal v1.1.3 – Several Issues Encountered with Proxmox VE 9.2.3I performed an additional test by running:
php yii vm-post-task/processThe 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.
-
MultiPortal v1.1.3 – Several Issues Encountered with Proxmox VE 9.2.3Thank 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: 104This 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 cronI also ran:
php yii migrate --interactive=0and 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/processmanually 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.
-
MultiPortal v1.1.3 – Several Issues Encountered with Proxmox VE 9.2.3MultiPortal v1.1.3
Proxmox VE 9.2.3
Single NodeHello,
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: 110Even 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.