[SOLVED] Proxmox Web Interface gone!

MaiaInternet

New Member
Jan 18, 2017
2
0
1
54
Hi all,

thanks for making proxmox - a great piece of kit - and mine has been working flawlessly for a year now.

Today, however, I tried to access the web gui with no joy: ERR_CONNECTION_TIMED_OUT

My setup:

Proxmox 4 (updated today) with 3 VMs running (on OVH dedicated server)
Additionally I have Directadmin (Apache,bind,exim and other things) installed to have a webhost.

Everything is working as expected but I now get the error for the web GUI.

If I port forward 8006 to my local machine via ssh; https://localhost:8006 works as advertised.

My IP address isn't in the iptables list and the same happens across different devices/browsers.

Any help would be greatly appreciated!

Cheers,

Dave

Here's some useful info:

Code:
tail -f /var/log/pveproxy/access.log
gives nothing except the curl request
Code:
netstat -an | grep 8006
tcp        0      0 0.0.0.0:8006            0.0.0.0:*               LISTEN
Code:
curl -s -k https://localhost:8006 | grep title
    <title>imogen - Proxmox Virtual Environment</title>
Code:
pvesh get nodes
200 OK
[
   {
      "cpu" : 0.0170197380744173,
      "disk" : 10894462976,
      "id" : "node/imogen",
      "level" : "",
      "maxcpu" : 8,
      "maxdisk" : 20506800128,
      "maxmem" : 16816005120,
      "mem" : 6972829696,
      "node" : "imogen",
      "type" : "node",
      "uptime" : 11067
   }
]
Code:
pve-firewall status
Status: disabled/running
Code:
uname -r
4.4.98-5-pve
Code:
dpkg -l | grep pve
ii  corosync-pve                   2.4.2-2~pve4+1                     amd64        Standards-based cluster framework (daemon and modules)
ii  dmeventd                       2:1.02.93-pve3                     amd64        Linux Kernel Device Mapper event daemon
ii  dmsetup                        2:1.02.93-pve3                     amd64        Linux Kernel Device Mapper userspace library
ii  grub-common                    2.02-pve5                          amd64        GRand Unified Bootloader (common files)
ii  grub-pc                        2.02-pve5                          amd64        GRand Unified Bootloader, version 2 (PC/BIOS version)
ii  grub-pc-bin                    2.02-pve5                          amd64        GRand Unified Bootloader, version 2 (PC/BIOS binaries)
ii  grub2-common                   2.02-pve5                          amd64        GRand Unified Bootloader (common files for version 2)
ii  libcorosync4-pve               2.4.2-2~pve4+1                     amd64        Standards-based cluster framework (libraries)
ii  libdevmapper-event1.02.1:amd64 2:1.02.93-pve3                     amd64        Linux Kernel Device Mapper event support library
ii  libdevmapper1.02.1:amd64       2:1.02.93-pve3                     amd64        Linux Kernel Device Mapper userspace library
ii  liblvm2app2.2:amd64            2.02.116-pve3                      amd64        LVM2 application library
ii  liblvm2cmd2.02:amd64           2.02.116-pve3                      amd64        LVM2 command library
ii  libpve-access-control          4.0-23                             amd64        Proxmox VE access control library
ii  libpve-common-perl             4.0-96                             all          Proxmox VE base library
ii  libpve-guest-common-perl       1.0-2                              all          Proxmox VE common guest-related modules
ii  libpve-http-server-perl        1.0-4                              all          Proxmox Asynchrounous HTTP Server Implementation
ii  libpve-storage-perl            4.0-76                             all          Proxmox VE storage management library
ii  lvm2                           2.02.116-pve3                      amd64        Linux Logical Volume Manager
ii  lxc-pve                        2.0.7-4                            amd64        Linux containers usersapce tools
ii  lxcfs                          2.0.6-pve1                         amd64        LXC userspace filesystem
ii  novnc-pve                      0.5-9                              amd64        HTML5 VNC client
ii  pve-cluster                    4.0-54                             amd64        Cluster Infrastructure for Proxmox Virtual Environment
ii  pve-container                  1.0-104                            all          Proxmox VE Container management tool
ii  pve-docs                       4.4-4                              all          Proxmox VE Documentation
ii  pve-firewall                   2.0-33                             amd64        Proxmox VE Firewall
ii  pve-firmware                   1.1-11                             all          Binary firmware code for the pve-kernel
ii  pve-ha-manager                 1.0-41                             amd64        Proxmox VE HA Manager
ii  pve-kernel-4.4.35-1-pve        4.4.35-77                          amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.35-2-pve        4.4.35-79                          amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.44-1-pve        4.4.44-84                          amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.59-1-pve        4.4.59-87                          amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.62-1-pve        4.4.62-88                          amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.67-1-pve        4.4.67-92                          amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.76-1-pve        4.4.76-94                          amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.79-1-pve        4.4.79-95                          amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.83-1-pve        4.4.83-96                          amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.98-3-pve        4.4.98-103                         amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-4.4.98-5-pve        4.4.98-105                         amd64        The Proxmox PVE Kernel Image
ii  pve-libspice-server1           0.12.8-2                           amd64        SPICE remote display system server library
ii  pve-manager                    4.4-22                             amd64        The Proxmox Virtual Environment
ii  pve-qemu-kvm                   2.9.1-6~pve4                       amd64        Full virtualization on x86 hardware
ii  smartmontools                  6.5+svn4324-1~pve80                amd64        control and monitor storage systems using S.M.A.R.T.
ii  tar                            1.27.1+pve.3                       amd64        GNU version of the tar archiving utility
Code:
pveversion -v
proxmox-ve: 4.4-105 (running kernel: 4.4.98-5-pve)
pve-manager: 4.4-22 (running version: 4.4-22/2728f613)
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.79-1-pve: 4.4.79-95
pve-kernel-4.4.98-3-pve: 4.4.98-103
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.4.59-1-pve: 4.4.59-87
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.98-5-pve: 4.4.98-105
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.62-1-pve: 4.4.62-88
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-54
qemu-server: 4.0-115
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-6~pve4
pve-container: 1.0-104
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
 
aaaaand after all that it was indeed a firewall problem!

Although there was no entry in the iptables list, the firewall had started (for an unknown reason) blocking 8006.

After a little digging I found that it was the firewall despite nmap saying the port was open/filtered, the firewall was still blocking access.

Thanks for reading - I've learned to check firewall configs a little more closely!

Cheers!
 
how to fix this problem, i not receive anything after command that line

* Check if the pveproxy and pvedaemon services are running (systemctl status service_name)
* Check if you have a firewall enabled on your PVE host and if it's blocking the port
* Check the output of `netstat -antlp` and `ss -l`