Proxmox GUI in Chrome - connection refused when using hostname, not IP. works fine in firefox

[harmgsn]

Hi all,

This one has me a bit confused and I'm not sure where to start looking. When I try to access a proxmox host in Chrome by hostname https://<hostname>:8006 in chrome I get "connection refused". If I go to it via IP address https://<ip>:8006 it loads fine. However, if I switch to another browser or use incognito mode then It loads without issue via hostname.

Here's what I see in chrome dev console when it fails:

(failed)
net::ERR_CONNECTION_REFUSED

The SSL cert is valid as it loads when I'm in Firefox or Opera via hostname without issue. I've cleared Chrome site data.

Anyone have any thoughts or suggestions?

Thanks!

 

[bbgeek17]

This is a client-side issue. You can start by disabling any extensions.

---

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

 

[harmgsn]

No extensions installed.

 

[bbgeek17]

No extensions installed.

Examine the console of the browser.
There is nothing in PVE that can possibly decide to actively refuse network connection at TCP layer just because you used a hostname in your browser.

See if you can run a light-weight VM on your workstation, ie Sandbox in Windows, to isolate from the host, and test there.

---

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

 

[BobhWasatch]

Most likely Chrome is not using the DNS you expect. Is Settings>Privacy>Use Secure DNS enabled? If so, try turning it off. You might also want to look at the DNS page in chrome://net-internals and see how it is doing DNS resolution.

 

[harmgsn]

Most likely Chrome is not using the DNS you expect. Is Settings>Privacy>Use Secure DNS enabled? If so, try turning it off. You might also want to look at the DNS page in chrome://net-internals and see how it is doing DNS resolution.

And there's the answer. Thank you @BobhWasatch