Good Day Team,
I've started noticing this issue recently where my Proxmox VE host is not pingable or resolvable over the browser. But starts working after several hours of reloads automatically. At the same time, the VM's hosted on the node are perfectly connecting and have no issue resolving their connections to the internet as well.
My tests have been on both Hostname FQDN's as well as IP. Both do not work. This issue seems to have started occurring since I moved to version 7.3-1 . Wondering if anyone could assist me with this issue as it gets increasingly frustrating to wait for the host to be reachable via ping or SSH to start any VM's.
For context, my node is hosted on an Intel NUC 12 Extreme which has a 10G Ethernet connection where only one network bridge has been configured. Several of my VM's work on different VLAN's for testing. While host is on a completely different VLAN.
I've started noticing this issue recently where my Proxmox VE host is not pingable or resolvable over the browser. But starts working after several hours of reloads automatically. At the same time, the VM's hosted on the node are perfectly connecting and have no issue resolving their connections to the internet as well.
My tests have been on both Hostname FQDN's as well as IP. Both do not work. This issue seems to have started occurring since I moved to version 7.3-1 . Wondering if anyone could assist me with this issue as it gets increasingly frustrating to wait for the host to be reachable via ping or SSH to start any VM's.
For context, my node is hosted on an Intel NUC 12 Extreme which has a 10G Ethernet connection where only one network bridge has been configured. Several of my VM's work on different VLAN's for testing. While host is on a completely different VLAN.
Last edited: