Hey @danielbfusionred we’re actually adding something like this for storage changes in the next release. Feedback noted: we’ll look at adding pending reboots for other changes.
Global Moderators
Forum wide moderators
Posts
-
Status Indication for Hardware Change Reboot -
GUI slow when QEMU agent not runningHey MikeD, thanks for the post! We’re aware of this bug and we’re already investigating it.
-
Console not workingHey @southwalesowl,
Adding the
127.0.0.1 multiportal.calligo.cloudhosts entry just allows MultiPortal and the console server to talk to each other locally, however, the error you now haveECONNREFUSED 127.0.0.1:443means 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
-
Console not workingHave you been able to connect to the console using the Service Provider account?
If not, can you please run through the steps outline on this page, particularly the one around the API key: https://docs.multiportal.io/troubleshooting/console-server/
Matt
-
Import-Export of OVA/OVF file directly from MultiPortal consoleHey @r.balboni
I’ve got this on the roadmap for 1.3.0. I’m literally reviewing roadmap items and timings (along with specifications) now, and it’ll definitely be in :)
Thanks
-
MultiPortal v1.1.3 – Several Issues Encountered with Proxmox VE 9.2.3Hey @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_statstable 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.logandruntime/logs/VirtualMachine.logaround 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 invokingphp 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/processis listed, enabled, andLast Runis updating - Please run
php yii migrate --interactive=0so 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/processmanually. If the network gets attached and the lingering task closes, scheduling is the only thing missing. - It’s also worth running
./yii cron/indexmanually 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.