GUI crashes within minutes after IP change

VioDor

New Member
Feb 22, 2022
5
0
1
Denmark
A bit of background: I recently changed from a old hardware router to Pfsense hosted on Proxmox. Pfsense has its own WAN & LAN port with PCI passthrough to a dual NIC and Proxmox managment has its own NIC(onboard).

After changing the IP range in my network from 10.0.8.1 to 192.168.1.1 and checking the connection to all other servers & managed switch I have running, I havent been able to connect to Proxmox GUI, kinda. I changed Proxmox to be hosted on 192.168.1.201 and the DHCP leasing range is from 0.100-0.199 so that IP shouldnt be handed out to another service.

Code:
------------------------------------------------------------------------
Welcome to Proxmox Virtual Enviroment. Please use your web browser to
configure this server - connect to:

    https://192.168.1.201:8006/

-------------------------------------------------------------------------

pve login:

Code:
/etc/hosts

127.0.0.1 localhost.localdomain localhost
192.168.1.201 pve.home.arpa pve

#IPv6 not configured

Code:
/etc/network/interfaces

auto lo
iface lo inet loopback

iface enp5s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.201
        gateway 192.168.1.1
        bridge-ports enp5s0
        brigde-stp off
        bridge-fd 0

iface enp4s0 inet manual

iface enp8s0f0 inet manual

iface enp8s0f1 inet manual


I can ping both 192.168.1.1 & 8.8.8.8 from proxmox when logging into proxmox directly from the host. I can also ping proxmox (192.168.1.201) from my windows machine. All with succes.

To make matters worse, I was able to connect directly to proxmox with a cable from my windows machine and open the GUI in Edge for a couple of minutes before it crashed. As I am writing this I was able to connect to the GUI for around a minute before crashing yet again. Its only the GUI that crashes from what I can gather since pfsense is stil running and I can still ping from and to Proxmox. It seem to be random when I can connect to the GUI but either way it crashes soon after.

I have attached a picture from the network tab in Proxmox. I dont know why but enp8s0f0 seems offline but those are the NICs, pfsense uses.
 

Attachments

  • proxpic.PNG
    proxpic.PNG
    39.5 KB · Views: 11
Have you tried restarting 'pveproxy'? systemctl restart pveproxy.service
Are you sure that the IP address isn't in use anywhere else in your network?
 
Thank you for your reply.
I Haven't tried restarting pveproxy.service but wouldn't a complete restart of the host do that too? I'll give it a shot when I get home.
Did a nmap scan of my network just to be sure and there is no hidden service pulling the same IP from what I can see.
 
I Haven't tried restarting pveproxy.service but wouldn't a complete restart of the host do that too? I'll give it a shot when I get home.
Yeah, a host reboot would also be an option (perhaps a better one). I just suggested restarting pveproxy, as some users are reluctant to reboot their system unless absolutely necessary.
Let me know how it goes!
 
I tried restarting the host several times before writing this post with no positive outcome unfortunately. I only host pfsense atm so have no issue restarting it since the VM start up perfectly after the restart within minutes. But I'll give the restart of pveproxy a shot more
 
Sorry for the late reply I finally got to it and it seemed to work for a whole 2 minutes and then the GUI went offline again unfortunately. I tried connecting through the browser, no connection. Then I ran the command you provided me with, reloaded the site and I connected no problem. After a minute or two it started having trouble loading the VM values and then "Error connection error - server offline?". I pinged the server with cmd, no loss and again pinged my pc from proxmox with a HDMI in it, no loss. Im clueless to what this issue can come from, the server connects and then drops after minutes.
 
Do you notice any strange lines in the system log ('/var/log/syslog')? In particular any error or warning messages which repeat continuously? Are you able to SSH into the machine?
Could you post the output of (when the GUI is offline):
  • pveversion -v
  • systemctl status pveproxy
  • systemctl status pvedaemon
 
I have not been able to login to the Webgui this morning and I am not able to SSH to pve from my windows machine. Connection times out.
Code:
root@pve:# ss -a -4 | grep ssh

tcp LISTEN 0    128        0.0.0.0:ssh        0.0.0.0:*

root login is allowed

Since I cant login via ssh I have taken pictures with my mobile of the commands you provides me with. Let me know if you cant read it because of the poor quality.

Last picture is from syslog after I ran systemctl restart pve.proxy
 

Attachments

  • 275167198_340534561377680_5830266684642399377_n.jpg
    275167198_340534561377680_5830266684642399377_n.jpg
    566.4 KB · Views: 8
  • 275251908_3067108490284864_944530282925984280_n.jpg
    275251908_3067108490284864_944530282925984280_n.jpg
    411.3 KB · Views: 8
  • 275255692_645658683171676_4701028837245585749_n.jpg
    275255692_645658683171676_4701028837245585749_n.jpg
    745 KB · Views: 8
Ran into this problem with a new hypervisor. Reboot seems to have fixed it, turns out when you update the IPs under Node>System>Network it doesn't reflect it in Node>System>Hostname so if you remove the original IP things start timing out. Stranger yet, when you have two entries (on separate lines at least) it also chokes and crashes.

Tmanok
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!