WebUI reachable via Safari, but not via Chrome

[24unix]

Hi Forum I'm new to this Forum and to Proxmox.

I used to have a server@home with some KVM-VM for a NAS (OMV) and some Debian VM for development.
That machine's power supply died twice within a year, and as it was old, loud and power consuming I decided not to repair it again.
But it turned out NextCloud is no good replacement for a NAS, so I built a new one with a leftover Mac mini.

It has only 8GB RAM, but that's enough, we are only two users in the net.

I attached two TB enclosures, one has a ZFS mirror for the system and a ZFS mirror for VM.
The second holds 4 SSD which per PCI-passthrough go to the OMV-VM, which itself builds a RAID Z2 on it.

That all works like a charm.
I made the external IPv6 addresses available via DNS, fetched a LE cert via ProxMox ACME client.

The problem now is, I can connect in the Browser, but only with Safari, but I use Fx for my internal stuff, so it should work with Fx as well.

Safari can connect, either by IP or FQDN (internally only resolve the IPv4 address). Fx cannot, neither by IP nor by FQDN, it always says "Unable to connect"
pve is running:

❯ netstat -luntep|grep 8006
tcp6       0      0 :::8006                 :::*                    LISTEN      33         8732       2526/pveproxy

but, strange enough, no response on 443:

❯ telnet 192.168.99.10 443
Trying 192.168.99.10...
telnet: Unable to connect to remote host: Connection refused

I added this to my interfaces file:

    post-up iptables -t nat -A PREROUTING -p tcp -d 192.168.99.10 --dport 443 -j REDIRECT --to-ports 8006

And it seems to work, as Safari can connect.

Has anybody a clue what could go wrong?

 

[bbgeek17]

Hi @24unix , welcome to the forum.

You've properly determined that the PVE is servicing the GUI on port 8006. There is nothing serviced on port 443, so your telnet results are expected.

I am guessing that "Fx" is firefox? I any case, if you have one browser working, that is an indication that PVE is functioning.
Check your "fx" browser for intrusive extensions, try anonymous mode, ensure that you use the right port (8006), check "fx" browser's console for errors, check your firewall/router for any "funny" non-standard port blocking, etc.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[24unix]

Hi @bbgeek17 thx for you reply.
Yes, Fx ist the official abbreviation for Firefox, while many use FF, which I find very ugly.

The port is OK, see the post-up entry for the iptables, and Safari (and, by the way, Chrome and Fx Developer Edition) can open the page.

As the problem seems to be more related to the browser than Proxmox I think I'll dump that browser, as all others work.