[SOLVED] Cannot Access Web Interface

[rchamp26]

I had an issue this morning not accessing the web interface on 7.3-4. I put the machine to sleep last night and wake-on-lan this morning.

ssh worked fine, but couldn't access from webgui.

i had a permission denied on /var/log/pveproxy/access,log permission denied.

so i did a rm /var/log/pveproxy/access.log and
touch /var/log/pveproxy/access.log

and then restarted the services and now i can access the gui again. weird issue as I also have nothing running on this machine yet. just stood it up a couple days ago to begin tests

 

[ilbarone87]

I had an issue this morning not accessing the web interface on 7.3-4. I put the machine to sleep last night and wake-on-lan this morning.

ssh worked fine, but couldn't access from webgui.

i had a permission denied on /var/log/pveproxy/access,log permission denied.

so i did a rm /var/log/pveproxy/access.log and
touch /var/log/pveproxy/access.log

and then restarted the services and now i can access the gui again. weird issue as I also have nothing running on this machine yet. just stood it up a couple days ago to begin tests

Which services have you restarted?
I'm still unable to access after even rebooting node1 (i have a cluster with 2 nodes). Followed your process on both but no luck...

● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2023-02-19 00:32:04 GMT; 4min 17s ago
    Process: 1035 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1037 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1039 (pveproxy)
      Tasks: 4 (limit: 19011)
     Memory: 136.9M
        CPU: 10.071s
     CGroup: /system.slice/pveproxy.service
             ├─1039 pveproxy
             ├─2813 pveproxy worker
             ├─2814 pveproxy worker
             └─2815 pveproxy worker


Feb 19 00:36:22 HostTheBaron pveproxy[2814]: worker exit
Feb 19 00:36:22 HostTheBaron pveproxy[2815]: worker exit
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: worker 2814 finished
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: starting 1 worker(s)
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: worker 2849 started
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: worker 2815 finished
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: starting 1 worker(s)
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: worker 2850 started
Feb 19 00:36:22 HostTheBaron pveproxy[2849]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 19 00:36:22 HostTheBaron pveproxy[2850]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied

 

[rchamp26]

Which services have you restarted?
I'm still unable to access after even rebooting node1 (i have a cluster with 2 nodes). Followed your process on both but no luck...

● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2023-02-19 00:32:04 GMT; 4min 17s ago
    Process: 1035 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1037 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1039 (pveproxy)
      Tasks: 4 (limit: 19011)
     Memory: 136.9M
        CPU: 10.071s
     CGroup: /system.slice/pveproxy.service
             ├─1039 pveproxy
             ├─2813 pveproxy worker
             ├─2814 pveproxy worker
             └─2815 pveproxy worker


Feb 19 00:36:22 HostTheBaron pveproxy[2814]: worker exit
Feb 19 00:36:22 HostTheBaron pveproxy[2815]: worker exit
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: worker 2814 finished
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: starting 1 worker(s)
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: worker 2849 started
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: worker 2815 finished
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: starting 1 worker(s)
Feb 19 00:36:22 HostTheBaron pveproxy[1039]: worker 2850 started
Feb 19 00:36:22 HostTheBaron pveproxy[2849]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 19 00:36:22 HostTheBaron pveproxy[2850]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied

It was the PVE proxy service. I wonder if you have an issue due to losing quorum since you only have a 2 node cluster when you should have a minimum of 3

 

[ilbarone87]

It was the PVE proxy service. I wonder if you have an issue due to losing quorum since you only have a 2 node cluster when you should have a minimum of 3

Not sure tbh, both of nodes are up. I can SSH to both as well. And VMs are up and fully working.
Also the web gui behind my cert proxmox.mydomain.com is reacheable, but not the private ip address at port 8006.

 

[FaySmash]

I had an issue this morning not accessing the web interface on 7.3-4. I put the machine to sleep last night and wake-on-lan this morning.

ssh worked fine, but couldn't access from webgui.

