Home assistant Docker 2025-1 bug

I dont believe both containers can run simultaneously. Please stop one and start the other.

you are using host networking. easier to just stop the other container.
You also cannot have both running containers using the same config folder

looks like go2rtc is causing the problem
possibly port conflicts with the other running HA container

The 2 containers are currently working at the same time as you asked me, the 2024 on port 8123 and the 2025 on port 8124, the 2 containers have their own config folder, the 2025 is a new config folder.
The go2rtc error only appears now because I have both containers running at the same time but if I stop one of the containers I don’t get this error.
The HA restart problem should not come from this go2rtc error which only appeared now.

So if you “restart” within HA with only 1 container running what is showing in portainer log?

HA 2025 logs on start :

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

2025-02-03 17:45:48.468 ERROR (MainThread) [homeassistant.helpers.translation] Validation of translation placeholders for localized (pt) string component.assist_pipeline.issues.assist_in_progress_deprecated.title failed: ({'entity_id', 'integration_name'} != {'integration_name'})

HA 2025 logs on restart within HA no line was added to the log, HA is inaccessible and nothing more in the logs.

HA 2025 logs on restart container via Portainer :

s6-rc: info: service legacy-services: stopping

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

2025-02-03 17:49:18.256 ERROR (MainThread) [homeassistant.helpers.translation] Validation of translation placeholders for localized (pt) string component.assist_pipeline.issues.assist_in_progress_deprecated.title failed: ({'entity_id', 'integration_name'} != {'integration_name'})


Can you try creating a folder under /share/container and deploy a container from there instead of /lib/docker/volumes/? If I recall correctly there are some specific access rights set on the latter folder.

I set it up in /Container/homeassistant-test

HA successfully created the different config files etc…, I tried to restart via HA but still the same.

Here is the log:

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

Unable to find configuration. Creating default one in /config

2025-02-03 18:11:24.335 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:11:24.509 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:11:29.878 WARNING (MainThread) [homeassistant.helpers.translation] Failed to load integration for translation: Invalid domain energy.sensor

2025-02-03 18:11:29.879 WARNING (MainThread) [homeassistant.helpers.translation] Failed to load integration for translation: Invalid domain mobile_app.notify

2025-02-03 18:11:29.879 WARNING (MainThread) [homeassistant.helpers.translation] Failed to load integration for translation: Invalid domain cloud.tts

2025-02-03 18:11:29.880 WARNING (MainThread) [homeassistant.helpers.translation] Failed to load integration for translation: Invalid domain homeassistant.scene

2025-02-03 18:11:29.880 WARNING (MainThread) [homeassistant.helpers.translation] Failed to load integration for translation: Invalid domain sun.sensor

2025-02-03 18:11:30.153 ERROR (MainThread) [homeassistant.helpers.translation] Validation of translation placeholders for localized (pt) string component.assist_pipeline.issues.assist_in_progress_deprecated.title failed: ({'entity_id', 'integration_name'} != {'integration_name'})

2025-02-03 18:11:35.955 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)

