(another) Can't access GUI thread

[dirkdiggler]

Am trying at https://[Proxmox IP]:8006 via microsoft edge. Returns ERR_CONNECTION_TIMED_OUT.

Things that work:

Ping from [Windows PC] to [Proxmox Host]
Ping from [Proxmox Host] to [Windows PC]
SSH from [Windows PC] to [Proxmox Host]

Things I've tried:

apt update
apt full-upgrade

Output: All packages are up to date // 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

apt install --reinstall pve-manager

netstat -an | grep 8006
tcp        0      0 0.0.0.0:8006            0.0.0.0:*               LISTEN

root@pve:/etc/pve/local# tcpdump -i vmbr0 port 8006
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmbr0, link-type EN10MB (Ethernet), capture size 262144 bytes
17:37:16.867399 IP [WIN IP].63271 > [PVE FQDN].8006: Flags [S], seq 878057993, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
17:37:17.134793 IP [WIN IP].63272 > [PVE FQDN].8006: Flags [S], seq 3457441265, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
17:37:17.868052 IP [WIN IP].63271 > [PVE FQDN].8006: Flags [S], seq 878057993, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
17:37:18.136763 IP [WIN IP].63272 > [PVE FQDN].8006: Flags [S], seq 3457441265, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0

The messages appear after trying to load the webgui.

 

[dirkdiggler]

root@pve:/etc/pve/local# curl -s -k https://localhost:8006 | grep title
    <title>pve - Proxmox Virtual Environment</title>

This means the webgui is active I assume? So could it be a firewall blocking access?

 

[Stoiko Ivanov]

do you have a firewall enabled (e.g. the PVE built-in firewall)?
what's the output of `iptables-save` ?

 

[dirkdiggler]

root@pve:/etc/pve/nodes/pve# iptables-save
# Generated by iptables-save v1.8.2 on Mon Feb  8 18:00:32 2021
*raw
:PREROUTING ACCEPT [11124:14741309]
:OUTPUT ACCEPT [6346:2798784]
COMMIT
# Completed on Mon Feb  8 18:00:32 2021
# Generated by iptables-save v1.8.2 on Mon Feb  8 18:00:32 2021
*filter
:INPUT ACCEPT [9224:14488269]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [6342:2798496]
:f2b-proxmox - [0:0]
-A INPUT -p tcp -m multiport --dports 443,80,8006 -j f2b-proxmox
-A f2b-proxmox -s [WIN IP]/32 -j REJECT --reject-with icmp-port-unreachable
-A f2b-proxmox -j RETURN
COMMIT
# Completed on Mon Feb  8 18:00:32 2021

Ahhh - looks like the IP was banned by F2B recently. Thanks!

 

[Stoiko Ivanov]

Glad you found the issue! - Please mark the thread as SOLVED, as this helps other users with similar problems.

Thanks!