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.