Proxmox is here today and gone tomorrow...

[ErikM1970]

Hello everyone,

I am very new to Proxmox and have been trying for the past several weeks to get it set up and configured as a means of developing a home lab. I have been dealing with an issue where I will install, update and configure the system during the evening and then shut it down for the night. Be it the next day or a few days later, when I power the system back up, Proxmox cannot be accessed. The console shows the expected IP address and port; however, the server is inaccessible. It does not respond to PING, my UniFi Controller cannot see it online, nothing. Assuming ignorance on my part, I have made many attempts to carefully set it up and this past week, got an early start and was able to even create three VMs; however, after a shutdown and restart a few days later, it is completely inaccessible. I was hoping one of you could point me to an existing solution or help me figure out why I am continually getting this behavior. This problem has occurred on both 7.3 and 7.4 as I have been troubleshooting this for many weeks now. Thank you for any help that can be provided. I very much would like to learn about this product as it seems perfect for my needs.

Thank you,
Erik

 

[leesteken]

I'm just guessing here but: did you accidently used a DHCP IP address as the static IP address of the Proxmox? Maybe the router does not accept addresses in the DHCP range that it did not give out (or refresh) within a day? Can you please share the contents of /etc/network/interfaces and the DHCP range of your router?
EDIT: Or you have a duplicate IP address on the local subnet (due to it being given to another system using DHCP after installing Proxmox)?

 

[ErikM1970]

Thank you for the reply. When I was setting up the system, I checked and saw that UniFi had assigned it an address of 192.168.1.121. I went ahead and used that address, and was going to establish a DHCP Reservation. I can always change it to a pure static address; however, I have never had an issue like this before. I have a couple of Windows Servers on this same network that was originally assigned an address from the pool, I set up a reservation with that same address and changed the address on the server to static matching with the same. If Proxmox doesn't care for this configuration (methodology,) I can move it to a static address outside of the DHCP Scope.

As for the /etc/network/interfaces, it is shown below. It also includes the start of my trying to separate the management network from a newly created VM network.

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.121/24
gateway 192.168.1.1
bridge-ports eno1
bridge-stp off
bridge-fd 0
#Management Network

auto vmbr1
iface vmbr1 inet static
address 10.0.0.0/24
bridge-ports eth1
bridge-stp off
bridge-fd 0
#VM Network

Thank you again,
Erik

 

[leesteken]

If you want Proxmox to use (a reserved) DHCP, then you need to configure that in /etc/network/interfaces. Otherwise, the DHCP will expire (after installation, because Proxmox will not renew it unless you configure it) and would result in the symptoms you describe. Change iface vmbro inet static to iface vmbr0 inet dhcp and remove the address and gateway lines ( I think).

 

[ErikM1970]

Hello,

I went ahead and logged into the console and changed the IP address in both the interfaces and hosts files to a static IP. I restarted the system and it is now showing https://192.168.1.23:8006 as the address in which to access the management interface. However, as usual, the interface does not respond via this address and port. I found an article where another user had similar issues:

Cannot Access Web Interface

Following through that article, I compared the results and appears that nmap -p 8006 192.168.1.23 is showing:

PORT STATE SERVICE
8086/tcp closed d-s-n

NOTE: There is also a SERVICE discrepancy where wpl-analytics appears for the other user, which I show "d-s-n".

EDIT: Jump ahead 10 minutes or so while preparing this post update. It looks like things don't update immediately. Now nmap is showing the port open for wpl-analytics and my UniFi Controller saw the device but reported no IP address; however, about five minutes later, the IP address was reported.

In the end, I am able to access to GUI. @leesteken thank you for your feedback... it helped me get over this and I do appreciate the guidance. Hopefully, this thread will help others who fall into this same pit I have been in for weeks.

Thank you,
Erik

 

[bbgeek17]

ollowing through that article, I compared the results and appears that nmap -p 8006 192.168.1.23 is showing:

PORT STATE SERVICE
8086/tcp closed d-s-n

NOTE: There is also a SERVICE discrepancy where wpl-analytics appears for the other user, which I show "d-s-n".

EDIT: Jump ahead 10 minutes or so while preparing this post update. It looks like things don't update immediately.

I think its more a case where you typed in forum "-p 8006" to show us what you run. But the output you provided is for port "8086".

---

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