HA reachable during statup, but not after

Configuration
1

Since yesterday my HA instance, which has been running for months using the following docker compose:

docker-compose.yml 
services:
  homeassistant:
    container_name: home-assistant
    image: ghcr.io/home-assistant/home-assistant:stable
    volumes:
      - /ssd_data/home-assistant:/config
      - /etc/localtime:/etc/localtime:ro
      - /run/dbus:/run/dbus:ro
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0
    environment:
      - TZ=Europe/Amsterdam
    restart: always
    privileged: true
    network_mode: host

is not reachable anymore after startup is complete.

It is still reachable during startup, so that I see my dashboard with missing entities, and some messages on the bottom “Starting xxx. Not everything will be available until it is finished.” and progressively some “integration xxx is loaded”.
Anyway, after the startup is complete, I cannot access it anymore.

I don’t get “host unreachable” like I get when I completely stop the container, it just stays with the loading circle.
Same on mobile.

The rest of the containers and my server (Ubuntu LTS 24.04.3) are otherwise perfectly running. Just in case, I rebooted it.

It suspiciously matches the update of 2026.2.2, which was installed automatically via watchtower.

I started the container again with docker compose -f docker-compose.yml up to see what’s going on and I have the following messages.
Keep in mind that I haven’t added or updated third party integrations for a while, so the warnings about third party integrations are unlikely to cause the issue.

docker 'up' output 
home-assistant  | s6-rc: info: service s6rc-oneshot-runner: starting
home-assistant  | s6-rc: info: service s6rc-oneshot-runner successfully started
home-assistant  | s6-rc: info: service fix-attrs: starting
home-assistant  | s6-rc: info: service fix-attrs successfully started
home-assistant  | s6-rc: info: service legacy-cont-init: starting
home-assistant  | s6-rc: info: service legacy-cont-init successfully started
home-assistant  | s6-rc: info: service legacy-services: starting
home-assistant  | services-up: info: copying legacy longrun home-assistant (no readiness notification)
home-assistant  | s6-rc: info: service legacy-services successfully started
home-assistant  | 2026-02-15 09:48:13.780 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration moonraker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:13.781 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration entsoe which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:13.781 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration thermal_comfort which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:13.782 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frank_energie which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:13.782 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:13.782 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration apsystems_ecu_reader which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:13.783 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration astroweather which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:13.784 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dewpoint which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:13.784 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration config_editor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:13.785 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
home-assistant  | 2026-02-15 09:48:14.914 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
home-assistant  | 2026-02-15 09:48:14.947 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=648 from 2026-02-15 08:47:53.907603)
home-assistant  | 2026-02-15 09:48:17.973 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.13/site-packages/miio/miot_device.py:23: FutureWarning: functools.partial will be a method descriptor in future Python versions; wrap it in enum.member() if you want to preserve the old behavior
home-assistant  |   Bool = partial(_str2bool)
home-assistant  | 
home-assistant  | 2026-02-15 09:48:26.952 WARNING (MainThread) [custom_components.moonraker] Cannot configure moonraker instance
home-assistant  | 2026-02-15 09:48:26.952 ERROR (MainThread) [moonraker_api.websockets.websocketclient] Websocket connection error: Cannot connect to host 192.168.3.230:7125 ssl:default [Connect call failed ('192.168.x.y', 7125)]

Any way to fix whatever is not working anymore? point release should not cause disruptions.

1 Like
2

Exactly the same issue here. I have installed 2026.2.2 yesterday and the system is unreachable.
Tried to do a backup restore from the CLI but that is not working as well.

Error: 'BackupManager.do_restore_full' blocked from execution, system is not running - freeze

Luckily I am running on Proxmox and have a backup of the VM as well, but this is not a very elegant way of restoring everything after a update.

3

I have heard of multiple instances where the Entso-e integration is breaking their system (mine too) If you have it then restart in safe-mode (if possible) or remove ir from the cli:

ha core stop
cd homeassistant
mkdir -p disabled_custom_components
mv custom_components/entsoe disabled_custom_components/
exit
ha core start
4

Hello,

My Home Assistant (running on a Laptop) is also unrecheble.

The same as Kouny
It is still reachable during startup, so that I see my dashboard with missing entities, and some messages on the bottom “Starting xxx. Not everything will be available until it is finished.” and progressively some “integration xxx is loaded”.
Anyway, after the startup is complete, I cannot access it anymore.

after a hard bood for 4 times i can acces the dachboard if the intrergrations are straring up. but not the terminal
Instellingen > system also dont work. ( sorry i am Ducht my Engels is not that good)

i have installed the HAC Remot HomeAssistant yesterday. but in dont tink thats the problem ?

And i made some automations

I have Entso-e also idd.

5

on the laptop is ha>

ha core stop gifs error annother jop is running core

can i put in somting to safe reboot ?

6

ha core restart --safe-mode

7

That did not work for the first time.

i Hard reboot the laptop( via Power button) and used :
Core restart --Safe-mode

bevore al intergations where started and that Worked. Tanks @istapeter

intergration stoped:
Entso
Backup
remote_homeassistant

Now it is running :smile:

1 Like
8

Okay will try see if the Entso-e integration is the culprit. Thanks @istapeter

1 Like
9

Hi please can someone help me on the same situation on a Raspberry Pi.

in cli command screen I got only Error: another job is running for job group home_assistant_core when I want to restart in --safe-mode.

how can I disable the Entso integration by CLI ?

Thanks

1 Like
10

for me it worked the only wen the intergation was not starded.

1 Like
11

Indeed Entsoe-e is the culprit.
This worked for me in CLI. Just give it a hard reboot thereafter (unplug power).

1 Like
12

Found it!! indeed the same issue here, the Entso component is the issue.

connect my raspberrypi to the HDMI and in command I did

login
cd /mnt/data/supervisor/homeassistant/
mkdir -p disabled_custom_components
mv custom_components/entsoe disabled_custom_components/
exit
remove the powercord and rebooted

Thanks

2 Likes
13
2 Likes
14

You guys are life savers!

3 Likes
15

Idd Tanks All

16

Integration updated to correct this issue and some more.