Can't access Web-GUI

[Cesar da Silva]

Hi!
I am having problem accessing the Web-GUI on two of the Proxmox nodes from the browser running on the same network. I can ping them and connect to them using ssh from the the client.
I think this issue started after I upgraded from v5.2 to v5.3.

The browser (Firefox) gives me this message when I try to browse to the URL: https://192.168.1.92:8006/

Secure Connection Failed

The connection to 192.168.1.92:8006 was interrupted while the page was loading.

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.

Tried curl locally on the machine and got this output:

root@pve2:/var/log# curl -Lkvv https://192.168.1.92:8006
* Rebuilt URL to: https://192.168.1.92:8006/
* Trying 192.168.1.92...
* TCP_NODELAY set
* Connected to 192.168.1.92 (192.168.1.92) port 8006 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* Unknown SSL protocol error in connection to 192.168.1.92:8006
* Curl_http_done: called premature == 1
* stopped the pause stream!
* Closing connection 0
curl: (35) Unknown SSL protocol error in connection to 192.168.1.92:8006



root@pve2:/var/log# ss -ntpl | grep 8006
LISTEN 0 128 0.0.0.0:8006 0.0.0.0:* users("pveproxy worker",pid=2413,fd=6),("pveproxy worker",pid=2412,fd=6),("pveproxy worker",pid=2411,fd=6),("pveproxy",pid=2407,fd=6))

root@pve2:/var/log# pveversion -v
proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.3-6 (running version: 5.3-6/37b3c8df)
pve-kernel-4.15: 5.2-12
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-4-pve: 4.15.18-23
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.15.17-2-pve: 4.15.17-10
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.15.15-1-pve: 4.15.15-6
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-2-pve: 4.13.13-33
ceph: 12.2.10-pve1
corosync: 2.4.4-pve1
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.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-43
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-34
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-5
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
openvswitch-switch: 2.7.0-3
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-31
pve-container: 2.0-31
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-16
pve-firmware: 2.0-6
pve-ha-manager: 2.0-5
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-43
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1


Any suggestions on how to fix this?

 

[Richard]

Hi!
I am having problem accessing the Web-GUI on two of the Proxmox nodes from the browser running on the same network. I can ping them and connect to them using ssh from the the client.
I think this issue started after I upgraded from v5.2 to v5.3.

The browser (Firefox) gives me this message when I try to browse to the URL: https://192.168.1.92:8006/

Secure Connection Failed

The connection to 192.168.1.92:8006 was interrupted while the page was loading.

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.

Follow the steps described here: https://pve.proxmox.com/wiki/HTTPS_..._5.0_and_5.1)#Revert_to_default_configuration

and restart pveproxy service.

 

[Cesar da Silva]

Thanks.
It fixed the issue.

 

[Stoiko Ivanov]

This page does not work 10.0.0.254 has not sent any data.
ERR_EMPTY_RESPONSE

That's usually the error when connecting to http instead of https