Access to the web panel was lost

[Walery]

I am trying to set up a test server. There was a problem. After installing and updating Proxmox VE 6.3, access to the web panel was lost. I made a ping to the server - ok, I made a ping from the server - ok.
After that, I ran the command
service pveproxy restart
access to the web panel appeared.
After restarting the server, there is no access to the web panel again
command
service pveproxy restart
Does not help.
p.s.
I also do not have an ssh connection.

 

[Dominic]

I also do not have an ssh connection.

If not even SSH works then I wouldn't expect the web interface to come up. Generally, looking at /var/log/syslog is a good idea.

After installing and updating Proxmox VE 6.3, access to the web panel was lost.

So you installed and it worked and updated some time later and then it didn't work anymore?

 

[Walery]

If not even SSH works then I wouldn't expect the web interface to come up. Generally, looking at /var/log/syslog is a good idea.


So you installed and it worked and updated some time later and then it didn't work anymore?

1 i installed Proxmox VE 6.3 it worked.
2 I updated PVE 6.3, rebooted and access to the Web GUI was lost
3 I executed the command
service pveproxy restart
web GUI is working
4 I rebooted PVE 6.3 again and now the web gui does not work (but ping from server and to server works)

 

[Dominic]

(but ping from server and to server works)

And stuff like ssh?

Is there something interesting in

journalctl -u pvedaemon
journalctl -u pveproxy

?

 

[Walery]

And stuff like ssh?

Is there something interesting in

journalctl -u pvedaemon
journalctl -u pveproxy

?

ping works. ssh is not.

journalctl -u pvedaemon
pve2 systemd(1): Starting PVE API Daemon...
pve2 pvedaemon (1012): starting server
pve2 pvedaemon (1012): starting 3 worker(s)
pve2 pvedaemon (1012): worker 1013 started
pve2 pvedaemon (1012): worker 1014 started
pve2 pvedaemon (1012): worker 1015 started
pve2 systemd(1): Started PVE API Daemon...

journalctl -u pveproxy
pve2 systemd(1): Starting PVE API Proxy Server...
pve2 pveproxy (1021): starting server
pve2 pveproxy (1021): starting 3 worker(s)
pve2 pveproxy (1021): worker 1022 started
pve2 pveproxy (1021): worker 1023 started
pve2 pveproxy (1021): worker 1024 started
pve2 systemd(1): Started PVE API Proxy Server.
pve2 systemd(1): Stopping PVE API Proxy Server...
pve2 pveproxy (1021): received signal TERM
pve2 pveproxy (1021): server closing
pve2 pveproxy (1024): worker exit
pve2 pveproxy (1023): worker exit
pve2 pveproxy (1022): worker exit
pve2 pveproxy (1021): worker 1022 finished
pve2 pveproxy (1021): worker 1023 finished
pve2 pveproxy (1021): worker 1024 finished
pve2 pveproxy (1021): server stopped
pve2 systemd(1): pveproxy.service: Succeeded.
pve2 systemd(1): Stopped PVE API Proxy Server.
pve2 systemd(1): Starting PVE API Proxy Server...
pve2 pveproxy (1882): starting server
pve2 pveproxy (1882): starting 3 worker(s)
pve2 pveproxy (1882): worker 1883 started
pve2 pveproxy (1882): worker 1884 started
pve2 pveproxy (1882): worker 1885 started
pve2 systemd(1): Started PVE API Proxy Server.

 

[Walery]

Any ideas?

 

[Dominic]

The journal entries look OK.

Please try ssh with multiple -v options, like

ssh -vv <destionation>

and also to get the Proxmox VE web interface via command line for an exact error

curl -k https://localhost:8006