Search results

Hello Fabian, thanks for the reply, after thrashing around a bit this morning it seems I've managed to get this sorted out, yesterday I had added a new node, renamed it, then renamed another established node then regenerated SSL certificates as I was getting SSL errors even from the web...

I know this is an ancient thread but did this ever get fixed? I've followed the SSL FAQ like you have but on linux I'm now getting the same issue; (remote-viewer:32190): Spice-WARNING **: 06:16:26.751: ssl_verify.c:445:openssl_verify: Error in certificate chain verification: self signed...

Ah OK I've done a few quick tests by editing /etc/hosts and this seems to work now so I'll just decide which of the two solutions fits my needs best, thanks for the quick reply.

Hello all, I've installed proxmox on top of Debian as a developer workstation (so the dev workstation is running both a desktop environment and proxmox) and made this part of a cluster. All works fine and when logged into the developer workstation and running the proxmox UI, I can connect to VMs...

OK that seems to have sorted it. It seems that the migration was picking up a bunch of old images and moving them with the VM despite those images not being in the VM's config, once I did the qm rescan it associated those old images with the VM config, making them visible and permitting me to...

Thanks but it wouldn't delete it. I think I have found the source of the problem however, googling for the error message I was given when attempting to delete the phantom disk prompted me to run "qm rescan --vmid 101" which added not just the phantom disc but another two discs to the machine's...

Hello both, the VM is being migrated offline, I did put that in the original post although in parentheses. Here's PVEVersion: root@d01c02n01f:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve) pve-manager: 6.2-10 (running version: 6.2-10/a20769ed) pve-kernel-5.4: 6.2-4...

Hello all, I just created this account to ask this question as I can't find the answer elsewhere. I have a VM set up on a 6.2 community edition cluster. It's not using HA, the cluster is quorate and all seems well. The VM has replication set up for the two other nodes. The documentation...