web gui not accessible

fakker

Member
Apr 2, 2022
8
0
6
Hi - I've previously had this working, but on booting the proxmox server (intel nuc) I cannot access the web GUI any more.

I have confirmed the IP address of the box is 10.1.1.151 (via the CLI). I can ping that address from my windows PC.

I have Frigate running on the server and nothing else. That also isn't accessible via the web.

I ran ss -antlp | grep 8006 which gave the following

LISTEN 0 4096 0.0.0.0:8006 0.0.0.0:* users:(("pveproxy worker", pid=944,fd=6), ("pveproxy worker", pid=943,fd=6), ("pveproxy worker", pid=942,fd=6),("pveproxy worker", pid=941,fd=6))

When I boot the server up, I do get an ACPI BIOS error - but I still then get to the Proxmox login. Could that be something to do with it?

the specific error on boot is ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._PPC], AE_NOT_FOUND (20210730/psargs-330)

It then goes on to list a few times ima: Error Communicating to TPM chip

(I've also tried from different devices and browsers)

Any ideas?!
 
Last edited:
Hi,

did you maybe enable the firewall on accident? Please check if there are any errors in the syslog (/var/log/syslog). The access log for the GUI is located at /var/log/pveproxy/access.log, do you see any of your requests being logged in there?
 
Hi,

did you maybe enable the firewall on accident? Please check if there are any errors in the syslog (/var/log/syslog). The access log for the GUI is located at /var/log/pveproxy/access.log, do you see any of your requests being logged in there?
Hi @nunner,
I have a similar problem and I am replying to this post as this is very recent.

Currently, my GUI is only accessible from the VMs running inside the Proxmox. I cannot access it using any other machine in the same subnet.

I looked at the access log for the GUI /var/log/pveproxy/access.log, but I do not see any other requests being logged in there except from the VM that can access the GUI.

I also restarted the services using systemctl restart pveproxy.service pvedaemon.service but it did not fix the problem as well.
This only happened recently and the server GUI was working fine a few weeks ago. What could be the reason?

Regards.
 
Any changes in the networking side of your infrastructure, like having a VM doing firewall or routing duties?
Otherwise can you describe your networking layout.