How to troubleshoot web UI timeouts/hangs?

[Sod Almighty]

I'm having serious problems with the web UI on one of my Proxmox systems.

The problem is basically that the page fails to load, or hangs, or times out. This can happen when I first navigate to the web UI, or when I log in, or when I'm just interacting with the UI normally. Sometimes it works, sometimes it doesn't. The severity varies, but the problem is frequent and annoying.

I get timeouts like the following:

I also get "please wait" messages that don't go away until I refresh the page. Refreshing often doesn't work, and I have to wait a minute or two and try again.

I have googled; and I have checked these forums for existing threads. I have tried multiple browsers. I have tried connecting from multiple computers. I have checked my router's firewall settings.¹ I have rebooted the Proxmox machine and also my router. I have tried reinstalling Proxmox; and I have tried upgrading from Proxmox 6 to Proxmox 7.

The problem is fairly recent: I first noticed it a couple of months back. I considered that the issue might be related to the recent Root SSL Certificate Issue, but I have another system (running Proxmox 5) and that works fine.

The actual virtual machines themselves seem unaffected. I can SSH into the Proxmox system and into the child VMs without randomly losing connection.

I'm getting to the end of my tether with this. Should I downgrade to Proxmox 5, or are there other troubleshooting steps I could take?

---

¹ I normally have IPv6 blocked on my router, but I temporarily re-enabled it and that didn't help either.

 

[dcsapak]

you can:

* check the browser console (typically accessible with F12)
* check the hosts syslog/journal/etc.

though, timeouts are most often a network issue, so maybe check if there is anything broken in your network setup (duplicate ips, broken cables/switches/etc)

 

[Sod Almighty]

I already checked the browser console. I didn't find anything helpful there.

dmesg shows entries like:

[Tue Nov  9 22:24:18 2021] vmbr0: port 5(fwpr200p0) entered blocking state
[Tue Nov  9 22:24:18 2021] vmbr0: port 5(fwpr200p0) entered disabled state
[Tue Nov  9 22:24:18 2021] device fwpr200p0 entered promiscuous mode
[Tue Nov  9 22:24:18 2021] vmbr0: port 5(fwpr200p0) entered blocking state
[Tue Nov  9 22:24:18 2021] vmbr0: port 5(fwpr200p0) entered forwarding state
[Tue Nov  9 22:24:18 2021] fwbr200i0: port 2(tap200i0) entered blocking state
[Tue Nov  9 22:24:18 2021] fwbr200i0: port 2(tap200i0) entered disabled state
[Tue Nov  9 22:24:18 2021] fwbr200i0: port 2(tap200i0) entered blocking state
[Tue Nov  9 22:24:18 2021] fwbr200i0: port 2(tap200i0) entered forwarding state
[Tue Nov  9 22:37:21 2021] fwbr119i0: port 2(tap119i0) entered disabled state
[Tue Nov  9 22:37:21 2021] fwbr119i0: port 1(fwln119i0) entered disabled state
[Tue Nov  9 22:37:21 2021] vmbr0: port 7(fwpr119p0) entered disabled state
[Tue Nov  9 22:37:21 2021] device fwln119i0 left promiscuous mode
[Tue Nov  9 22:37:21 2021] fwbr119i0: port 1(fwln119i0) entered disabled state
[Tue Nov  9 22:37:21 2021] device fwpr119p0 left promiscuous mode
[Tue Nov  9 22:37:21 2021] vmbr0: port 7(fwpr119p0) entered disabled state

I don't know if they're relevant? Or if they're normal behaviour?

It can't be a broken network cable/hub/etc, or an ip conflict, because SSH works without a problem.