[SOLVED] Cannot access WEB GUI

E

Exio

Member
Mar 30, 2022
55
8
13
Hi,

I did an update of my server and after the reboot, cannot access the web gui.
I tried to restart the pveproxy service and the log shows “permission denied” and i did a chmod 777 /var/log/pveproxy/access.log command…
Also i tried to do apt install proxmox-ve

Nothing works...

Some ideas? I'm desperate

Thanks
 
Hi,

Exio said:
I tried to restart the pveproxy service and the log shows “permission denied”
Click to expand...
What user did you run the command as? Could you post the output of:
  • pveversion -v
  • systemctl status pveproxy
  • systemctl status pvedaemon
Can the server still be accessed via SSH?

Exio said:
did a chmod 777 /var/log/pveproxy/access.log command
Click to expand...
I would change this back to '640', as it shouldn't have anything to do with the issue.

Best regards,
Dylan
 
  • Like
Reactions: lucidperplexity and Spirog
dylanw said:
Hi,


What user did you run the command as? Could you post the output of:
Click to expand...
I perform all the commands as root user
dylanw said:
  • pveversion -v
Click to expand...
Code: 
proxmox-ve: 7.1-1 (running kernel: 5.13.19-6-pve)
pve-manager: 7.1-11 (running version: 7.1-11/8d529482)
pve-kernel-helper: 7.1-13
pve-kernel-5.13: 7.1-9
pve-kernel-5.13.19-6-pve: 5.13.19-14
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph: 16.2.7
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-5
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-7
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-6
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
dylanw said:
  • systemctl status pveproxy
Click to expand...
Code: 
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-03-31 09:08:56 CEST; 23min ago
    Process: 1539 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1541 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 1544 (pveproxy)
      Tasks: 4 (limit: 77160)
     Memory: 132.2M
        CPU: 1min 33.809s
     CGroup: /system.slice/pveproxy.service
             ├─1544 pveproxy
             ├─7597 pveproxy worker
             ├─7598 pveproxy worker
             └─7600 pveproxy worker

Mar 31 09:32:37 proxmox pveproxy[7597]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Mar 31 09:32:37 proxmox pveproxy[7566]: worker exit
Mar 31 09:32:37 proxmox pveproxy[1544]: worker 7566 finished
Mar 31 09:32:37 proxmox pveproxy[1544]: starting 1 worker(s)
Mar 31 09:32:37 proxmox pveproxy[1544]: worker 7598 started
Mar 31 09:32:37 proxmox pveproxy[7598]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Mar 31 09:32:37 proxmox pveproxy[7568]: worker exit
Mar 31 09:32:37 proxmox pveproxy[1544]: worker 7568 finished
Mar 31 09:32:37 proxmox pveproxy[1544]: starting 1 worker(s)
Mar 31 09:32:37 proxmox pveproxy[1544]: worker 7600 started
dylanw said:
  • systemctl status pvedaemon
Click to expand...
Code: 
● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-03-31 09:08:54 CEST; 25min ago
    Process: 1415 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
   Main PID: 1534 (pvedaemon)
      Tasks: 4 (limit: 77160)
     Memory: 139.0M
        CPU: 2.174s
     CGroup: /system.slice/pvedaemon.service
             ├─1534 pvedaemon
             ├─1535 pvedaemon worker
             ├─1536 pvedaemon worker
             └─1537 pvedaemon worker

Mar 31 09:08:52 proxmox systemd[1]: Starting PVE API Daemon...
Mar 31 09:08:54 proxmox pvedaemon[1534]: starting server
Mar 31 09:08:54 proxmox pvedaemon[1534]: starting 3 worker(s)
Mar 31 09:08:54 proxmox pvedaemon[1534]: worker 1535 started
Mar 31 09:08:54 proxmox pvedaemon[1534]: worker 1536 started
Mar 31 09:08:54 proxmox pvedaemon[1534]: worker 1537 started
Mar 31 09:08:54 proxmox systemd[1]: Started PVE API Daemon.
dylanw said:
Can the server still be accessed via SSH?
Click to expand...
yes, i can access the server via SSH:
Code: 
C:\Users\exio0>ssh root@192.168.1.116
The authenticity of host '192.168.1.116 (192.168.1.116)' can't be established.
ECDSA key fingerprint is SHA256:---------------------.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.1.116' (ECDSA) to the list of known hosts.
root@192.168.1.116's password:
Linux proxmox 5.13.19-6-pve #1 SMP PVE 5.13.19-14 (Thu, 10 Mar 2022 16:24:52 +0100) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Mar 31 09:09:49 2022
root@proxmox:~#
dylanw said:
I would change this back to '640', as it shouldn't have anything to do with the issue.
Click to expand...
Ok, done..
dylanw said:
Best regards,
Dylan
Click to expand...

