Hello,
I have Proxmox 6.1 running with a few VMs and a NextCloud container. I can access the NextCloud portal but not the gui for Proxmox. I am able to access the gui for Proxmox if I go to the web address from inside a virtual machine running on the same computer that cannot connect. Here are some details I pulled hoping someone might be able to shed some light.
#cat /etc/apt/sources.list
deb http://download.proxmox.com/debian buster pve-no-subscription
deb http://ftp.us.debian.org/debian buster main contrib
deb http://ftp.us.debian.org/debian buster-updates main contrib
#security updates
deb http://security.debian.org buster/updates main contrib
#cat /etc/apt/sources.list.d/pve-enterprise.list
#deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
I have ran apt update and apt dist-upgrade with no errors and all packages up to date. I have tried turning the firewall off and on.
Running the command systemctl status 'pve*':
All active (running)
I see one error listed in pvenetcommit.service:
Process: 982 ExecStartPre=/bin/mv /etc/network/interaces.new /etc/network/interfaces (code=exited, status=1/FAILURE)
I have ran systemctl restart pveproxy.service with no change.
Here are the results from journalctl -u pveproxy and ss -tlpn
journalctl -u pveproxy
systemd[1]: Starting PVE API Proxy Server...
pveproxy[1417]: starting server
pveproxy[1417]: starting 3 worker(s)
pveproxy[1417]: worker 1418 started
pveproxy[1417]: worker 1419 started
pveproxy[1417]: worker 1420 started
systemd[1]: Started PVE API Proxy Server.
systemd[1]: Stopping PVE API Proxy Server...
pveproxy[1417]: received signal TERM
pveproxy[1417]: server closing
pveproxy[1419]: worker exit
pveproxy[1417]: worker 1418 finished
pveproxy[1417]: worker 1419 finished
pveproxy[1417]: worker 1420 finished
pveproxy[1417]: server stopped
pveproxy[2026]: worker exit
systemd[1]: pveproxy.service: Succeeded.
systemd[1]: Stopped PVE API Proxy Server.
systemd[1]: Starting PVE API Proxy Server...
pveproxy[2035]: starting server
pveproxy[2035]: starting 3 worker(s)
pveproxy[2035]: worker 2036 started
pveproxy[2035]: worker 2037 started
pveproxy[2035]: worker 2038 started
systemd[1]: Started PVE API Proxy Server.
pveproxy[2036]: worker exit
pveproxy[2035]: worker 2036 finished
pveproxy[2035]: starting 1 worker(s)
pveproxy[2035]: worker 7398 started
# ss -tlpm
State Recv-Q Send-Q Local Address: Port Peer Address: Port
LISTEN 0 128 0.0.0.0:8006 0.0.0.0:* users: (("pveproxy worker",pid=7398,fd=6),("pveproxy worker",pid=2038,fd=6),("pveproxy worker",pid=2037,fd=6),("pveproxy",pid=2035,fd=6))
skmem: (r0,rb131072,t0,tb16384,f0,w0,o0,bl0,d0)
I have Proxmox 6.1 running with a few VMs and a NextCloud container. I can access the NextCloud portal but not the gui for Proxmox. I am able to access the gui for Proxmox if I go to the web address from inside a virtual machine running on the same computer that cannot connect. Here are some details I pulled hoping someone might be able to shed some light.
#cat /etc/apt/sources.list
deb http://download.proxmox.com/debian buster pve-no-subscription
deb http://ftp.us.debian.org/debian buster main contrib
deb http://ftp.us.debian.org/debian buster-updates main contrib
#security updates
deb http://security.debian.org buster/updates main contrib
#cat /etc/apt/sources.list.d/pve-enterprise.list
#deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
I have ran apt update and apt dist-upgrade with no errors and all packages up to date. I have tried turning the firewall off and on.
Running the command systemctl status 'pve*':
All active (running)
I see one error listed in pvenetcommit.service:
Process: 982 ExecStartPre=/bin/mv /etc/network/interaces.new /etc/network/interfaces (code=exited, status=1/FAILURE)
I have ran systemctl restart pveproxy.service with no change.
Here are the results from journalctl -u pveproxy and ss -tlpn
journalctl -u pveproxy
systemd[1]: Starting PVE API Proxy Server...
pveproxy[1417]: starting server
pveproxy[1417]: starting 3 worker(s)
pveproxy[1417]: worker 1418 started
pveproxy[1417]: worker 1419 started
pveproxy[1417]: worker 1420 started
systemd[1]: Started PVE API Proxy Server.
systemd[1]: Stopping PVE API Proxy Server...
pveproxy[1417]: received signal TERM
pveproxy[1417]: server closing
pveproxy[1419]: worker exit
pveproxy[1417]: worker 1418 finished
pveproxy[1417]: worker 1419 finished
pveproxy[1417]: worker 1420 finished
pveproxy[1417]: server stopped
pveproxy[2026]: worker exit
systemd[1]: pveproxy.service: Succeeded.
systemd[1]: Stopped PVE API Proxy Server.
systemd[1]: Starting PVE API Proxy Server...
pveproxy[2035]: starting server
pveproxy[2035]: starting 3 worker(s)
pveproxy[2035]: worker 2036 started
pveproxy[2035]: worker 2037 started
pveproxy[2035]: worker 2038 started
systemd[1]: Started PVE API Proxy Server.
pveproxy[2036]: worker exit
pveproxy[2035]: worker 2036 finished
pveproxy[2035]: starting 1 worker(s)
pveproxy[2035]: worker 7398 started
# ss -tlpm
State Recv-Q Send-Q Local Address: Port Peer Address: Port
LISTEN 0 128 0.0.0.0:8006 0.0.0.0:* users: (("pveproxy worker",pid=7398,fd=6),("pveproxy worker",pid=2038,fd=6),("pveproxy worker",pid=2037,fd=6),("pveproxy",pid=2035,fd=6))
skmem: (r0,rb131072,t0,tb16384,f0,w0,o0,bl0,d0)
