Search results

Yes I just read through the bugfix correspondence, very interesting communications in there for sure. Yes, I also found the issue whilst upgrading infrastructure and worked out that old keys were appearing despite removing and re-generating. In the end it became annoying and such a waste of time...

Thank you. Yes I knew the symlink was broken/being overwritten with a local file. As a short term workaround I added 'StrictHostKeyChecking no' to each ssh config file since my PVEs are running on their own internal network. I will have a look at this patch.

I see, I was only removing the host name. I will try again and also remove the IPs. Thanks for your reply.

Sure, I've looked in there and I do see entries for each host using it's IP and name. Which ones do I remove ?? Can I just remove all and run updatecerts to refresh them all ?

Hi All, I have a cluster of 5x PVE 7.4 nodes which we recently upgraded onto new hardware. We did this host by host and it all worked fine, however every time I try to remote console (NoVNC) I get "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! " This is likely due to old host keys still...

Thank you Stefan, much appreciated. I will update the certs on all cluster nodes.

Hi All, I recently upgraded a cluster of 5x PVE 7.3 nodes to 7.4-16 at the same time as performing hardware upgrades (complete server replacement). The approach used was migrate workloads off one node at a time, delnode and remove host folder in /etc/pve/nodes, then re-join cluster as new...

Yes this is production. Thanks for the input, much appreciated.

Hi All, I have 2 clusters running PVE 7.3 where we are about to upgrade hardware to new HP Proliant servers. I've done some reading and can see at least some benefits and improvements for installing PVE 8, however these PVE clusters all run local storage with Infiniband cards and don't use any...

Just following up on this, today I re-installed PVE then patched and applied custom configs before re-joining the cluster. All worked perfectly fine, no issues.

Thankyou for the reply. Working with corosync always results in stress for me since it's easy to break and there are always dramas everytime it stops working properly. I tried for hours to recover the failed node mainly as a learning exercise however despite the corosync configs all being...

Hi All, I'm in the process of upgrading from 7.1-10 to 7.3-3 and the upgrade failed on 1 of 5 nodes. I have not progressed with any further upgrades and ended up shutting down the failed node. The other nodes have all voted and are online, working fine. The node which failed is node 1 (ie...

Hi All, We're seeing a strange issue with a handful of Windows 2012 STD R2 VMs on Proxmox 7.1-10, virtio 0.219. The VMs are up to date with patches. They run fine for weeks, then without notice they crash. On reboot the VM launches into Windows Automatic Repair Mode. This never works, even...

Hi Stoiko, Yes, all connections are on HTTPS/SSL. The certificate is valid and working. Normal admin works fine using the SSL hostname. The curl command output does show it found the SSL. Thanks BeDazzler.

Hi, I have a new Proxmox 6.3 server installed with remote access via IPSec VPN (we use pfSense at both ends of the VPN). On the local network next to the Promox server everything works fine and I can access both web interface and API with no issues. However, when remote at the other end of...

Stoiko, that's fine, I don't expect you to instantly come up with all the answers. Yes the community has been good, I have also contributed back to help others because I know it's a valuable resource.

I was hoping for a little more help from you. I am relatively new to Promox, however I am comfortable with Linux/UNIX. A simple point in the right direction would have helped me find the answer sooner rather than silence.

Answering my own question to help others with the same issue. I could not get Proxmox to work with the DigiCert RapidSSL cert, no matter what we tried. I cancelled it, ordered another cert and installed - now working. Proxmox 6.3 didn't know or see there was an issue with the cert, it just...

Has nobody else encountered this issue ? Are there any known issues using external CAs and methods other than ACME/LE with Proxmox ?

Hi Stoiko, Thank you for the reply. Output of journal shows all OK May 28 18:44:02 xxxx-pve04 systemd[1]: pveproxy.service: Succeeded. May 28 18:44:02 xxxx-pve04 systemd[1]: Stopped PVE API Proxy Server. May 28 18:44:02 xxxx-pve04 systemd[1]: Starting PVE API Proxy Server... May 28 18:44:03...