Traceback (most recent call last):

  File "/usr/src/homeassistant/homeassistant/helpers/discovery_flow.py", line 137, in _async_start

    await gather_with_limited_concurrency(FLOW_INIT_LIMIT, *init_coros)

  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 114, in gather_with_limited_concurrency

    return await gather(

           ^^^^^^^^^^^^^

    ...<2 lines>...

    )

    ^

  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 112, in sem_task

    return await task

           ^^^^^^^^^^

  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1315, in async_init

    flow, result = await self._async_init(flow_id, handler, context, data)

                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1350, in _async_init

    result = await self._async_handle_step(flow, flow.init_step, data)

             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 491, in _async_handle_step

    result: _FlowResultT = await getattr(flow, method)(user_input)

                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 689, in async_step_zeroconf

    return await self.async_step_confirm()

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 581, in async_step_confirm

    return await self.async_step_verify_radio()

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 331, in async_step_verify_radio

    return await self.async_step_choose_formation_strategy()

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/usr/src/homeassistant/homeassistant/components/zha/config_flow.py", line 347, in async_step_choose_formation_strategy

    await self._radio_mgr.async_load_network_settings()

  File "/usr/src/homeassistant/homeassistant/components/zha/radio_manager.py", line 251, in async_load_network_settings

    await app.connect()

  File "/usr/local/lib/python3.13/site-packages/bellows/zigbee/application.py", line 150, in connect

    await self._ezsp.connect(use_thread=self.config[CONF_USE_THREAD])

  File "/usr/local/lib/python3.13/site-packages/bellows/ezsp/__init__.py", line 138, in connect

    await self.startup_reset()

  File "/usr/local/lib/python3.13/site-packages/bellows/ezsp/__init__.py", line 119, in startup_reset

    await self._gw.wait_for_startup_reset()

  File "/usr/local/lib/python3.13/site-packages/bellows/uart.py", line 63, in wait_for_startup_reset

    await self._startup_reset_future

ConnectionResetError: Remote server closed connection

2025-02-03 18:11:41.438 ERROR (MainThread) [homeassistant.helpers.translation] Validation of translation placeholders for localized (pt) string component.assist_pipeline.issues.assist_in_progress_deprecated.title failed: ({'entity_id', 'integration_name'} != {'integration_name'})

2025-02-03 18:11:45.866 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

s6-rc: info: service legacy-services: stopping

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

2025-02-03 18:14:10.731 ERROR (MainThread) [homeassistant.helpers.translation] Validation of translation placeholders for localized (pt) string component.assist_pipeline.issues.assist_in_progress_deprecated.title failed: ({'integration_name', 'entity_id'} != {'integration_name'})

2025-02-03 18:14:12.102 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from Nas2 (192.168.1.212). Requested URL: '/api/websocket'. (Python/3.12 aiohttp/3.11.6)

2025-02-03 18:15:00.692 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:00.699 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:00.778 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:00.780 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:09.235 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:09.311 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:09.315 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:09.318 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:09.321 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:09.324 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:09.328 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:09.331 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:09.358 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:10.949 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:15:50.178 ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 10.0.3.3, but your HTTP integration is not set-up for reverse proxies

2025-02-03 18:16:12.461 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from Nas2 (192.168.1.212). Requested URL: '/api/websocket'. (Python/3.12 aiohttp/3.11.6)

Do you need to add 10.0.3.3 or the network to “trusted_proxies”? What is this?

ultimately, You really need someone with QNAP to confirm restarts from UI work.
I have always found restarts from software in docker container to be hit or miss. You have some other minor errors that seem unrelated but may be effecting restart as well (such as proxy error above).

I cannot tell from log but normally that proxy error result in IP Ban. Just check if there is file created in your config of banned IPs.

I’ve already tried that earlier in the thread, works like a charm.

1 Like

I have nginx proxy manager, on this new version 2025 I did not put any configuration of the old one and therefore I did not put the proxy parameters, I just added them I no longer have the proxy errors which appear in the log.

Logs from starting container :

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

2025-02-03 22:27:23.203 ERROR (MainThread) [homeassistant.helpers.translation] Validation of translation placeholders for localized (pt) string component.assist_pipeline.issues.assist_in_progress_deprecated.title failed: ({'entity_id', 'integration_name'} != {'integration_name'})

The problem persists, any version of HA from 2025 whether it is fresh installed or not it is impossible to restart HA from its UI, HA freezes at some point without knowing when, becomes inaccessible via browser or mobile app and nothing appears in the logs from the moment HA freezes.

All versions before 2025 work perfectly, HA restarts without problem and I have never had a HA freeze or server crash.

There is a problem with version 2025 and my QNAP but how can I find an error without error logs…