i had a permission denied on /var/log/pveproxy/access,log permission denied.

so i did a rm /var/log/pveproxy/access.log and
touch /var/log/pveproxy/access.log

and then restarted the services and now i can access the gui again. weird issue as I also have nothing running on this machine yet. just stood it up a couple days ago to begin tests

I only had to recreate the log file and the GUI was available immediately afterwards...
My Web GUI just randomly stopped working and that fixed it. Thanks!, but something as minor as a missing log shouldn't keep the Web GUI from starting...

 

[Loulou91]

Hi,

user http://localhost:8006 instead of https and check.

Looks funny, I just had the same issue and I had to use https instead of http to make it work ;-)

 

[Softlution]

Here is the reason I couldn't access the gui https://youtu.be/jxW2it3v8Ps

 

[raining]

I installed Proxmox on 3 new server and all the procedure from the iso went ok. I configured cluster and tested it, all work like a charm.
Now, after a reboot I cannot access to web interface from any server: login to ssh its ok but from web interface (tested in many browser) always return connection refued.
If I try from ssh console to connect with curl or wget I take this:
root@rvs1:/etc/pve# curl https://localhost:8006 -k | grep title
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8006: Connection refused
root@rvs1:/etc/pve# wget --no-check-certificate https://localhost:8006
--2022-01-17 18:13:36-- https://localhost:8006/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8006... failed: Connection refused.

ss -tulpn
tcp LISTEN 0 4096 [::]:8006 [::]:* users("pveproxy worker",pid=18053,fd=6),("pveproxy worker",pid=18052,fd=6),("pveproxy worker",pid=18051,fd=6),("pveproxy",pid=18050,fd=6))


Tried disable firewall
I updated from repository but nothing changed
All services are active, the test VM also function.

What can I check to solve the problem?
Thanks

i stuck with the topic issue
myself was installing the latest iso that was downloaded today, 18june2023.

after viewing logs, there was cert issues.
go into this site: https://forum.proxmox.com/threads/p...rtificate-chain-after-upgrade-to-pve-6.56060/

long story short: fix.

rm -f /etc/pve/pve-root-ca.pem /etc/pve/priv/pve-root-ca.* /etc/pve/local/pve-ssl.*

pvecm updatecerts -f

 

[Dulcow]

I solved:
nano etc/default/pveproxy
insert:
LISTEN_IP=0.0.0.0
save
restart
systemctl restart pve-cluster.service
systemctl restart pveproxy.service

Now all function correctly.
Thanks a lof

This saved my new installation ;-) Thanks!

 

[iamrafkid]

Ok, can you try restarting the pveproxy and pvedaemon services

systemctl restart pveproxy.service pvedaemon.service

This worked for me. I have no idea how I borked it in the first place. I could SSH but could not access the web GUI. Did this and reloaded the web page (F5) and the web GUI was up again.

 

[SysAdminDev]

Hello everyone, I was looking for the solution to the problem. Well, the same thing happened to me but in this case I stopped and used the following address and started. I hope they help you with the problem. In the part underlined with yellow is the solution

 

[Pistolas]

I'm now facing a similar case.
Can't access the webui after a reboot.
Using 2 NIC, one access is connected to router enp4s0 and the second enp5s0 is only used to get to the webui 192.168.*.99/8006.
Sundenly stopped working.

Need some help. Please.

 

[Arech]

Hi, had the same connection issues despite the fact port 8006 was open and all services were running. The issue was because during Proxmox installation was conducted with WiFi netword card. I reinstalled Proxmox but changed to eth card and the connection problem is not a case anymore.

 

[leesteken]

Hi, had the same connection issues despite the fact port 8006 was open and all services were running. The issue was because during Proxmox installation was conducted with WiFi netword card. I reinstalled Proxmox but changed to eth card and the connection problem is not a case anymore.

Proxmox does not support WiFi (as it does not support a virtual bridge), but you set it up manually (but only with NAT) if you really want to: https://pve.proxmox.com/wiki/WLAN