Recent content by cwoelkers

I do have a cluster and have defined a separate network interface for corosync to handle that traffic which exists on our management VLAN(not VLAN 1). As I wanted access to the web interface on that VLAN I needed to add the interface's IP address to the SSL cert before everything worked.

I figured it out. The certs I generated initially did not have the cluster interface IP defined as a Subject Alternative Name, just the main IP and the hostname. Once I added it everything worked fine.

Funny, I am also a Chris. Guess we really are everywhere. Anyways... The root certificate is valid through 2025 so no worries there. I installed the certificate using the web GUI by under System > Certificates for each host using the "Upload Custom Certificate" button. Here is the requested...

I'm running a cluster of four Proxmox community servers, Proxmox 7.3-3 on Debian 11, in a cluster. I was getting tired of the SSL warnings from the self-signed certificate so created a CSR on each and signed them on my local CA server, I'm aware of ACME but did not want to use an external...

Thank you for posting this. I would make one change in leaving the restart button available. Even if you accidentally hit it, and then blindly click through the affirmation, then at least the system will only reboot. That said these buttons should be removable via an option. SSH, KVM, and...

I admin a four node cluster that has recently been upgraded from Debian Stretch, and Proxmox 5.x, to Debian Buster and Proxmox 6.x. The latest updates are installed on all nodes. After upgrading the cluster I moved my focus to the LXC containers and QEMU virtual machines. The VMs had no issues...

That's kinda what I thought it would take. I'll try it today when I can.

The target storage is a local LVM "drive" of at least 200GB of available storage, different hypervisors. The overall storage space of the VM should be no more than 180GB, the total size of the VM's drive. I could see the issue of the source archive being corrupted. That's why I tried backing up...

I am attempting to replace one of our hypervisors. It is not part of the cluster, though the new one will be. I was able to get all but one of the VMs that was running on it transferred to the other hypervisors via the backup, transfer, and restore method. But one of them is being problematic...

Also thought of something and checked the cookies stored in my browser, after clearing them all and logging into the web interfaces four proxmox servers we have. Three of the servers leave a cookie, the fourth, vhost2 the one that I added to the cluster, does not. This is probably part of the...

The problem seems to have gotten better in some ways. The authentication prompt does not come up as often but will still do so. One place it will come up is when I attempt to restore a VM from a backup. The prompt pops up when I try to select a storage location, and then constantly during the...

Yes I can ssh between all nodes, no password needed. Here is the pvecm and command output from the first, ie the first in the cluster, node: root@vhost4:~# pvecm status Quorum information ------------------ Date: Wed Apr 11 09:07:28 2018 Quorum provider: corosync_votequorum Nodes...

So one of the hosts has been rebooted, the one without any VMs, and the other I have restarted the three services you mentioned. The problem seems to have changed somewhat. If I stay on a screen that is within the host that I initially logged into, say a VM within vhost4 after logging into it...

The vhosts are each on a single physical link via 10Gbit Ethernet to the switch. Each makes use of a set of bridges to provide access to various VLANs as needed. One of those VLANs is our management network, no user access, and that is what I have the cluster communications set to use. I know...

I have a total of four Proxmox 4.4 servers running in a production environment. They are of differing ages, the fourth, vhost4, was added recently and when it was the other three were recreated with Proxmox 4.4 in such a way as to minimize service interruptions. When it was first installed...