If you want more information please, dont doubt in ask to me... Thanks for your reply

Regards
 
Could you also post the output of?
  • ls -ld /var/log/pveproxy
  • ls -l /var/log/pveproxy
Additionally, what version did you upgrade from?
 
Last edited:
  • Like
Reactions: Spirog
dylanw said:
Could you also post the output of?
  • ls -ld /var/log/pveproxy
Click to expand...
Code: 
drw-r----- 2 777 root 4096 Mar 31 00:01 /var/log/pveproxy
dylanw said:
  • ls -l /var/log/pveproxy
Click to expand...
Code: 
total 4
-rw-r----- 1 www-data www-data 0 Mar 31 00:01 access.log
-rwxrwxrwx 1 root     root     2 Mar 30 19:58 access.log.1

That access.log.1 was created by me and access.log doesnt contain anything.
dylanw said:
Additionally, what version did you upgrade from?
Click to expand...
I update some packages, i dont know which ones. Just did an update from Web Gui and then, and dont know how, i accidentally did rm -r /var/log [facepalm] Sorry for not mentioning this on the beginning of the post.
 
Last edited:
Exio said:
Just did an update from Web Gui and then
Click to expand...
Okay, if it was an update from the GUI, it was likely a minor update anyway.

Exio said:
i accidentally did rm -r /var/log [facepalm] Sorry for not mentioning this on the beginning of the post.
Click to expand...
Ah, this explains it ;)
The directory /var/log/pveproxy and its contents should be owned by 'www-data'. Can you run the following command to see if it fixes the issue?
chown -R www-data:www-data /var/log/pveproxy
 
  • Like
Reactions: IconDon and Spirog
dylanw said:
Okay, if it was an update from the GUI, it was likely a minor update anyway.


Ah, this explains it ;)
The directory /var/log/pveproxy and its contents should be owned by 'www-data'. Can you run the following command to see if it fixes the issue?
chown -R www-data:www-data /var/log/pveproxy
Click to expand...
Code: 
root@proxmox:~# sudo chown -R www-data:www-data /var/log/pveproxy
root@proxmox:~# systemctl restart pveproxy
root@proxmox:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-03-31 11:30:05 CEST; 6s ago
    Process: 7211 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 7214 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 7243 (pveproxy)
      Tasks: 4 (limit: 77160)
     Memory: 131.9M
        CPU: 2.481s
     CGroup: /system.slice/pveproxy.service
             ├─7243 pveproxy
             ├─7248 pveproxy worker
             ├─7249 pveproxy worker
             └─7250 pveproxy worker

Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7245 finished
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7244 finished
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7246 finished
Mar 31 11:30:10 proxmox pveproxy[7243]: starting 3 worker(s)
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7248 started
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7249 started
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7250 started
Mar 31 11:30:10 proxmox pveproxy[7248]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Mar 31 11:30:10 proxmox pveproxy[7249]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Mar 31 11:30:10 proxmox pveproxy[7250]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied

Code: 
root@proxmox:~# ls -l /var/log/pveproxy
total 4
-rw-r----- 1 www-data www-data 0 Mar 31 00:01 access.log
-rwxrwxrwx 1 www-data www-data 2 Mar 30 19:58 access.log.1

Hmm seems like not fixed... Should i reboot the server?
 
  • Like
