No web GUI after apt upgrade

[aa1516]

I mistakenly did an apt update instead of apt dist-upgrade and now the web GUI doesn't work. Netstat shows port 8006 is in use, but I don't get anything when doing

curl -s -k https://localhost:8006 | grep title

or browsing from another computer.

pveversion -v:

proxmox-ve: 5.2-2 (running kernel: 4.15.18-5-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-8
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-2-pve: 4.15.18-21
pve-kernel-4.15.18-1-pve: 4.15.18-19
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.13.16-3-pve: 4.13.16-50
pve-kernel-4.13.16-2-pve: 4.13.16-48
pve-kernel-4.4.35-1-pve: 4.4.35-76
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-40
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-29
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-36
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve1~bpo1

 

[tschanness]

Did you do an apt-get dist-upgrade afterwards? Maybe try rebooting the host after the dist-upgrade..

 

[aa1516]

Did you do an apt-get dist-upgrade afterwards? Maybe try rebooting the host after the dist-upgrade..

I did try and rebooted, but there was no change. No packages updated either.

 

[dcsapak]

what does

systemctl status pveproxy pvedaemon

say?

 

[aa1516]

say?

systemctl status pveproxy pvedaemon
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2018-10-08 01:04:51 CDT; 9h ago
  Process: 21152 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
 Main PID: 8022 (pveproxy)
    Tasks: 4 (limit: 4915)
   Memory: 119.8M
      CPU: 4.355s
   CGroup: /system.slice/pveproxy.service
           ├─ 8022 pveproxy
           ├─21472 pveproxy worker
           ├─21473 pveproxy worker
           └─21474 pveproxy worker

Oct 08 06:25:04 hostname pveproxy[8022]: starting 3 worker(s)
Oct 08 06:25:04 hostname pveproxy[8022]: worker 21472 started
Oct 08 06:25:04 hostname pveproxy[8022]: worker 21473 started
Oct 08 06:25:04 hostname pveproxy[8022]: worker 21474 started
Oct 08 06:25:09 hostname pveproxy[8025]: worker exit
Oct 08 06:25:09 hostname pveproxy[8024]: worker exit
Oct 08 06:25:09 hostname pveproxy[8023]: worker exit
Oct 08 06:25:09 hostname pveproxy[8022]: worker 8023 finished
Oct 08 06:25:09 hostname pveproxy[8022]: worker 8024 finished
Oct 08 06:25:09 hostname pveproxy[8022]: worker 8025 finished

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2018-10-08 01:04:35 CDT; 9h ago
 Main PID: 7378 (pvedaemon)
    Tasks: 4 (limit: 4915)
   Memory: 129.5M
      CPU: 5.854s
   CGroup: /system.slice/pvedaemon.service
           ├─7378 pvedaemon
           ├─7381 pvedaemon worker
           ├─7382 pvedaemon worker
           └─7383 pvedaemon worker

Oct 08 01:04:34 hostname systemd[1]: Starting PVE API Daemon...
Oct 08 01:04:35 hostname pvedaemon[7378]: starting server
Oct 08 01:04:35 hostname pvedaemon[7378]: starting 3 worker(s)
Oct 08 01:04:35 hostname pvedaemon[7378]: worker 7381 started

 

[dcsapak]

seems the services are running. is the firewall enabled ?

 

[aa1516]

is the firewall enabled ?

I do have iptables enabled.

sudo iptables -S  | grep 8006
-A GROUP-proxmox-IN -p tcp -m tcp --dport 8006 -g PVEFW-SET-ACCEPT-MARK
-A PVEFW-HOST-IN -p tcp -m set --match-set PVEFW-0-management-v4 src -m tcp --dport 8006 -j RETURN
-A PVEFW-HOST-OUT -d {MY.IP.ADDY.HERE}/29 -p tcp -m tcp --dport 8006 -j RETURN

Here's what I get on lynx from a vm within:

lynx https://mydomain.com:8006

Looking up mydomain.com:8006
Making HTTPS connection to mydomain.com:8006
Alert!: Unable to make secure connection to remote host.

lynx: Can't access startfile https://mydomain.com:8006/