Cannot access the Web interface anymore after update

1

Hi,

I cannot access my home assistant anymore via the Web interface (http://homeassistant.local:8123/) nor via the mobile companion app, since yesterday.
Obviously, it doesn’t work either from outside the local network (via external IP, via DuckDNS).

The IP address 192.168.0.x does not work anymore either.

I use the home assistant green box.

Presumably, this is happening since an HA update (via my mobile app) yesterday.

I ticked the “backup” box just before.

Oddly enough, ZigBee is still working: that is, any automation is still OK, switches still control the lamps, etc.

I tried many many (rather random?) things, including:


ha core restart

ha supervisor restart

No problem.

Then


ha host reboot

Error: Post "http://supervisor/host/reboot": dial tcp 172.30.32.2:80: connect: connection refused"

Then I tried


reboot

ha supervisor repair

Command completed successfully.

ha supervisor restart

Error: 'Supervisor.restart' blocked from execution, system is not running - startup

Then I tried to reset supervisor


ha core stop

systemctl restart docker

ha supervisor update Error: no supervisor update available - 2025.12.3

Then I tried rebuild:


docker ps -a | grep supervisor

hassio_supervisor

docker rm -f hassio_supervisor

reboot

I also tried


ha supervisor info | grep -i healthy

healthy: true

Then I tried to check if there is something listening to the 8123 port:


ss -tulpn | grep 8123

tcp LISTEN 0 128 0.0.0.0:8123 0.0.0.0:* users:(("python3",pid=3168,fd=12))

tcp LISTEN 0 128 [::]:8123 0.0.0.0:* users:(("python3",pid=3168,fd=11))

And most importantly, I cannot access the Web server from the box itself!


curl http://localhost:8123
curl: (52) empty reply from server

I tried deleting the frontend:


ha core stop

rm -rf /config/.storage/http*

rm -rf /config/.storage/frontend*

ha core start

Still the same issue…

I even tried to rollback


ha core update --version previous

ha core restart

And then


ha core stop

ha core rebuild

ha core start

What else can I try?

Many thanks!

2

Have you tried a cold reboot?
(remove the power)

I am asking, since it sounds to me the supervisor is stuck somehow, preventing a clean reboot:

When that is the case, it is impossible to recover by trying to do a warn reboot, as the supervisor is…well…stuck…

1 Like
3

Oops, sorry for not mentioning it: yes, of course. I removed the power for 5 minutes prior to doing anything else.
Also, the LED status after (re)boot is:

  • white: stable
  • green/orange: blinking more or less randomly.
4

Also note that ping 192.168.0.x does work from another computer on the same network.
What would that mean? A corrupted server in the box, because of a failed upgrade?
What else can I try?

Would reflashing the box solve the issue? If so, what would be the safest procedure? (I have a backup, presumably on the box itself)

5

Hi, that ’ 192.168.0.x’ address is from your HA?

To be clear, it’s a local address and does not leave your network, nor can anybody else access it, so there is no problem to reveal that last digit.

About your problem now:

  • are you sure about the right IP address from your HA?
  • you can ping that IP address and get a reply?
  • did you connect a display to your Green and what is the relevant information?

From https://support.nabucasa.com/hc/en-us/articles/25210352599197-About-the-status-lights-LEDs-on-Home-Assistant-Green

White = power, so normal that it is lit permanently (stable)
Green = activity LED, normal that it blinks
Yellow = system health, blinks in ‘heartbeat pattern’

Depending on the amount of personalization of your HA and whether you have a backup, it can be useful to reinstall.

1 Like
6

Have you tried to start in Safe-Mode ?(No Add-Ons etc loaded!), And also actually checked the Supervisor/Core logs

1 Like
7

Yes, it is displayed on the screen I connected to the HA box, and recognized by my Internet box as well.

Yes.

Yes.
I’m not sure what is relevant, but I cannot find any issue; I tried numerous things (see first message) without success.

No! How can I do that?

8

core restart --safe-mode

General troubleshooting - Home Assistant -

What you then(if you get access to it, you could try to look into configurations/integrations/addons Faults

And Also your DiskSpace, backup-solution etc. related to this

1 Like
9

Safe mode is working, I can log in into the Web interface in safe mode.
But where can I look into relevant information?

Only error I can see in the logs (Home assistant core) is

Enregistreur: homeassistant.components.netatmo
Source: components/netatmo/__init__.py:172
intégration: Netatmo ([documentation](https://www.home-assistant.io/integrations/netatmo), [problèmes](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+netatmo%22))
S'est produit pour la première fois: 14:27:24 (1 occurrence)
Dernier enregistrement: 14:27:24

Error during webhook registration - 400 - Bad request - Allowed ports for webhooks are 80, 88, 443 and 9443. (21) when accessing 'https://api.netatmo.com/api/addwebhook'

I had seen them yesterday as well in the terminal view (see my first message).

The “correction” panel is empty.

I can also see some backups, one Home Assistant Core 2025.12.3, and three Automatic Backup 2025.12.5.

10

check the RAW-log ( 3 dots to the right ), debug (if needed)

Good that you have Backups, but check your DiskSpace, i have no info in regards to your setup, if your system continuesly have build up huge logs and backups, Supervisor will have problems loading all Integrations, Add.Ons etc( In such cases ), but Core will run fine

Edit: And If it was running fine with 2025.12.3 , you could try to restore-backup ( From The Cli ) , thou this would probably be/end up in a “dead-tread” when you try to upgrade again :grin:

Note: I Asume you have checked SuperVisorlog aswell, top right corner

11

Thanks.

Regarding disk space: no problem, 20% usage, I only installed my instance a couple of weeks ago.

Regarding logs, I realize I hadn’t found the whole logs, just what I could see in the terminal.
Using the Web interface, I now have access to all.

In the logs, I can see these selected errors:

[2025-12-28 13:59:35.257 ERROR (MainThread) [homeassistant.components.update] Platform hassio does not generate unique IDs. ID home_assistant_core_version_latest already exists - ignoring update.home_assistant_core_update

…

e[31m2025-12-28 15:11:14.304 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/core_duckdns/restart - Add-on core_duckdns has invalid options: Missing required option 'domains' in Duck DNS (core_duckdns). Got {'domains': [None], 'token': None, 'aliases': [], 'lets_encrypt': {'accept_terms': False, 'algo': 'secp384r1', 'certfile': 'fullchain.pem', 'keyfile': 'privkey.pem'}, 'seconds': 300}e[0m
e[31m2025-12-28 15:20:29.800 ERROR (MainThread) [frontend.js.modern.202512033] Uncaught error from Chrome WebView xx.xx.xx.xx on Android 16
Script error.
null
@:0:0e[0m
e[31m2025-12-28 15:30:29.784 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1462, in async_init
    flow, result = await self._async_init(flow_id, handler, context, data)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1510, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 493, in _async_handle_step
    result: _FlowResultT = await getattr(flow, method)(user_input)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/freebox/config_flow.py", line 106, in async_step_zeroconf
    host = zeroconf_properties["api_domain"]
           ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
KeyError: 'api_domain'e[0m
e[31m2025-12-28 15:30:29.794 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1462, in async_init
    flow, result = await self._async_init(flow_id, handler, context, data)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1510, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 493, in _async_handle_step
    result: _FlowResultT = await getattr(flow, method)(user_input)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/freebox/config_flow.py", line 106, in async_step_zeroconf
    host = zeroconf_properties["api_domain"]
           ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
KeyError: 'api_domain'e[0m

The issue is that I’m almost certain I did the (failed?) update on 30th, not on 28th.
On 30th, the only log is:

s6-rc: info: service legacy-services: stopping
[21:57:40] INFO: e[32mHome Assistant Core finish process exit code 0e[0m
[21:57:40] INFO: e[32mHome Assistant Core service shutdowne[0m
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
e[31m2025-12-30 22:59:27.872 ERROR (MainThread) [homeassistant.components.netatmo] Error during webhook registration - 429 -  - Maximum api usage reached (26) when accessing 'https://api.netatmo.com/api/addwebhook'e[0m
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started

In the supervisor logs, I only find error on 28th December (it might be the day when I added a remote SSL access via DuckDNS + NGINX)

e[33m2025-12-28 14:35:28.993 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon NGINX Home Assistant SSL proxy is failed, restarting...e[0m
e[32m2025-12-28 14:35:29.009 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning addon_core_nginx_proxy applicatione[0m
e[32m2025-12-28 14:35:29.725 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-nginx_proxy with version 3.14.0e[0m
e[32m2025-12-28 14:35:29.982 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from core_nginx_proxye[0m
e[31m2025-12-28 14:35:34.385 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-483855' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1626> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 1640, in watchdog_container
    await self._restart_after_problem(event.state)
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 287, in wrapper
    if not await self._handle_throttling(group_name):
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 552, in _handle_throttling
    raise on_condition(
        f"Rate limit exceeded, more than {self.throttle_max_calls} calls in {self.throttle_period(group_name)}",
    )
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00e[0m
e[33m2025-12-28 14:35:40.911 WARNING (MainThread) [supervisor.addons.addon] Add-on core_nginx_proxy is not runninge[0m
e[33m2025-12-28 14:35:42.738 WARNING (MainThread) [supervisor.addons.addon] Add-on core_nginx_proxy is not runninge[0m
e[32m2025-12-28 14:39:15.343 INFO (SyncWorker_2) [supervisor.docker.manager] Stopping addon_core_duckdns applicatione[0m
e[32m2025-12-28 14:39:18.951 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_core_duckdns applicatione[0m
12

easy test:
go to integration, disable netatmo … restart HA normal

But are you sure you can rule out Duckdns and Nginx ?

Restore from backup, through CLI to backup before Installing duckdns-nginx, could be you next step then

PS: if and when you suspect a specific integration, you can also from the /settings/integrations enable debug for most integration
Again Look at your interface UI, i.e top right corner / 3 Dots

1 Like
13

Hi,
I disabled all integrations, restarted in normal (not safe) mode, all went smooth.
Then, I reenabled each integration one by one, and… everything is still fine. Which is quite strange.

Now, there are two issues:

  • I cannot access the HA interface via the companion app (very strange, as the local IP is correct)
  • I cannot access the HA interface outside the LAN, which may come from some incorrect DuckDNS / NGINX modules configuration when restarted.
14

I unsinstalled and reinstalled the companion app with the default setting (homeassistant.local:8123): on the same Wi-Fi network as the box, I get

Error code: -1
Description: net::ERR_EMPTY_RESPONSE

I even tried in the browser of my mobile phone (on the same Wi-Fi network, again), and I get no connection!
I cannot understand this.

And, even on the local terminal of HA (via the Web interface), I get

[core-ssh ~]$ curl homeassistant.local:8123
curl: (52) Empty reply from server

What am I misunderstanding?

15

Check your companion app if you have the right settings , if you are home you might set settings to “less secure” when at local-network

16

Also, in the companion app, you have to add your WiFi SSID first for it to be able to access your HA.

1 Like
17

Yes, done but it doesn’t work

Even more crazy: on a browser on the mobile phone, I cannot access
http://homeassistant.local:8123/

…While I can on the computer (including in private mode, or using a different browser).

Both are on the same WiFi network.

And the HA terminal itself cannot access this URL (using curl).

18

Use the IP address instead of homeassistant.local to avoid other issues that play a role.

19

Thanks. It doesn’t work either from the mobile phone. Same WiFi network. I tried a different browser, I restarted the mobile phone. It doesn’t work. Always the same ERR_EMPTY_RESPONSE error.

20

Check if your device is not blocked.
With your mobile, if mobile network is turned off and only WiFi: still no connection?