Lost access to GUI - getting "Problem loading page" error

[helloworld1]

I have Proxmox VE set up on a Dell Optiplex system which has been working fine for years until now.

Recently I had to take the PCIE based Intel NIC card out of it to test it in another system. in the meanwhile I tried turning it on using the onboard NIC but couldn't connect to it but thought nothing of it and turned it back off.

A week later, I have not put the Intel NIC card back into the machine that has proxmox installed but can't connect to it via GUI.

I can see the IP address assigned to the machine and have gone through some of the basic troubleshooting steps mentioned here on the forum but couldn't find any errors popping up within any of the logs - unsure how to troubleshoot the issue further to be able to connect back to it.

Yes, I am trying to access using https://192.168.10.40:8006/

After the Proxmox system boots up, it says on the screen that I need to connect to https://192.168.10.40:8006/

Logging as the root user on the Proxmox system, I can see the machine is getting an IP addr assigned to it from my pfsense firewall.

Unsure how to paste the output from the Proxmox system here since I can't access it from my system but can post images though.

 

[leesteken]

Recently I had to take the PCIE based Intel NIC card out of it to test it in another system. in the meanwhile I tried turning it on using the onboard NIC but couldn't connect to it but thought nothing of it and turned it back off.

Removing (or addind) PCI(e) devices can change the PCI ID of other devices (by plus or minus one). The name of the network devices depends on the PCI ID, unless you used udev rules to fix them to something else. Use (a physical display and keyboard to run) ip a to find the new names and adjust the network device names in /etc/network/interfaces accordingly. This happens somewhat regularly to people and there are several threads about it on this forum.

 

[helloworld1]

ah okay - never thought it could be an issue.

Does this happen even when the same NIC card is removed and added back to the machine?

 

[leesteken]

ah okay - never thought it could be an issue.

Does this happen even when the same NIC card is removed and added back to the machine?

It could if you used another slot, since also influences the PCI ID. Please show a photo of the outputs of ip a (without any VM/CTs running) and cat /etc/network/interfaces.

 

[helloworld1]

I don't remember setting up any udev rules when I set up this Proxmox machine - just the simple vanilla install.

I will have just checked the ID based on what you mentioned - all appears be ok.

I have added the outputs as photos as I can't copy + paste the output fro the proxmox terminal.

 

[helloworld1]

It could if you used another slot, since also influences the PCI ID. Please show a photo of the outputs of ip a (without any VM/CTs running) and cat /etc/network/interfaces.

Learned something new today, thanks.

I have only got the one PCIE slot though so unlikely to happen in my case.

 

[leesteken]

I don't remember setting up any udev rules when I set up this Proxmox machine - just the simple vanilla install.

I will have just checked the ID based on what you mentioned - all appears be ok.

I have added the outputs as photos as I can't copy + paste the output fro the proxmox terminal.

You configured enp4s0f1 for Proxmox but that has no working cable attached (NO-CARRIER) but enp3s0f0 does have a connection. Maybe unplug the cable and plug it in the correct port? Or change the network configuration manually to match the device that has a cable?

 

[helloworld1]

Legend.. I am pretty sure I have already tried switching the cable between all the ports but I will try again now.

Thanks mate.

 

[leesteken]

Legend.. I am pretty sure I have already tried switching the cable between all the ports but I will try again now.

Thanks mate.

If it's a 4 port network controller, it's the port on the most other side probably. You might have to reboot the Proxmox host.

 

[helloworld1]

Just had to do a static IP mapping again after you helped me identify the issue and it started working - it wasn't getting the correct IP addr assigned from DHCP even after switching the cable to the correct port.

Appreciate your help - such a relief - been at it for hours now haha.

 

[leesteken]

Just had to do a static IP mapping again after you helped me identify the issue and it started working - it wasn't getting the correct IP addr assigned from DHCP even after switching the cable to the correct port.

Appreciate your help - such a relief - been at it for hours now haha.

Your Proxmox is not configured for DHCP and has a static IP address, so I don't really understand, but glad you got it fixed.

 

[helloworld1]

Your Proxmox is not configured for DHCP and has a static IP address, so I don't really understand, but glad you got it fixed.

Sorry - I meant static IP mapping within pfsense - unsure why it was assigning Proxmox a different IP address this time when it was working all fine with the IP assignment about a week ago.

I am glad it is working now though.