Proxmox web UI does not start

atsy

New Member
Mar 30, 2024
1
0
1
Disclamer: I did read several thread on this subject but it didn't help. I think the problem is something very simple but I cannot get it.

Prehistory: I installed the proxmox ~5-6 month ago (it was working then), then didn't touch it during these months (turned off) and now moved to another network (IP changed) and trying to reanimate. I can access the machine by SSH. But the 4006 port is not open

ss -lnt4
State Recv-Q Send-Q Local AddressPort Peer AddressPort Process
LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
LISTEN 0 4096 0.0.0.0:111 0.0.0.0:*
LISTEN 0 4096 127.0.0.1:85 0.0.0.0:*
LISTEN 0 100 127.0.0.1:25 0.0.0.0:*

What could be the issue ?

1) As I understood the enterprise access has expired since 5 month so I switched to non-subscription repos, following more or less this: https://forum.proxmox.com/threads/proxmox-web-gui-problems.41391/


apt update and upgrade were successful, also `apt install pve-manager`

2) Hosts
cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.0.121 ha.local ha
3) ip a
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 8c:01:60:4c:31:b1 brd ff:ff:ff:ff:ff:ff
3: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 8c:01:60:4c:31:b2 brd ff:ff:ff:ff:ff:ff
4: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether c8:21:58:b2:e9:d1 brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 8c:01:60:4c:31:b1 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.121/24 brd 192.168.0.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::8e01:60ff:fe4c:31b1/64 scope link
valid_lft forever preferred_lft forever
4) interfaces (dhcp address is static for this machine)
cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface enp1s0 inet manual
auto vmbr0
iface vmbr0 inet dhcp
# static
# address 192.168.0.121/24
# gateway 192.168.0.1
bridge-ports enp1s0
bridge-stp off
bridge-fd 0
iface enp2s0 inet manual
iface wlp3s0 inet manual
5) systemctl
systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
Active: active (running) since Sat 2024-03-30 20:56:22 EET; 14min ago
Process: 838 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 872 (pvedaemon)
Tasks: 4 (limit: 18831)
Memory: 166.3M
CPU: 1.071s
CGroup: /system.slice/pvedaemon.service
├─872 pvedaemon
├─873 "pvedaemon worker"
├─874 "pvedaemon worker"
└─875 "pvedaemon worker"

Mar 30 20:56:21 ha systemd[1]: Starting pvedaemon.service - PVE API Daemon...
Mar 30 20:56:22 ha pvedaemon[872]: starting server
Mar 30 20:56:22 ha pvedaemon[872]: starting 3 worker(s)
Mar 30 20:56:22 ha pvedaemon[872]: worker 873 started
Mar 30 20:56:22 ha pvedaemon[872]: worker 874 started
Mar 30 20:56:22 ha pvedaemon[872]: worker 875 started
Mar 30 20:56:22 ha systemd[1]: Started pvedaemon.service - PVE API Daemon.

systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: active (running) since Sat 2024-03-30 20:56:23 EET; 15min ago
Process: 877 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUC>
Process: 879 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 881 (pveproxy)
Tasks: 4 (limit: 18831)
Memory: 151.4M
CPU: 1.270s
CGroup: /system.slice/pveproxy.service
├─881 pveproxy
├─882 "pveproxy worker"
├─883 "pveproxy worker"
└─884 "pveproxy worker"

Mar 30 20:56:22 ha systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Mar 30 20:56:23 ha pveproxy[881]: starting server
Mar 30 20:56:23 ha pveproxy[881]: starting 3 worker(s)
Mar 30 20:56:23 ha pveproxy[881]: worker 882 started
Mar 30 20:56:23 ha pveproxy[881]: worker 883 started
Mar 30 20:56:23 ha pveproxy[881]: worker 884 started
Mar 30 20:56:23 ha systemd[1]: Started pveproxy.service - PVE API Proxy Server.

6) journal
journalctl -f
Mar 30 20:57:54 ha systemd[1124]: Reached target basic.target - Basic System.
Mar 30 20:57:54 ha systemd[1124]: Reached target default.target - Main User Target.
Mar 30 20:57:54 ha systemd[1124]: Startup finished in 91ms.
Mar 30 20:57:54 ha systemd[1]: Started user@0.service - User Manager for UID 0.
Mar 30 20:57:54 ha systemd[1]: Started session-1.scope - Session 1 of User root.
Mar 30 20:57:54 ha sshd[1121]: pam_env(sshd:session): deprecated reading of user environment enabled
Mar 30 21:11:10 ha systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Mar 30 21:11:10 ha systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Mar 30 21:11:10 ha systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Mar 30 21:11:10 ha systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
 
Last edited:

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!

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!