That's great! I was expecting "it's not done yet" so "here's how to do it, but it's subject to change" is better then that!
Proxmox Datacenter Manager - First Alpha Release
- Thread starter t.lamprecht
- Start date
When Proxmox VE updates a Let's Encrypt certificate then Proxmox Datacenter Manager always gives the error that it cannot verify ssl cert. (Since the thumbprints do not match.)
I get that you want to verify the thumbprint but when using Let's encrypt then it really gets to be a pain.
I get that you want to verify the thumbprint but when using Let's encrypt then it really gets to be a pain.
it doesn't make sense to pin the fingerprint in this case, just let the cert be verified via the system trust store by leaving the fingerprint out..
That is what I would expect. But when I remove the fingerprint, it still shows the SSL cert verify error.
I fixed it for now with adding the new fingerprint but when I have time later today I will remove it again and post the errors.
I simply disabled 2FA for the account temporarily, got PDM to generate the token, then after connecting re-enabled 2FA again. Seems to be ok so far.
Nice Job!!
Is there a possibility this tool to use
It is waaaaay faster and it also has the bonus of preserving any zfs dataset snapshots...
I apologize in advance if this has been asked a million times, I started to read through the commends on this thread to see if this was asked before or not, but gave up at around page 5...
Is there a possibility this tool to use
syncoid for migrating in the cases where the VMs are using [B]ZFS[/B] on both sides of the migration?It is waaaaay faster and it also has the bonus of preserving any zfs dataset snapshots...
I apologize in advance if this has been asked a million times, I started to read through the commends on this thread to see if this was asked before or not, but gave up at around page 5...
no, but there are plans for extending the built-in replication feature to allow replicating across clusters (and re-using this replication state for migration, just like we do when migrating within a cluster with replication enabled).
Is it normal that live migration of LXC containers is no longer possible?
When I try, the container is turned off and on again after migration.
I seem to remember that this was possible.
When I try, the container is turned off and on again after migration.
Last edited:
you misremember - live migration for containers does not exist and never has.
it's a very tough problem to solve for generic containers, so I'd not get my hope's up 
after this I can't make a backup of this VM:
Before the unsuccessful migration I made a backup of this VM
Task viewer: VM/CT 10022 - Backup
OutputStatus
Code:
INFO: starting new backup job: vzdump 10022 --storage ssdstorage --node rfqsrv0 --mode stop --notes-template '{{vmid}} | {{guestname}} | {{node}}' --compress zstd --all 0 --fleecing 0 --prune-backups 'keep-last=1'
INFO: Starting Backup of VM 10022 (qemu)
INFO: Backup started at 2025-03-24 13:59:23
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: Copy-of-VM-CLOUDRON-rfq4u.ru
INFO: include disk 'scsi0' 'nvmestorage:10022/vm-10022-disk-0.qcow2' 500G
INFO: creating vzdump archive '/mnt/ssdstorage/vz/dump/vzdump-qemu-10022-2025_03_24-13_59_23.vma.zst'
INFO: starting kvm to execute backup task
ERROR: unable to add /mnt/ssdstorage/vz/dump/vzdump-qemu-10022-2025_03_24-13_59_23.tmp/qemu-server.fw config data to vma archive
INFO: aborting backup job
INFO: stopping kvm after backup task
trying to acquire lock...
OK
ERROR: Backup of VM 10022 failed - unable to add /mnt/ssdstorage/vz/dump/vzdump-qemu-10022-2025_03_24-13_59_23.tmp/qemu-server.fw config data to vma archive
INFO: Failed at 2025-03-24 13:59:25
INFO: Backup job finished with errors
TASK ERROR: job errors
Last edited: