GUI stops working

P

pranit

Member
Oct 10, 2019
28
0
6
34
Hello team, i'm using proxmox version "pve-manager/6.3-2/22f57405 (running kernel: 5.4.73-1-pve)"
this particular node is standalone. not used in any cluster. i was able to get an access of GUI till yesterday but since today i am not getting GUI. NO changes were made till yesterday. Im not getting what issue has occurred without changing anything. didnt perform any updates also. kindly help to get GUI access back .
 

Attachments

  • proxmox gui.PNG
    proxmox gui.PNG
    97.1 KB · Views: 10
The only thing which i remember is i had made an extra entry in /etc/hosts. which i have undo now. but this doesnt work
 
Hi,
so you can login via ssh? What is the output of systemctl status pveproxy.service and cat /etc/default/pveproxy (if the file exists). Do you get the same error with other browsers? Please also check your firewall settings everywhere.
 
  • Like
Reactions: pranit
Fabian_E said:
Hi,
so you can login via ssh? What is the output of systemctl status pveproxy.service and cat /etc/default/pveproxy (if the file exists). Do you get the same error with other browsers? Please also check your firewall settings everywhere.
Click to expand...
hello sir,

pveproxy service is having some errors now. also there is no file as such " /etc/default/pveproxy"
here is the output of service.
systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset:
Active: failed (Result: exit-code) since Tue 2021-05-25 15:04:15 IST; 2 days
Process: 1281 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, s
Process: 1282 ExecStart=/usr/bin/pveproxy start (code=exited, status=255/EXCEP

May 25 15:04:15 nic2 systemd[1]: pveproxy.service: Service RestartSec=100ms expi
May 25 15:04:15 nic2 systemd[1]: pveproxy.service: Scheduled restart job, restar
May 25 15:04:15 nic2 systemd[1]: Stopped PVE API Proxy Server.
May 25 15:04:15 nic2 systemd[1]: pveproxy.service: Start request repeated too qu
May 25 15:04:15 nic2 systemd[1]: pveproxy.service: Failed with result 'exit-code
May 25 15:04:15 nic2 systemd[1]: Failed to start PVE API Proxy Server.
lines 1-12/12 (END)...skipping...
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-05-25 15:04:15 IST; 2 days ago
Process: 1281 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=111)
Process: 1282 ExecStart=/usr/bin/pveproxy start (code=exited, status=255/EXCEPTION)

May 25 15:04:15 nic2 systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
May 25 15:04:15 nic2 systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 10.
May 25 15:04:15 nic2 systemd[1]: Stopped PVE API Proxy Server.
May 25 15:04:15 nic2 systemd[1]: pveproxy.service: Start request repeated too quickly.
May 25 15:04:15 nic2 systemd[1]: pveproxy.service: Failed with result 'exit-code'.
May 25 15:04:15 nic2 systemd[1]: Failed to start PVE API Proxy Server.
 
Meaning that the service indeed failed. You can use journalctl -u pveproxy.service to get more of the log and hopefully find the cause.
 
  • Like
Reactions: pranit
Fabian_E said:
Meaning that the service indeed failed. You can use journalctl -u pveproxy.service to get more of the log and hopefully find the cause.
Click to expand...
As i Know i had changed /etc/host for adding entry of new ip and its hostname. afterwhich i encountered this problem. i undo those changes thereafter but issue still persists. Kindly Help

pls check the attached output of said command
 

Attachments

  • journelctl .png
    journelctl .png
    188.3 KB · Views: 4
Same problem here... i have a blank page!

systemctl status pveproxy.service
Code: 
root@servags-vm:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-05-31 09:24:55 -04; 19min ago
  Process: 6603 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 6614 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
 Main PID: 6615 (pveproxy)
    Tasks: 4 (limit: 4915)
   Memory: 162.3M
   CGroup: /system.slice/pveproxy.service
           ├─6615 pveproxy
           ├─6616 pveproxy worker
           ├─6617 pveproxy worker
           └─6618 pveproxy worker

May 31 09:24:54 servags-vm systemd[1]: Stopped PVE API Proxy Server.
May 31 09:24:54 servags-vm systemd[1]: Starting PVE API Proxy Server...
May 31 09:24:55 servags-vm pveproxy[6614]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
May 31 09:24:55 servags-vm pveproxy[6615]: starting server
May 31 09:24:55 servags-vm pveproxy[6615]: starting 3 worker(s)
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6616 started
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6617 started
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6618 started
May 31 09:24:55 servags-vm systemd[1]: Started PVE API Proxy Server.

journalctl -u pveproxy.service
Code: 
root@servags-vm:~# journalctl -u pveproxy.service
-- Logs begin at Mon 2021-05-31 09:07:25 -04, end at Mon 2021-05-31 09:41:00 -04. --
May 31 09:07:30 servags-vm systemd[1]: Starting PVE API Proxy Server...
May 31 09:07:31 servags-vm pveproxy[2406]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
May 31 09:07:31 servags-vm pveproxy[2413]: starting server
May 31 09:07:31 servags-vm pveproxy[2413]: starting 3 worker(s)
May 31 09:07:31 servags-vm pveproxy[2413]: worker 2414 started
May 31 09:07:31 servags-vm pveproxy[2413]: worker 2415 started
May 31 09:07:31 servags-vm pveproxy[2413]: worker 2416 started
May 31 09:07:31 servags-vm systemd[1]: Started PVE API Proxy Server.
May 31 09:23:25 servags-vm systemd[1]: Stopping PVE API Proxy Server...
May 31 09:23:26 servags-vm pveproxy[2413]: received signal TERM
May 31 09:23:26 servags-vm pveproxy[2413]: server closing
May 31 09:23:26 servags-vm pveproxy[2415]: worker exit
May 31 09:23:26 servags-vm pveproxy[2416]: worker exit
May 31 09:23:26 servags-vm pveproxy[2414]: worker exit
May 31 09:23:26 servags-vm pveproxy[2413]: worker 2414 finished
May 31 09:23:26 servags-vm pveproxy[2413]: worker 2415 finished
May 31 09:23:26 servags-vm pveproxy[2413]: worker 2416 finished
May 31 09:23:26 servags-vm pveproxy[2413]: server stopped
May 31 09:23:27 servags-vm systemd[1]: pveproxy.service: Succeeded.
May 31 09:23:27 servags-vm systemd[1]: Stopped PVE API Proxy Server.
May 31 09:23:27 servags-vm systemd[1]: Starting PVE API Proxy Server...
May 31 09:23:28 servags-vm pveproxy[449]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
May 31 09:23:28 servags-vm pveproxy[450]: starting server
May 31 09:23:28 servags-vm pveproxy[450]: starting 3 worker(s)
May 31 09:23:28 servags-vm pveproxy[450]: worker 451 started
May 31 09:23:28 servags-vm pveproxy[450]: worker 452 started
May 31 09:23:28 servags-vm pveproxy[450]: worker 453 started
May 31 09:23:28 servags-vm systemd[1]: Started PVE API Proxy Server.
May 31 09:24:53 servags-vm systemd[1]: Stopping PVE API Proxy Server...
May 31 09:24:53 servags-vm pveproxy[450]: received signal TERM
May 31 09:24:53 servags-vm pveproxy[450]: server closing
May 31 09:24:53 servags-vm pveproxy[453]: worker exit
May 31 09:24:53 servags-vm pveproxy[452]: worker exit
May 31 09:24:53 servags-vm pveproxy[451]: worker exit
May 31 09:24:53 servags-vm pveproxy[450]: worker 452 finished
May 31 09:24:53 servags-vm pveproxy[450]: worker 453 finished
May 31 09:24:53 servags-vm pveproxy[450]: worker 451 finished
May 31 09:24:53 servags-vm pveproxy[450]: server stopped
May 31 09:24:54 servags-vm systemd[1]: pveproxy.service: Succeeded.
May 31 09:24:54 servags-vm systemd[1]: Stopped PVE API Proxy Server.
May 31 09:24:54 servags-vm systemd[1]: Starting PVE API Proxy Server...
May 31 09:24:55 servags-vm pveproxy[6614]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
May 31 09:24:55 servags-vm pveproxy[6615]: starting server
May 31 09:24:55 servags-vm pveproxy[6615]: starting 3 worker(s)
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6616 started
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6617 started
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6618 started
May 31 09:24:55 servags-vm systemd[1]: Started PVE API Proxy Server.
 
Last edited:
pranit said:
As i Know i had changed /etc/host for adding entry of new ip and its hostname. afterwhich i encountered this problem. i undo those changes thereafter but issue still persists. Kindly Help
pls check the attached output of said command
Click to expand...
Could you share the content of /etc/hosts and /etc/hostname? It does seem like nic2 cannot be resolved, please ensure there is an entry for it.

What is the output of journalctl -u pve-cluster.service?


Hi,
pcready.cl said:
Same problem here... i have a blank page!

systemctl status pveproxy.service
Code: 
root@servags-vm:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-05-31 09:24:55 -04; 19min ago
  Process: 6603 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 6614 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
 Main PID: 6615 (pveproxy)
    Tasks: 4 (limit: 4915)
   Memory: 162.3M
   CGroup: /system.slice/pveproxy.service
           ├─6615 pveproxy
           ├─6616 pveproxy worker
           ├─6617 pveproxy worker
           └─6618 pveproxy worker

May 31 09:24:54 servags-vm systemd[1]: Stopped PVE API Proxy Server.
May 31 09:24:54 servags-vm systemd[1]: Starting PVE API Proxy Server...
May 31 09:24:55 servags-vm pveproxy[6614]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
May 31 09:24:55 servags-vm pveproxy[6615]: starting server
May 31 09:24:55 servags-vm pveproxy[6615]: starting 3 worker(s)
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6616 started
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6617 started
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6618 started
May 31 09:24:55 servags-vm systemd[1]: Started PVE API Proxy Server.

journalctl -u pveproxy.service
Code: 
root@servags-vm:~# journalctl -u pveproxy.service
-- Logs begin at Mon 2021-05-31 09:07:25 -04, end at Mon 2021-05-31 09:41:00 -04. --
May 31 09:07:30 servags-vm systemd[1]: Starting PVE API Proxy Server...
May 31 09:07:31 servags-vm pveproxy[2406]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
May 31 09:07:31 servags-vm pveproxy[2413]: starting server
May 31 09:07:31 servags-vm pveproxy[2413]: starting 3 worker(s)
May 31 09:07:31 servags-vm pveproxy[2413]: worker 2414 started
May 31 09:07:31 servags-vm pveproxy[2413]: worker 2415 started
May 31 09:07:31 servags-vm pveproxy[2413]: worker 2416 started
May 31 09:07:31 servags-vm systemd[1]: Started PVE API Proxy Server.
May 31 09:23:25 servags-vm systemd[1]: Stopping PVE API Proxy Server...
May 31 09:23:26 servags-vm pveproxy[2413]: received signal TERM
May 31 09:23:26 servags-vm pveproxy[2413]: server closing
May 31 09:23:26 servags-vm pveproxy[2415]: worker exit
May 31 09:23:26 servags-vm pveproxy[2416]: worker exit
May 31 09:23:26 servags-vm pveproxy[2414]: worker exit
May 31 09:23:26 servags-vm pveproxy[2413]: worker 2414 finished
May 31 09:23:26 servags-vm pveproxy[2413]: worker 2415 finished
May 31 09:23:26 servags-vm pveproxy[2413]: worker 2416 finished
May 31 09:23:26 servags-vm pveproxy[2413]: server stopped
May 31 09:23:27 servags-vm systemd[1]: pveproxy.service: Succeeded.
May 31 09:23:27 servags-vm systemd[1]: Stopped PVE API Proxy Server.
May 31 09:23:27 servags-vm systemd[1]: Starting PVE API Proxy Server...
May 31 09:23:28 servags-vm pveproxy[449]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
May 31 09:23:28 servags-vm pveproxy[450]: starting server
May 31 09:23:28 servags-vm pveproxy[450]: starting 3 worker(s)
May 31 09:23:28 servags-vm pveproxy[450]: worker 451 started
May 31 09:23:28 servags-vm pveproxy[450]: worker 452 started
May 31 09:23:28 servags-vm pveproxy[450]: worker 453 started
May 31 09:23:28 servags-vm systemd[1]: Started PVE API Proxy Server.
May 31 09:24:53 servags-vm systemd[1]: Stopping PVE API Proxy Server...
May 31 09:24:53 servags-vm pveproxy[450]: received signal TERM
May 31 09:24:53 servags-vm pveproxy[450]: server closing
May 31 09:24:53 servags-vm pveproxy[453]: worker exit
May 31 09:24:53 servags-vm pveproxy[452]: worker exit
May 31 09:24:53 servags-vm pveproxy[451]: worker exit
May 31 09:24:53 servags-vm pveproxy[450]: worker 452 finished
May 31 09:24:53 servags-vm pveproxy[450]: worker 453 finished
May 31 09:24:53 servags-vm pveproxy[450]: worker 451 finished
May 31 09:24:53 servags-vm pveproxy[450]: server stopped
May 31 09:24:54 servags-vm systemd[1]: pveproxy.service: Succeeded.
May 31 09:24:54 servags-vm systemd[1]: Stopped PVE API Proxy Server.
May 31 09:24:54 servags-vm systemd[1]: Starting PVE API Proxy Server...
May 31 09:24:55 servags-vm pveproxy[6614]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
May 31 09:24:55 servags-vm pveproxy[6615]: starting server
May 31 09:24:55 servags-vm pveproxy[6615]: starting 3 worker(s)
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6616 started
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6617 started
May 31 09:24:55 servags-vm pveproxy[6615]: worker 6618 started
May 31 09:24:55 servags-vm systemd[1]: Started PVE API Proxy Server.
Click to expand...
in your case there doesn't seem to be any problem with the service. Can you ping the host? Does using a different browser/clearing the browser cache help? Also check your firewall settings.
 
  • Like
Reactions: pranit
Fabian_E said:
Could you share the content of /etc/hosts and /etc/hostname? It does seem like nic2 cannot be resolved, please ensure there is an entry for it.

What is the output of journalctl -u pve-cluster.service?


Hi,

in your case there doesn't seem to be any problem with the service. Can you ping the host? Does using a different browser/clearing the browser cache help? Also check your firewall settings.
Click to expand...
I resolv my issue, check: https://forum.proxmox.com/threads/cant-access-proxmox-webgui.89396/page-2#post-394135

Thanks :)
 
Fabian_E said:
Could you share the content of /etc/hosts and /etc/hostname? It does seem like nic2 cannot be resolved, please ensure there is an entry for it.

What is the output of journalctl -u pve-cluster.service?


Hi,

in your case there doesn't seem to be any problem with the service. Can you ping the host? Does using a different browser/clearing the browser cache help? Also check your firewall settings.
Click to expand...
Thank you.. it has resolved now by adding entry in /etc/hosts.
 
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