Does anyone know there are logs from the qnap and not from the container that I can see? as I have no error in the container logs…

Well after multiple new installations without old configuration, the 2025 versions do not work on my QNAP, while the versions before 2025 of home assistant there were no problems for more than 3 years! So since 2025 I unfortunately can no longer update Home Assistant which is disappointing, I opened an issue but it was immediately closed because it is not a HA Bug… as they say while before 2024 everything works but since 2025 not…

Help!

“Restart” from ui is issue correct?

This is not great but not world ending. Frustrating however.

Other QNAP user say OK.
Maybe someone with working system can share docker compose?

If it was just the restart from the interface I could do without it but HA becomes inaccessible from time to time and that is the main problem.

I’m going to implement version 2025-2-0 and see if it becomes inaccessible again on its own.

Already did a bit up in the thread.

Hi!
After 3 days of using version 2025.2.0 well I still encounter the same problem, HA becomes inaccessible after an indefinite time without presenting any errors in the logs, the container is still running but HA inaccessible, this happened at different times, yesterday at 7 a.m., tonight at 1 a.m., there are no fixed times…

I don’t know what to do anymore…

After HA crash I lose Tocken access to Smartthings and Tuya which I have to reconfigure each time.

You problem is now unclear to me. So please answer yes/no:

Did you have any problems with 2024 version?

Have you had tried 2025 version with default config?

Restart from UI is not possible if HA has crashed or has out of memory error. It seems your real issue is HA crashing or become non responsive.

If this is true you must first
-confirm HA will run when set as default. Safe mode should be OK but I prefer HA container with default config. You should start with 2024 version running default then upgrade to 2025. This ensures a default that works with 2024 either fails or works with 2025

-after this you can report problem here or GitHub

Did you have any problems with 2024 version?

  • No

Have you had tried 2025 version with default config?

  • Yes

Restart from UI is not possible if HA has crashed or has out of memory error. It seems your real issue is HA crashing or become non responsive.

If this is true you must first
-confirm HA will run when set as default. Safe mode should be OK but I prefer HA container with default config. You should start with 2024 version running default then upgrade to 2025. This ensures a default that works with 2024 either fails or works with 2025

-after this you can report problem here or GitHub

  • I will install a blank version 2024 and update to 2025 to see if the problem persists.

I will try to be more clear about my problem.

All versions before 2025.1.0 I have never encountered a problem.

From 2025 I encounter 2 problems:

  1. HA becomes inaccessible after an indefinite time and nothing appears in the logs, the container is still running.

  2. When HA is working normaly and I need to restart HA via the UI, when I click on restart HA becomes inaccessible and nothing appears in the logs, the container is still running.

I specify that I did tests with an HA 2025 with default config and also an HA 2025 with old config, whether it is a default config or not HA 2025 becomes inaccessible.

I also specify that the QNAP memory was increased to see if the problem with HA did not come from there.

Good news tmjpugh, by switching from HA 2024 default config to HA 2025 default config, I no longer have the problem of restarting from UI. Which is weird because I did blank installations of 2025 and I always had the problem…

How can I recover all my configuration now? Do you think it’s possible for me to reinstall all my old configurations?

Maybe let it run a while to verify but you know needed testing period to find this issue best.

if you restore backup I expect the cause of problem to be restored.
rebuild may not be very difficult. Cut paste yaml is easy to do, just takes time

Even UI items have ability to change to yaml so you may copy it for pasting.

I would manually move items one by one and test for short period between moves. I would start with the custom integrations. I still suspect one of those cause this problem for you. restoring indiviually and testing after install may bring you to the cause. Once it is know maybe you just need to modify original install to work.

EDIT
And as a side note dont make the mistake I did
I update from 2024.12.4 to 2024.2.1. Spent an hour trying to figure out why matter and some automations havent been working for past 3 days.

Get so used to changing the month and point release I forgot to change the year :person_facepalming: