ERR_CONNECTION_REFUSED on Web UI and SSH after update

[DoNotCorrelate]

Installed Version: 7.3-1 on a single host (Dell PowerEdge T420)

After installation host could be reached from SSH and using the webGUI (https://192.168.11.5:8006) created a single VM, did not modify any host settings

Added the no-subscription repository, checked for updates and applied them all, host kept working fine, then I went for the recommended reboot, after that the server cannot be accessed from the web GUI nor from SSH, I get ERR_CONNECTION_REFUSED on web browsers and timeout using Putty

Already tried different browsers and devices, confirmed the static IP used is in a non DHCP region of the internal network.

I can ping the device, ports 22 and 8006 show as closed (Currently testing from a wireless device, issue is the same on wired devices)



This is the output of pveversion -i



Output of systemctl | grep pve


Issue remains after another reboot and after selecting the previous kernel from GRUB



I have been able to reproduce the issue twice (1st time I just nuked the whole installation as I thought it could have been an issue with the ISO I used)

Thanks

 

[bbgeek17]

What is the output of:
PVE: ip a
PVE: cat /etc/network/interfaces
PVE: curl -sk https://192.168.11.5:8006|grep title
Workstation: arp -a|findstr 192.168.11.5
Workstation: arp -a|findstr /I [macofpve]

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[DoNotCorrelate]

Also: It suddenly started to work, but it stopped after a reboot.

The 1st time I had a similar issue, it would randomly work after a number of restart but then stop working without any pattern, seems to be consistent then from the 1st time

 

[bbgeek17]

you can make things much easier if you use CODE tags and paste text output rather than blurry images.

Beyond that, take a good look at the MAC address of the PVE interface, do you see how it ends in 38:da?
Now look on your windows box - do you see a completely different MAC in the second screenshot?

In the 3rd one you were supposed to replace "[macofpve]" with the actual MAC of your PVE host. But we already know what the issue is - duplicate IP.
The MAC found by windows is LAA (Locally administered addresses (LAA): the address is assigned to a device by a network administrator, overriding the burned-in address.). This likely means that it belongs to a VM of some sort.

good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[DoNotCorrelate]

Yes, I would rather use code blocks, it is just that in this case I only have access to the server's console using iDrac, I would have to manually transcribe the output

Thanks for taking the time to answer!

I see the issue!

I pulled up the ARP table of my router and correlated the MAC address with another IP an IPv6, some days ago I modified my DHCP range from 1-253 to 11-253 so I could use the 1st 10 for statically assigned IPs

It also had a setting enabled where DHCP reservations are automatically created for connected devices, which means it was ignoring the DHCP scope change I made to accomodate Proxmox and was still giving the .5 lease to a device that was not supposed to be using that lease anymore

I removed the reservation, forced the device to grab a new lease and we're back up

Thanks for your assistance