Virtual Environment 6.4-13 Cluster (x4 nodes)
Using NGINX VM as a reverse proxy for VMs on private address space (VMBR1)
The issue is that starting and stopping any VM on the node with the Proxy causes all VMs to have a network timeout of circa 15 seconds before connecting as expected again...
Hi Moayad,
I believe i did see that thread but wanted to check with the experts before attempting.
So for the avoidance of doubt.... you are saying "remove the transport line from the corosync configuration and continue with the upgrade ?"
Currently running 4 node Promox cluster 5.4-15 with Ceph and trying to upgrade to Proxmox 6 and then hopefully Proxmox 7.
I have followed all the instructions documented on your site including https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0#Cluster:_always_upgrade_to_Corosync_3_first
The...
Updated Proxmox cluster with licences and update fails.
x4 Proxmox 5.3-8 nodes clustered and each node shows that the subscription is valid.
I have tried manually running update command but both this and the scheduled proxmox task fail with this error.
Any assistance would be greatly appreciated.
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.