Hi there,
try to restart pve proxy
systemctl restart pveproxy
The client is in the same network and subnet. I'm trying to type it that way and still nothing.And make sure you actually type in "https://10.0.10.254:8006" and not simply "10.0.10.254:8006" or "http://10.0.10.254:8006".
And your Client has to be part of the same subnet.
systemctl status pveproxy.service pvedaemon.service
curl https://localhost:8006 -k | grep title
ss -tulpn
lspci | egrep -i --color 'network|ethernet'
ip addr
shouldn't show "NO-CARRIER" for that NIC.The curl comand isn't working.Check if the pveproxy service is running:systemctl status pveproxy.service pvedaemon.service
Check if you can access the webUI from localhost:curl https://localhost:8006 -k | grep title
Check if the server is listening on port 8006:ss -tulpn
Check if the NIC uses a RTL8111/8411/8168 chipset:lspci | egrep -i --color 'network|ethernet'
If your host got multiple NIC check if your cable is plugged into the correct port. Anip addr
shouldn't show "NO-CARRIER" for that NIC.
Verify that your chosen IP isn't used twice (so no other machine already using it).
Verify that your chosen IP is outside of the DHCP IP range of your router.
In case you ever edited the network config, make sure you don't gave that PVE host multiple IPs that are part of the same subnet.
Try another ethernet cable in case that cable is broken.
Reboot your router and PVE server.
Check your routers/clients firewall rules.
Do you mean etc/hosts?pve host is currently at 10.0.0.250 not 254
I bet on 254 was set during install then you've edited to 250.
the banner on the console isn't updated.
No, you gave it 10.0.10.250 and not 10.0.10.254.Do you mean etc/hosts?
We use essential cookies to make this site work, and optional cookies to enhance your experience.