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...
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...
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...
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...
This seems more a feature request than anything but I thought this would be a good place to start.
My office uses smartcards for authentication of just about everything. Computer logins, web sites, email, etc and all authentication is verified via Active Directory. It has been requested by our...
Here is what I am trying to do, and how I seem to have failed.
I manage 4 hypervisors. One is brand new and 4.4 was installed on it. The other 3 are all older, 2 with 3.2, and one with 4.1. The plan was to move the VMs, a mix of containers and qemu, from one of the old hypervisors to the new one...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.