HAOS Proxmox can't access UI

Configuration
1

I have HAOS 14.0 installed on Proxmox 8.2. I’ve had a number of problems accessing the HA over the LAN ever since installing it:

  1. I have never been able to access it using the internal IP address (http://192.168.1.37:8123) - I get ERR_EMPTY_RESPONSE
  2. I have never been able to access it using the hostname shown on the HAOS console: (http://homeassistant.local:8123) - I get ERR_EMPTY_RESPONSE
  3. I have usually been able to access it using http://homeassistant:8123, but can no longer do so - I get ERR_EMPTY_RESPONSE.

I can access HA on the observer port (http://homeassistant.local:4357/). It shows:
Supervisor:Connected
Supported:Supported
Healthy:Healthy

I have tried restarting HAOS. I have the nginx proxy manager installed, but have not had any success getting it to work.

I am able to access the SMB share, on \homeassistant. I can see that the HA log is being written to, but not with any clues regarding the inability for web clients to connect.

So I am now effectivly locked out of my HA console.
Any ideas for how I can diagnose this?

2

Make sure your device is on the able to access the ProxMox network.
Some WiFi routers can have segregation or similar named features enabled that will prevent access.
Also make sure to use your local DNS and not something like DNS-over-HTTPS.

3

I am seeing the same issue from 3 client devices on the same LAN as the Proxmox host:

  • A Windows 11 desktop connected via ethernet
  • A Windows 11 laptop connected via wifi
  • A Windows 10 VM on the same Proxmox host as the HAOS.
    None of them can access the HA console.
    I’m not using DNS-over-HTTPS or anything else unusual in that respect.
    My router is a Netgear R7800 running DD-WRT v3. I am not implementing any form of segmentation or VLANs.
    I have a DHCP reservation/static IP address for the HAOS defined on the router.
4

Are you sure your browser do not have DNS-OVER-HTTPS enabled?

5

That is not something which I would know how to enable.
Is there any way to check?

EDIT: I just went into Chrome settings and found that “Use secure DNS” was turned on. I turned it off and relaunched the browser, but it hasn’t resolved the problem.
I get the same issue with Edge browser.

6

It is somewhere in your browser settings.
I think all browsers support it today and some have it enabled as default.

7

I’ve just disabled “Secure DNS” on both Chrome and Edge, but I still have the problem.

8

I have also just found this in the log. I don’t know if it’s connected:

2024-12-15 22:09:06.634 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_default_certs with args (<ssl.SSLContext object at 0x7fb734832050>, <Purpose.SERVER_AUTH: _ASN1Object(nid=129, shortname='serverAuth', longname='TLS Web Server Authentication', oid='1.3.6.1.5.5.7.3.1')>) in /usr/local/lib/python3.12/ssl.py, line 713: context.load_default_certs(purpose) inside the event loop; This is causing stability issues. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue
9

How did you manage to install NGINX and SMB Share if you have never been able to access the UI? I fear you are leaving out some details that may be important to troubleshooting.

In the Proxmox web interface, can you access the console ?
{D4BC8531-A6AB-4F67-B76C-C064E17F365B}

10

If you can do that, type login, enter, and run this netstat command

{68CF15E4-3432-407B-ACE0-75825403A1A8}
{68CF15E4-3432-407B-ACE0-75825403A1A8}692×315 25 KB

You should see the line 0.0.0.0:8123 with LISTEN at the end. Is that there?

11

This problem literally resolved itself overnight. First thing this morning I was able to connect again to the HA console (having literally changed nothing overnight). Maybe there was some sort of network issue last night.
???