[SOLVED] Can't access UI

[manwealmighty]

Hello As the post says, I set up the server successfully some time ago. I even have a VM with Home Assistant running, and I can access that VM just fine. The problem is that I can't access the Proxmox GUI.

I have PFSense with a static mapping set for the Proxmox machine, and it seems to be assigning the IP just fine,
and I am guessing that this is not a firewall problem because if it was I should be able to access homeassistant which is in the same ip range.

I have also tried plugging in a keyboard and a monitor to the machine and I get the following prompt:


After this prompt, I tried typing, and nothing seemed to happen; the keyboard is working fine, btw.

This is weird because the IP that should be displayed is .201 and not .11

So I am a bit lost here; I am not sure what to try next, it has to be related to networking because I cannot ping the Proxmox IP.

Any help would be appreciated.

 

[bbgeek17]

Hi @manwealmighty , welcome to the forum.

There are a few things to consider:
a) DHCP is not a recommended way to assign IP to the PVE appliance
b) The fact that your DHCP server reports a different active IP for PVE than the one reported in the shell implies that the IP has changed over time. If you use DHCP - you should assign a static mapping to the PVE host.
c) You have not indicated when the IP change has occurred. Was it on reboot? During steady operations? The system's services should be restarted on IP change.
d) The IP reported on the physical console is stored in a text file and sometimes does not match the running configuration. The proper way to find the actual running configuration is to log in to the PVE and execute "ip a"
e) Assigning IP to PVE, or any hypervisor, from a VM that runs on that hypervisor is not a great idea. There are too many opportunities for a race. Many of the PVE services that depend on IP information being in place have already started before the VM.
f) A none-working keyboard could be an indication of a bad USB port (or PS/2 ?), an uninitialized driver, or a deficient BIOS that can't handle the keyboard being plugged in later in the boot process.

---

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

 

[manwealmighty]

I have a static IP mapping, sorry if I wasn't clear, and it is assigned properly or that is what PFSense states?
The keyboard does work fine on boot to select the OS to boot on.

Thanks for the help btw!!

It looks inconsistent I know, I changed the IP assigned to the Proxmox in hopes that, that would fix it, knowing it probably wouldn't.

 

[bbgeek17]

I have a static IP mapping, sorry if I wasn't clear, and it is assigned properly or that is what PFSense states?

Great.

It clearly changed at some point, since the first IP recorded by the PVE was different. There is a service that supposed to update the file but even if it did not - the console information is not in the critical path of IP networking.

You have not described what "can't access the Proxmox GUI" actually means, so there could be dozens if not hundreds of solutions.

Yes, the fact that you can access a VM is a good indication that the NIC, switch and the many other layers are functioning.
So your issue (still undefined) could be a duplicate IP, firewall on the client, extension in the browser, issue with a physical router/switch processing that particular IP conversation, etc.

As for the keyboard, try a different port, check the BIOS for any related settings, try to boot another OS from an ISO/CD/USB.

---

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

 

[manwealmighty]

Yeah sorry can't acces the GUI is more like can't even reach the Proxmox server but can reach what Proxmox is hosting.

So for the IP part, it cannot be a duplicate IP if I am the one defining the IPs that each device use, the IP pool that PFSense DHCP Server can pick from is outside this range, I have also changed the IP just in case and that didn't work.

---- Update

I have managed to login and I found the IP that the proxmox server was actually using, I don't get it, I assign an IP through PFSense it says that it is using that IP but it turns out that is not the case.

 

[bbgeek17]

I have managed to login and I found the IP that the proxmox server was actually using, I don't get it, I assign an IP through PFSense it says that it is using that IP but it turns out that is not the case.

PVE is a set of original packages providing a great Hypervisor experience on top of Debian Linux.

The DHCP interaction is not customized by PVE developers. It is essentially Linux DHCP with PFSense, i.e., basic Linux system administration.
I am not an expert on PFsense, perhaps, someone else can chime in. You may get better assistance in the PFSense forum. They could point you to where the DHCP logs are located which could contain some clues.

Best,

---

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

 

[manwealmighty]

Okey final updates, thanks for the help bbgeek17 everything works now!, I changed the host file and the Linux Bridge.