Reactions: krysus
Exio said:
Code: 
root@proxmox:~# sudo chown -R www-data:www-data /var/log/pveproxy
root@proxmox:~# systemctl restart pveproxy
root@proxmox:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-03-31 11:30:05 CEST; 6s ago
    Process: 7211 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 7214 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 7243 (pveproxy)
      Tasks: 4 (limit: 77160)
     Memory: 131.9M
        CPU: 2.481s
     CGroup: /system.slice/pveproxy.service
             ├─7243 pveproxy
             ├─7248 pveproxy worker
             ├─7249 pveproxy worker
             └─7250 pveproxy worker

Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7245 finished
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7244 finished
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7246 finished
Mar 31 11:30:10 proxmox pveproxy[7243]: starting 3 worker(s)
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7248 started
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7249 started
Mar 31 11:30:10 proxmox pveproxy[7243]: worker 7250 started
Mar 31 11:30:10 proxmox pveproxy[7248]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Mar 31 11:30:10 proxmox pveproxy[7249]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Mar 31 11:30:10 proxmox pveproxy[7250]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied

Code: 
root@proxmox:~# ls -l /var/log/pveproxy
total 4
-rw-r----- 1 www-data www-data 0 Mar 31 00:01 access.log
-rwxrwxrwx 1 www-data www-data 2 Mar 30 19:58 access.log.1

Hmm seems like not fixed... Should i reboot the server?
Click to expand...

run this command again
Code: 
ls -ld /var/log/pveproxy

I think the permissions are wrong here\\

mine looks like this
Code: 
root@proxmox:~# ls -ld /var/log/pveproxy
drwx------ 2 www-data www-data 4096 Mar 31 03:44 /var/log/pveproxy
root@proxmox:~# ls -l /var/log/pveproxy
total 3224
-rw-r----- 1 www-data www-data 1152964 Mar 31 04:49 access.log
-rw-r----- 1 www-data www-data 1507947 Mar 30 23:51 access.log.1
 
Last edited:
  • Like
Reactions: krysus
Spirog said:
run this command again
Code: 
ls -ld /var/log/pveproxy

I think the permissions are wrong here
Click to expand...
ls -ld /var/log/pveproxy -> drw-r----- 2 www-data www-data 4096 Mar 31 00:01 /var/log/pveproxy

Should i run chmod 640 /var/log/pveproxy ?
 
Spirog said:
chmod 640 /var/log/pveproxy/access.log
Click to expand...
Done...
Code: 
root@proxmox:~# chmod 640 /var/log/pveproxy/access.log
root@proxmox:~# sudo chmod 640 /var/log/pveproxy/
root@proxmox:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-03-31 11:55:22 CEST; 12min ago
    Process: 12872 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 12874 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 12876 (pveproxy)
      Tasks: 4 (limit: 77160)
     Memory: 131.7M
        CPU: 51.783s
     CGroup: /system.slice/pveproxy.service
             ├─12876 pveproxy
             ├─15721 pveproxy worker
             ├─15727 pveproxy worker
             └─15728 pveproxy worker

Mar 31 12:08:04 proxmox pveproxy[15721]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Mar 31 12:08:04 proxmox pveproxy[15711]: worker exit
Mar 31 12:08:04 proxmox pveproxy[15712]: worker exit
Mar 31 12:08:04 proxmox pveproxy[12876]: worker 15711 finished
Mar 31 12:08:04 proxmox pveproxy[12876]: worker 15712 finished
Mar 31 12:08:04 proxmox pveproxy[12876]: starting 2 worker(s)
Mar 31 12:08:04 proxmox pveproxy[12876]: worker 15727 started
Mar 31 12:08:04 proxmox pveproxy[12876]: worker 15728 started
Mar 31 12:08:04 proxmox pveproxy[15727]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Mar 31 12:08:04 proxmox pveproxy[15728]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
root@proxmox:~#
 
I have a question, can i access a VM without having access to the web gui? how?
 
Spirog said:
then after change permission to 700

run
Code: 
systemctl status pveproxy
Click to expand...
SOLVED. Omg thanks a lot Spirog. Love uo_O
I can login into the web GUI now.

I will mark post title as Solved, hope this will be helpful for someone in the future.

Again, THANKS.

And thanks for Dylan too!!!
 
Last edited:
  • Like
Reactions: fgordilloz, dylanw and Spirog
I had the same problem today with the exact same error.
The solution was the same for me.

Can anyone tell me how this can happen and why it happens?

The only thing I see right now is that Proxmox on this host is still on version 7.4-18 (I should really update this host)

For me the folder `/var/log/pveproxy` was non-existent and I don't understand how this could happen.

Anyway, thank you all!
I love this forum.
Thank you.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back