Update 2025.2.3 - core do no start - startup fatal error

DeFla · February 14, 2025, 3:39pm

Hi there,
I expected a quite annoying issue by updating to 2025.2.3, i’m not anymore able to connect to the web interface (ERR_CONNECTION_REFUSED), where the CLI and observer works.
After lot of tries, it seems that the core does not anymore start.
I tried to downgrade, to rebuild, to repair the supervisor, to restart is safe mode, I usualy get the following error : No Home Assistant Core response, assuming a fatal startup error.

I also tried to setup a fresh new VMs and restore one of my backups (I tested the lastest one, but also an older one), the web interface never refesh after the restore.

I succeed to catch some logs in the supervisor in -f mode :

It seems that with the restore, the core component does not start anymore, but why ? I used a backup at a time where HA restart several times without issue.

I’m affraid I would have to reconfigure HA from 0, I’m feeling lost…

jonslilbro · February 25, 2025, 2:58am

Any chance you’ve found a way around this? Restarted this morning and am having the exact same symptoms, CLI and observer say fine, can’t connect from any IP or mdns .local as I have for years, can’t go into safe mode or rebuild, etc.

Rene6 · March 1, 2025, 2:50pm

Same issue here; in CLI I do a “core rebuild” and the result also is “Prossessing done” and next line “Error: No Home Assistant Core response, assuming a fatal startup error”

Rene6 · March 1, 2025, 2:51pm

Did you find out how to reconfigure HA from, 0?

Edwin_D · March 1, 2025, 3:03pm

It says it can’t connect to https://172.30.32.1 so could it be the certificate expired or the ip address changed? Also a bit surprised supervisor connects with ssl but that might be needed in your case?

kizilbash · March 1, 2025, 5:07pm

I’m in the same boat. I ran the update and now I get “connection refused” from my browser. My system is on a raspberry pi 3 headless. I don’t know that I’ve ever even tried to connect to server itself. It does start up enough to get an IP address but I can’t ssh to it and I can’t connect via the web. I really don’t want to reinstall but are there other options?

kizilbash · March 1, 2025, 5:12pm

Update: the connection refused error was from ssh, my browser gives me the following error:

This site can’t be reached

Check if there is a typo in homeassistant.local.

DNS_PROBE_FINISHED_NXDOMAIN

kizilbash · March 1, 2025, 5:32pm

I found my problem! Sort of…
So I went to my PC to see if I could access it via samba and I found it in my network devices. I double click on it and it opens right up in a browser. Huh? I went back to my Mac and nope, I still can’t access it. I do a web search and found that others have had this issue. As a workaround, I installed the HomeAssistant application for MacOS and that runs just fine. It’s only my web browsers (Safari and Arc) that can’t access it. Weird!

quizzical · March 9, 2025, 12:24pm

UPDATE:
In the end my Home Assistant is working again.
I first got the restored backup working by running the command ha core restart.
Then I tried runnign my original instance of home assistant again.
It did shows some errors (see below), but I saw the logs of supervisor and core were still busy doing things and in the end it loaded fine.

2025-03-09 14:44:45.380 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
2025-03-09 14:44:45.381 ERROR (MainThread) [supervisor.core] Can’t start Home Assistant Core - rebuiling
2025-03-09 14:44:45.396 INFO (SyncWorker_5) [supervisor.docker.manager] Stopping homeassistant application
2025-03-09 14:45:05.010 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning homeassistant application
2025-03-09 14:45:14.254 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from a0d7b954_adguard
2025-03-09 14:45:14.369 INFO (MainThread) [supervisor.api.middleware.security] /network/interface/enp0s3/info access from a0d7b954_adguard
2025-03-09 14:45:28.482 WARNING (MainThread) [supervisor.addons.addon] Timeout while waiting for addon Samba share to start, took more than 120 seconds
2025-03-09 14:45:54.225 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2025-03-09 14:46:17.459 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant Package qemux86-64-homeassistant · GitHub with version 2025.2.4
2025-03-09 14:46:17.460 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2025-03-09 14:49:18.153 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
2025-03-09 14:49:18.154 INFO (MainThread) [supervisor.resolution.module] Create new suggestion execute_repair - core / None
2025-03-09 14:49:18.155 INFO (MainThread) [supervisor.resolution.module] Create new issue fatal_error - core / None
2025-03-09 14:49:18.156 INFO (MainThread) [supervisor.addons.manager] Phase ‘application’ starting 7 add-ons

OLD POST:
@DeFla, @jonslilbro , @Rene6
Have you been able to solve this issue?
I am facing the same problem “No Home Assistant Core response, assuming a fatal startup error”
I was thinking I’d fix it by doing a clean install and then restoring my backup from a few days ago, but the restoring backup page keeps running eternally, and when I SSH into my Home Assistant and check type ha su logs then I see the restore process fails due to the same error:

2025-03-09 13:08:24.544 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
2025-03-09 13:08:36.557 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name=‘Task-824’ coro=<BackupManager.do_restore_partial() done, defined at /usr/src/supervisor/supervisor/jobs/decorator.py:191> exception=HomeAssistantStartupTimeout(‘No Home Assistant Core response, assuming a fatal startup error’)>
Traceback (most recent call last):
File “/usr/src/supervisor/supervisor/jobs/decorator.py”, line 312, in wrapper
raise err
File “/usr/src/supervisor/supervisor/jobs/decorator.py”, line 304, in wrapper
return await self._method(obj, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/supervisor/supervisor/backups/manager.py”, line 884, in do_restore_partial
success = await self._do_restore(
^^^^^^^^^^^^^^^^^^^^^^^
…<6 lines>…
)
^
File “/usr/src/supervisor/supervisor/backups/manager.py”, line 742, in _do_restore
await self.sys_homeassistant.core.start(
_job_override__cleanup=False
)
File “/usr/src/supervisor/supervisor/jobs/decorator.py”, line 312, in wrapper
raise err
File “/usr/src/supervisor/supervisor/jobs/decorator.py”, line 304, in wrapper
return await self._method(obj, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/supervisor/supervisor/homeassistant/core.py”, line 352, in start
await self._block_till_run(self.sys_homeassistant.version)
File “/usr/src/supervisor/supervisor/homeassistant/core.py”, line 509, in _block_till_run
raise HomeAssistantStartupTimeout(
…<2 lines>…
)
supervisor.exceptions.HomeAssistantStartupTimeout: No Home Assistant Core response, assuming a fatal startup error

So now I’m equally lost as you are (were?)
Any help would be greatly appreciated. I rely on Home Assistant for a great many things (even my password manager…)