Native HA Backups - Hanging on Uploading to locations

Chykan · July 20, 2025, 2:05am

The native HA Backups is Hanging on Uploading to locations.

This is the second time this has happened to me in the past few months.

While this is occurring I am unable to restart home assistant

Observations and Settings

Home Assistant Cloud is my only external location
1.4GB X 3 = 4.2GB this should be within the 5GB limit

I do a daily backup with retention of 3 and System Optimal time between 06:45 and 07:45.

The naming of the automatic backups seem to be the same (based on HA release version) I am unsure if this naming convection is causing some sort of error. A date/time code would be nice in the name.

I do run Google Cloud Back-ups daily as well at 4:00am

The timings do not seem to be overlapping

STEPS THAT FAILED

Wait until the backup times out and come up with Failed, (Today this was 7hrs Ago)
There does not seem to be a backup.stop command
‘ha supervisor reset’ this did not work

STEPS THAT WORKED

1. Identify the stuck backup

Go to:
Settings → System → Backups

Look for a backup in progress or labeled Creating / Uploading.

2. Delete or force-remove it

Try UI delete → THIS WORKED FOR ME

If it fails: Run in SSH or Terminal add-on:
ha backups list
Find the slug of the stuck backup and remove:
ha backups remove <slug>
3. Restart Home Assistant Core (if backup job is ghosted)
ha core restart
This flushes any stuck backup locks.

3. Check Backup has failed

Go to:
Settings → System → Backups

image949×238 13.3 KB

4. Check Restart is Working

Go to:
Developer Tools → YAML → CHECK CONFIGURATION → RESTART → RESTART

image1425×558 45 KB

5. Should be All OK

Chykan · July 20, 2025, 3:39am

Edwin_D · July 20, 2025, 3:52am

Did you see the note that HA cloud only stores the latest backup? For those from my era, it is like Highlander: There can be only one. My backup is bigger though, it never failed on me.

The is also ~~a Google integration for native backup. I use that one now~~, not the addon. EDIT, I’m mistaking, I dropped Google. Could it be, even without overlap, they are somehow interfering? I use HA cloud, Samba and Onedrive, all with the new HA backup system It takes a long time, but they have not failed on me yet.

Another thing I was wondering, could there be something else on your lan be messing with the upload? As I said, it can take quite long.

Chykan · July 20, 2025, 4:08am

I remember all 3 original Highlander movies well.

I did not realise it only saves one, but I do have full generational back-ups set in Google Cloud. Do you do daily backups @Edwin_D?

Generally my backups are functioning fine it is just these two edge cases.

This would suggest it is not a network setting in my Unifi Dream Wall
Unsure if file names being the same is an issue?

I am not sure if anything is interfering to be quite honest.

This is the second time this has happened since I enabled HA Backups.
My Unifi Dream Wall shows no irregularities when the backup occurred.
Small yellow blip is high latency on Thursday Evening.

image2134×866 173 KB

Edwin_D · July 20, 2025, 4:12am

I’m doing dailies to 4 locations, two encrypted, two not encrypted, system optimal time.

Chykan · July 20, 2025, 4:13am

I am not alone with this issue, even though it seems rare.

Edwin_D · July 20, 2025, 4:17am

It is good to know you can help people get unstuck, better if we can identify what triggers the problem.

Chykan · July 20, 2025, 4:34am

Yes definitely, I looked everywhere. I could not see any obvious errors in logs. Do you have anywhere you would suggest looking? Especially if I have the issue again.

SUPERVISOR LOGS

2025-07-20 12:09:43.320 INFO (MainThread) [supervisor.backups.manager] Found 5 backup files

2025-07-20 12:09:43.349 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/31e48303.tar: "filename './backup.json' not found"

2025-07-20 12:09:43.374 INFO (MainThread) [supervisor.discovery] Loaded 1 messages

2025-07-20 12:09:43.374 INFO (MainThread) [supervisor.ingress] Loaded 12 ingress sessions

e[32m2025-07-20 12:27:26.614 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation completee[0m
e[32m2025-07-20 12:27:27.411 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='NOT_RUNNING', offline_db_migration=False)e[0m
e[32m2025-07-20 12:27:57.914 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='RUNNING', offline_db_migration=False)e[0m
e[32m2025-07-20 12:27:57.915 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instancee[0m

e[31m2025-07-20 10:44:01.588 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-241611' coro=<_websocket_forward() done, defined at /usr/src/supervisor/supervisor/api/ingress.py:380> exception=ClientConnectionResetError('Cannot write to closing transport')>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/api/ingress.py", line 387, in _websocket_forward
    await ws_to.send_bytes(msg.data)
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client_ws.py", line 252, in send_bytes
    await self._writer.send_frame(data, WSMsgType.BINARY, compress=compress)
  File "/usr/local/lib/python3.13/site-packages/aiohttp/_websocket/writer.py", line 72, in send_frame
    raise ClientConnectionResetError("Cannot write to closing transport")
aiohttp.client_exceptions.ClientConnectionResetError: Cannot write to closing transporte[0m
e[32m2025-07-20 11:00:05.356 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state runninge[0m

e[32m2025-07-20 04:01:46.256 INFO (MainThread) [supervisor.api.backups] Downloading backup 6b5735bbe[0m
e[32m2025-07-20 04:01:48.613 INFO (MainThread) [supervisor.backups.manager] Found 5 backup filese[0m
e[31m2025-07-20 04:01:48.646 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/31e48303.tar: "filename './backup.json' not found"e[0m
e[32m2025-07-20 04:03:29.415 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m

e[31m2025-07-19 08:01:48.587 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/31e48303.tar: "filename './backup.json' not found"e[0m

e[33m2025-07-19 03:08:00.026 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff7c454e10>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[33m2025-07-19 03:08:05.037 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff7c4565d0>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[33m2025-07-19 03:08:10.041 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff7c454050>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m

[32m2025-07-18 08:14:07.128 INFO (MainThread) [supervisor.resolution.check] System checks completee[0m
e[32m2025-07-18 08:14:07.129 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state runninge[0m
e[32m2025-07-18 08:14:07.810 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation completee[0m
e[32m2025-07-18 08:14:07.810 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state runninge[0m
e[32m2025-07-18 08:14:07.811 INFO (MainThread) [supervisor.resolution.fixup] System autofix completee[0m
e[32m2025-07-18 08:17:29.944 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m
e[33m2025-07-18 08:27:48.923 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Error WebSocket message received while proxying: ServerTimeoutError('No PONG received after 15.0 seconds')e[0m
e[33m2025-07-18 08:27:48.737 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Error WebSocket message received while proxying: ServerTimeoutError('No PONG received after 15.0 seconds')e[0m
e[33m2025-07-18 08:27:48.870 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Error WebSocket message received while proxying: ServerTimeoutError('No PONG received after 15.0 seconds')e[0m
e[33m2025-07-18 08:27:48.871 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Error WebSocket message received while proxying: ServerTimeoutError('No PONG received after 15.0 seconds')e[0m
e[33m2025-07-18 08:27:48.872 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Error WebSocket message received while proxying: ServerTimeoutError('No PONG received after 15.0 seconds')e[0m
e[33m2025-07-18 08:27:48.873 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Error WebSocket message received while proxying: ServerTimeoutError('No PONG received after 15.0 seconds')e[0m
e[33m2025-07-18 08:27:48.875 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Error WebSocket message received while proxying: ServerTimeoutError('No PONG received after 15.0 seconds')e[0m
e[33m2025-07-18 08:27:48.876 WARNING (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Error WebSocket message received while proxying: ServerTimeoutError('No PONG received after 15.0 seconds')e[0m
e[33m2025-07-18 08:27:49.525 WARNING (MainThread) [supervisor.misc.tasks] Watchdog missed an Home Assistant Core API response.e[0m
e[32m2025-07-18 08:27:54.681 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closede[0m
e[32m2025-07-18 08:27:54.790 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closede[0m
e[32m2025-07-18 08:27:54.791 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closede[0m
e[32m2025-07-18 08:27:54.793 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closede[0m
e[32m2025-07-18 08:27:54.794 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closede[0m
e[32m2025-07-18 08:27:54.796 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closede[0m
e[32m2025-07-18 08:27:54.800 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closede[0m
e[32m2025-07-18 08:27:54.801 INFO (MainThread) [supervisor.api.proxy] [a0d7b954_vscode] Home Assistant WebSocket API closede[0m
e[33m2025-07-18 08:27:54.831 WARNING (MainThread) [supervisor.misc.tasks] Watchdog/Application found a problem with observer plugin!e[0m
e[32m2025-07-18 08:27:55.591 INFO (SyncWorker_1) [supervisor.docker.manager] Stopping hassio_observer applicatione[0m
e[32m2025-07-18 08:27:57.533 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning hassio_observer applicatione[0m
e[32m2025-07-18 08:27:57.785 INFO (MainThread) [supervisor.plugins.observer] Starting observer plugine[0m
e[32m2025-07-18 08:27:59.030 INFO (MainThread) [supervisor.docker.observer] Starting Observer ghcr.io/home-assistant/aarch64-hassio-observer with version 2025.02.0 - 172.30.32.6e[0m
e[32m2025-07-18 08:28:04.617 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m2025-07-18 08:28:04.696 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m2025-07-18 08:28:04.709 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m2025-07-18 08:28:04.721 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m2025-07-18 08:28:04.727 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m2025-07-18 08:28:04.736 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m2025-07-18 08:28:04.740 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m2025-07-18 08:28:04.832 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[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
cont-init: info: running /etc/cont-init.d/udev.sh
[22:33:07] INFO: e[32mUsing udev information from hoste[0m
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
[22:33:07] INFO: e[32mStarting local supervisor watchdog...e[0m
s6-rc: info: service legacy-services successfully started
e[32m2025-07-17 22:33:10.233 INFO (MainThread) [__main__] Initializing Supervisor setupe[0m

e[32m2025-07-16 18:12:25.306 INFO (MainThread) [supervisor.docker.observer] Starting Observer ghcr.io/home-assistant/aarch64-hassio-observer with version 2025.02.0 - 172.30.32.6e[0m
e[31m2025-07-16 18:12:25.779 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/states/binary_sensor.backups_stale: [Errno None] Can not write request body for http://172.30.32.1:8123/api/states/binary_sensor.backups_stalee[0m
e[31m2025-07-16 18:12:25.780 ERROR (MainThread) [supervisor.api.proxy] Error on API for request states/binary_sensor.backups_stalee[0m
e[32m2025-07-16 18:12:25.807 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[31m2025-07-16 18:12:25.850 ERROR (MainThread) [aiohttp.server] Error handling request from 172.30.33.3
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_protocol.py", line 510, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/sentry_sdk/integrations/aiohttp.py", line 157, in sentry_app_handle
    reraise(*_capture_exception())
    ~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/sentry_sdk/utils.py", line 1746, in reraise
    raise value
  File "/usr/local/lib/python3.13/site-packages/sentry_sdk/integrations/aiohttp.py", line 140, in sentry_app_handle
    response = await old_handle(self, request)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_app.py", line 569, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 198, in block_bad_requests
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 208, in system_validation
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 225, in token_validation
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 289, in core_proxy
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/supervisor/supervisor/api/proxy.py", line 227, in websocket
    await server.prepare(request)
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_ws.py", line 214, in prepare
    protocol, writer = self._pre_start(request)
                       ~~~~~~~~~~~~~~~^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_ws.py", line 317, in _pre_start
    assert transport is not None
           ^^^^^^^^^^^^^^^^^^^^^
AssertionErrore[0m

e[32m2025-07-16 14:15:41.367 INFO (MainThread) [supervisor.backups.manager] Found 4 backup filese[0m
e[31m2025-07-16 14:15:41.388 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/31e48303.tar: "filename './backup.json' not found"e[0m
e[32m2025-07-16 14:15:50.194 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m

e[32m2025-07-15 18:13:33.589 INFO (MainThread) [supervisor.backups.manager] Found 4 backup filese[0m
e[31m2025-07-15 18:13:33.613 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/31e48303.tar: "filename './backup.json' not found"e[0m
e[32m2025-07-15 18:13:33.629 INFO (MainThread) [supervisor.discovery] Loaded 1 messagese[0m

e[31m2025-07-15 08:17:28.547 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/31e48303.tar: "filename './backup.json' not found"e[0m

e[31m2025-07-13 16:17:28.438 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/31e48303.tar: "filename './backup.json' not found"e[0m

e[33m2025-07-12 21:23:17.872 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff954af390>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[33m2025-07-12 21:23:22.877 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff954af750>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[33m2025-07-12 21:23:27.882 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff954aee90>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[32m2025-07-12 21:24:17.162 INFO (MainThread) [supervisor.host.info] Updating local host informatione[0m
e[33m2025-07-12 21:24:17.873 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff954afb10>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[32m2025-07-12 21:24:17.937 INFO (MainThread) [supervisor.host.services] Updating service informatione[0m
e[32m2025-07-12 21:24:17.951 INFO (MainThread) [supervisor.host.network] Updating local network informatione[0m
e[32m2025-07-12 21:24:18.149 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio informatione[0m
e[32m2025-07-12 21:24:18.160 INFO (MainThread) [supervisor.host.manager] Host information reload completede[0m
e[33m2025-07-12 21:24:22.878 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff954ada90>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[33m2025-07-12 21:24:27.883 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffffa6aef4d0>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m

e[33m2025-07-12 21:17:42.553 WARNING (MainThread) [supervisor.jobs] 'GitRepo.pull' blocked from execution, no supervisor internet connectione[0m
e[33m2025-07-12 21:17:52.679 WARNING (MainThread) [supervisor.jobs] 'GitRepo.pull' blocked from execution, no supervisor internet connectione[0m
e[31m2025-07-12 21:17:52.681 ERROR (MainThread) [supervisor.store] Could not reload repository 69755fa6 due to StoreJobError("'GitRepo.pull' blocked from execution, no supervisor internet connection")e[0m
e[31m2025-07-12 21:17:52.682 ERROR (MainThread) [supervisor.store] Could not reload repository 8bce8ef4 due to StoreJobError("'GitRepo.pull' blocked from execution, no supervisor internet connection")e[0m
e[31m2025-07-12 21:17:52.682 ERROR (MainThread) [supervisor.store] Could not reload repository 68e874ae due to StoreJobError("'GitRepo.pull' blocked from execution, no supervisor internet connection")e[0m
internet connection")e[0m
e[33m2025-07-12 21:18:17.871 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffffa6aef4d0>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m

e[33m2025-07-12 21:15:17.871 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffffa1b42c10>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[33m2025-07-12 21:15:22.876 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff954ae0d0>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[32m2025-07-12 21:15:24.026 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state runninge[0m
e[32m2025-07-12 21:15:24.026 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_servere[0m
e[33m2025-07-12 21:15:27.878 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff954ad6d0>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[32m2025-07-12 21:15:30.680 INFO (MainThread) [supervisor.jobs] 'CheckDNSServer.run_check' blocked from execution, no supervisor internet connectione[0m
e[32m2025-07-12 21:15:30.680 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_servere[0m
e[32m2025-07-12 21:15:30.680 INFO (MainThread) [supervisor.jobs] 'CheckDNSServerIPv6.run_check' blocked from execution, no supervisor internet connectione[0m
e[32m2025-07-12 21:15:30.681 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/systeme[0m
e[32m2025-07-12 21:15:30.681 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/coree[0m
e[32m2025-07-12 21:15:30.681 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/systeme[0m
e[32m2025-07-12 21:15:30.682 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/systeme[0m
e[32m2025-07-12 21:15:30.687 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/systeme[0m
e[32m2025-07-12 21:15:30.687 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/systeme[0m
e[32m2025-07-12 21:15:30.688 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addone[0m
e[32m2025-07-12 21:15:30.688 INFO (MainThread) [supervisor.jobs] 'CheckAddonPwned.run_check' blocked from execution, no supervisor internet connectione[0m
e[32m2025-07-12 21:15:30.688 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisore[0m
e[32m2025-07-12 21:15:30.700 INFO (MainThread) [supervisor.resolution.check] System checks completee[0m
e[32m2025-07-12 21:15:30.700 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state runninge[0m
e[32m2025-07-12 21:15:30.991 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation completee[0m
e[32m2025-07-12 21:15:30.993 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state runninge[0m
e[32m2025-07-12 21:15:30.993 INFO (MainThread) [supervisor.resolution.fixup] System autofix completee[0m
e[33m2025-07-12 21:16:17.871 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffffa6aef4d0>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m

e[32m2025-07-12 20:15:24.013 INFO (MainThread) [supervisor.resolution.fixup] System autofix completee[0m
e[32m2025-07-12 20:17:28.361 INFO (MainThread) [supervisor.backups.manager] Found 4 backup filese[0m
e[31m2025-07-12 20:17:28.380 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/31e48303.tar: "filename './backup.json' not found"e[0m
e[32m2025-07-12 20:17:36.473 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m
e[32m2025-07-12 20:17:38.392 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backupe[0m
e[32m2025-07-12 20:17:38.399 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backupe[0m
e[33m2025-07-12 20:28:17.865 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffffa6aaf4d0>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:28:22.881 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NameResolutionError("<urllib3.connection.HTTPSConnection object at 0xffff954ae0d0>: Failed to resolve 'o427061.ingest.sentry.io' ([Errno -3] Try again)")': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:28:52.889 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0xffff954ad1d0>, 'Connection to o427061.ingest.sentry.io timed out. (connect timeout=30)')': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:29:18.558 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffff954aec10>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:29:21.626 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffff954ae490>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:29:24.698 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffff954aed50>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:30:16.926 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffffa6aef4d0>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:30:19.995 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffffa6aaf4d0>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:30:23.067 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffffa6aaf250>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:31:15.291 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffffa6aaf250>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:31:21.435 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffffa6aaf4d0>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m
e[33m2025-07-12 20:31:27.579 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffff954afc50>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m
e[32m2025-07-12 20:31:49.409 INFO (SyncWorker_1) [supervisor.docker.manager] Stopping addon_d5369777_music_assistant applicatione[0m
e[32m2025-07-12 20:31:49.599 INFO (MainThread) [supervisor.api.proxy] [d5369777_music_assistant] Home Assistant WebSocket API closede[0m
e[32m2025-07-12 20:31:59.979 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning addon_d5369777_music_assistant applicatione[0m
e[32m2025-07-12 20:32:00.576 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/music-assistant/server with version 2.5.5e[0m
e[33m2025-07-12 20:32:07.232 WARNING (MainThread) [supervisor.api.middleware.security] No API token provided for /coree[0m
e[32m2025-07-12 20:32:12.570 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initializee[0m
e[32m2025-07-12 20:32:12.579 INFO (MainThread) [supervisor.api.proxy] WebSocket access from d5369777_music_assistante[0m
e[32m2025-07-12 20:32:12.588 INFO (MainThread) [supervisor.api.proxy] [d5369777_music_assistant] Home Assistant WebSocket API proxy runninge[0m
e[33m2025-07-12 20:32:19.803 WARNING (sentry-sdk.BackgroundWorker) [urllib3.connectionpool] Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffffa1b425d0>: Failed to establish a new connection: [Errno 113] Host is unreachable')': /api/5370612/envelope/e[0m

DNS LOGS

[INFO] 127.0.0.1:59703 - 35077 "NS IN . udp 17 false 512" REFUSED qr,aa,rd 17 0.000150383s

[INFO] 127.0.0.1:57909 - 43259 "NS IN . udp 17 false 512" REFUSED qr,aa,rd 17 0.000144716s

[INFO] 172.30.32.1:42435 - 21465 "A IN ap-southeast-1-0.ui.nabu.casa. udp 47 false 512" - - 0 12.008798613s

[ERROR] plugin/errors: 2 ap-southeast-1-0.ui.nabu.casa. A: read udp 127.0.0.1:38812->127.0.0.1:5553: i/o timeout

[INFO] 127.0.0.1:35244 - 10851 "NS IN . udp 17 false 512" REFUSED qr,aa,rd 17 0.000282556s

[INFO] 172.30.32.1:42435 - 22173 "AAAA IN ap-southeast-1-0.ui.nabu.casa. udp 47 false 512" - - 0 12.013432014s

[ERROR] plugin/errors: 2 ap-southeast-1-0.ui.nabu.casa. AAAA: read udp 127.0.0.1:60488->127.0.0.1:5553: i/o timeout

[INFO] 127.0.0.1:44335 - 10334 "NS IN . udp 17 false 512" REFUSED qr,aa,rd 17 0.000200635s

[INFO] 127.0.0.1:43211 - 52908 "NS IN . udp 17 false 512" REFUSED qr,aa,rd 17 0.000133298s

[INFO] 172.30.32.1:42435 - 21465 "A IN ap-southeast-1-0.ui.nabu.casa. udp 47 false 512" - - 0 12.006838926s

[ERROR] plugin/errors: 2 ap-southeast-1-0.ui.nabu.casa. A: read udp 127.0.0.1:56302->127.0.0.1:5553: i/o timeout

[INFO] 172.30.32.1:42435 - 22173 "AAAA IN ap-southeast-1-0.ui.nabu.casa. udp 47 false 512" - - 0 12.006912347s

[ERROR] plugin/errors: 2 ap-southeast-1-0.ui.nabu.casa. AAAA: read udp 127.0.0.1:39452->127.0.0.1:5553: i/o timeout

[INFO] 172.30.32.2:35647 - 9759 "A IN o427061.ingest.sentry.io. udp 42 false 512" - - 0 12.006458804s
[ERROR] plugin/errors: 2 o427061.ingest.sentry.io. A: read udp 127.0.0.1:40406->127.0.0.1:5553: i/o timeout

creedda · December 12, 2025, 3:11am

I’m seeing this as well. Did you ever identify what caused it for you?

Chykan · December 12, 2025, 3:14am

No never found out. I have not had one hang in quite some time now.

The solution is Native HA Backups - Hanging on Uploading to locations

cromelex · December 14, 2025, 10:29am

I’m having this issue now with 2025.12.2 and .3. This started happening after adding the Backblaze B2 integration for backup target (but could have been coincidence, considering that’s 2025.12 so it could be that instead).

The automatic backup is hanging for over 4 hours. It doesn’t actually say creating/uploading for any of the backups on the list: /config/backup/overview just shows “uploading” on top of the page.

This backup and previous backups uploaded successfully to my NAS + Home Assistant Cloud - it doesn’t show any icon for Backblaze, so not sure if that’s where it is hanging, but I can actually see that.

Wish there was either a timeout or a stop command - ended up having to follow your instructions to stop it.

I can’t see anything in the logs to indicate what is failing unfortunately.

When I try a manual backup I can get it to upload to all locations successfully (including Backblaze), so I can’t quite understand why the automated one hang for the last 2 nights (well, it hang somewhere but it still seemingly uploaded everywhere?).

Weird one.

Chykan · December 15, 2025, 12:50am

I still run the Home Assistant Google Drive Backup Add-On daily at 04:00 and;

Native Backup (Locally & Nabu Casa Cloud) daily at 05:30

Unfortunately the only solution for me was to follow this process. Delete or force remove hung back-up then Restart Core.

I have had no issues since 20 July 2025, I always stay up to date with the latest HA stable updates.

Possibly related issues

github.com/home-assistant/core

Backups fail to signal completion, locking out further Core-initiated backups

opened 03:07AM - 23 Oct 25 UTC

jeffsf

integration: backup

### The problem I started noticing problems with GUI-initiated backups failing …to store to a WebDAV destination and "spinning forever" perhaps coincidentally with upgrade to 10.0. Backups even to local destinations began to spin forever shortly thereafter. Problem stated at https://community.home-assistant.io/t/backups-failing-coincident-with-2025-10-0-update/938487 with no solution. I have since transitioned to other hardware and the backups do not complete from the perspective of the GUI and recorded states. They show as failed even though the tar files are present on the local media. Claude pulled together the analysis. I'll spare you its suggestions as I don't know the codebase well enough to know if it is hallucinating or being truly useful. ## Summary Backups fail to complete on HAOS installations. Home Assistant Core initiates a backup successfully and receives initial progress events, but the backup process hangs indefinitely after the `addon_repositories` stage. The backup job completes successfully in Supervisor, but Home Assistant Core never receives the completion event. ## Environment Installation method: Home Assistant OS Core: 2025.10.3 Supervisor: 2025.10.0 Operating System: 16.2 Frontend: 20251001.4 ``` # ha info arch: amd64 channel: stable docker: 28.3.3 features: - reboot - shutdown - services - network - hostname - timedate - os_agent - haos - resolved - journal - disk - mount hassos: "16.2" homeassistant: 2025.10.3 hostname: homeassistant logging: info machine: qemux86-64 machine_id: 72b21e07527745b48ed954584c746819 operating_system: Home Assistant OS 16.2 state: running supervisor: 2025.10.0 supported: true supported_arch: - amd64 - i386 timezone: America/Los_Angeles ``` Both bare metal on ODRIOD C2 and Proxmox VM running OVA image on Dell Wyze 5070 (Pentium 5005) have been impacted. ## Steps to Reproduce 1. Initiate a backup through Home Assistant UI 2. Observe backup progress in logs 3. Backup progresses to `addon_repositories` stage 4. No further progress is shown 5. Backup appears to hang indefinitely ## Expected Behavior 1. Backup should progress through all stages 2. Backup should complete successfully and report completion to user 3. Backup file should be available in configured locations ## Actual Behavior 1. Backup reaches `addon_repositories` stage 2. No further progress events are received 3. Home Assistant Core remains in "creating backup" state indefinitely 4. User interface shows backup as "in progress" forever 5. Backup file IS created successfully locally 6. Backup is NOT written to the WebDAV store, if enabled 7. Supervisor job shows as completed successfully ## Evidence ### Home Assistant Core Logs ``` 2025-10-22 16:23:12.259 DEBUG (MainThread) [homeassistant.components.backup] Backup state: idle -> create_backup 2025-10-22 16:23:12.259 DEBUG (MainThread) [homeassistant.components.backup] Received backup event: CreateBackupEvent(manager_state=<BackupManagerState.CREATE_BACKUP: 'create_backup'>, reason=None, stage=None, state=<CreateBackupState.IN_PROGRESS: 'in_progress'>) 2025-10-22 16:23:12.261 DEBUG (MainThread) [homeassistant.components.backup] Finished fetching backup data in 0.000 seconds (success: True) 2025-10-22 16:23:12.296 DEBUG (MainThread) [homeassistant.components.backup] Received backup event: CreateBackupEvent(manager_state=<BackupManagerState.CREATE_BACKUP: 'create_backup'>, reason=None, stage=<CreateBackupStage.ADDON_REPOSITORIES: 'addon_repositories'>, state=<CreateBackupState.IN_PROGRESS: 'in_progress'>) 2025-10-22 16:23:12.296 DEBUG (MainThread) [homeassistant.components.backup] Finished fetching backup data in 0.000 seconds (success: True) ``` (No further log entries related to backup) ### Supervisor Job Status Output from `ha jobs info` for the backup job: ```yaml ignore_conditions: [] jobs: - child_jobs: - child_jobs: [] created: "2025-10-22T23:23:12.278812+00:00" done: true errors: [] extra: null name: backup_store_homeassistant progress: 100 reference: "21294352" stage: null uuid: e8b4bf941bad44e598e561d36c06ea02 - child_jobs: - child_jobs: [] created: "2025-10-22T23:23:34.687711+00:00" done: true errors: [] extra: null name: backup_addon_save progress: 100 reference: a0d7b954_ssh stage: null uuid: 84f1b872c8d4469d8ea7c3b9ed0daa2c created: "2025-10-22T23:23:34.687558+00:00" done: true errors: [] extra: null name: backup_store_addons progress: 100 reference: "21294352" stage: null uuid: 4d3d2b6acfb64d2398e949541dedd9b4 - child_jobs: - child_jobs: [] created: "2025-10-22T23:23:34.906561+00:00" done: true errors: [] extra: null name: backup_folder_save progress: 100 reference: ssl stage: null uuid: c5d70a43b6ad41f4b94fa83c36360362 created: "2025-10-22T23:23:34.906366+00:00" done: true errors: [] extra: null name: backup_store_folders progress: 100 reference: "21294352" stage: null uuid: 441f0106bd19469086a3074a6a281b21 created: "2025-10-22T23:23:12.269546+00:00" done: true errors: [] extra: null name: backup_manager_partial_backup progress: 100 reference: "21294352" stage: finishing_file uuid: 5b1c9ddfc7874a239463af988ac9b2db ``` ### Filesystem Evidence The actual backup file on disk confirms the timeline: ```bash # stat /mnt/data/supervisor/backup/manual-no-media-no-share-all-add-ons-both-destinations_2025-10-22_16.23_12261913.tar File: manual-no-media-no-share-all-add-ons-both-destinations_2025-10-22_16.23_12261913.tar Size: 782796800 Blocks: 1528912 IO Block: 4096 regular file Device: 811h/2065d Inode: 131102 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2025-10-22 16:23:12.275634462 -0700 Modify: 2025-10-22 16:23:34.918733057 -0700 Change: 2025-10-22 16:23:34.918733057 -0700 ``` ### Key Observations From Supervisor job status: - Job status: `done: true` - Job errors: `[]` (empty - no errors) - Job progress: `100` (complete) - Final stage: `finishing_file` - All child jobs completed successfully: - `backup_store_homeassistant` - done - `backup_store_addons` (including addon `a0d7b954_ssh`) - done - `backup_store_folders` (ssl folder) - done - Job creation time: `2025-10-22T23:23:12.269546+00:00` (16:23:12 local time) - Job completed by: `2025-10-22T23:23:34.906561+00:00` at latest (16:23:34 local time) - Total time: ~22 seconds from start to completion From filesystem: - ✅ File access time: `16:23:12.275` - matches when Supervisor job started (0.006 seconds after job creation) - ✅ File modify time: `16:23:34.918` - matches when Supervisor job completed (0.012 seconds after job marked done) - ✅ File size: 782,796,800 bytes (~746 MB) - backup is complete and valid - ✅ Write duration: 22.643 seconds from first access to final modification This ~~proves~~ _suggests:_ 1. The backup file was successfully created and completed 2. The completion timestamps precisely match between Supervisor job status and filesystem 3. The file is not corrupted or incomplete (full 746 MB file) 4. Supervisor successfully finished writing the backup file at 16:23:34.918 5. HA Core was still waiting for events at this time and beyond 6. Three independent sources (HA Core logs, Supervisor job status, filesystem) all corroborate the timeline ## Timeline Analysis Comparing Home Assistant Core logs with Supervisor job timestamps and filesystem evidence: | Time | Event | Source | |------|-------|--------| | 16:23:12.259 | Backup state: idle -> create_backup | HA Core | | 16:23:12.269 | Job created in Supervisor | Supervisor | | 16:23:12.275 | Backup file first accessed (write begins) | Filesystem | | 16:23:12.278 | backup_store_homeassistant started | Supervisor | | 16:23:12.296 | Last event received by HA Core (addon_repositories stage) | HA Core | | 16:23:34.687 | backup_store_addons completed | Supervisor | | 16:23:34.906 | backup_store_folders completed | Supervisor | | 16:23:34.906 | Job completed (stage: finishing_file) | Supervisor | | 16:23:34.918 | Backup file last modified (write complete) | Filesystem | | [never] | Completion event received by HA Core | ❌ Missing | **Critical Gap:** Supervisor completed the backup at 16:23:34 (~22 seconds after start), confirmed by filesystem write completion at 16:23:34.918, but HA Core never received any events after 16:23:12.296 (the initial addon_repositories event). During the 22+ seconds of backup activity, HA Core received zero progress updates. ## Technical Analysis ### Event Flow Architecture Home Assistant Core receives job progress events from Supervisor through the following mechanism: 1. **Supervisor → HA Core WebSocket Connection** - Supervisor sends events via websocket to HA Core - Endpoint: `websocket_supervisor_event` in `homeassistant/components/hassio/websocket_api.py:99-104` 2. **Event Dispatcher** - Events are dispatched internally via `async_dispatcher_send(hass, EVENT_SUPERVISOR_EVENT, msg[ATTR_DATA])` - Signal name: `EVENT_SUPERVISOR_EVENT = "supervisor_event"` 3. **Event Listener in Backup Code** - Located in `homeassistant/components/hassio/backup.py:714-739` - Method: `_async_listen_job_events()` - Subscribes to `EVENT_SUPERVISOR_EVENT` signal - Filters for matching job UUID 4. **Progress Callback** - Located in `homeassistant/components/hassio/backup.py:394-409` - Method: `on_job_progress()` - Processes event data and updates UI 5. **Blocking Wait** - Located in `homeassistant/components/hassio/backup.py:414` - Code: `await backup_complete.wait()` - Waits indefinitely for `backup_complete` event to be set - Event is set when `data.get("done") is True` in progress callback ### Where the Process Hangs **File:** `homeassistant/components/hassio/backup.py` **Method:** `SupervisorBackupReaderWriter._async_wait_for_backup()` **Line:** ~414 ```python async def _async_wait_for_backup(self, backup, locations, *, on_progress, ...) -> WrittenBackup: backup_complete = asyncio.Event() backup_id: str | None = None create_errors: list[dict[str, str]] = [] @callback def on_job_progress(data: Mapping[str, Any]) -> None: """Handle backup progress.""" nonlocal backup_id if not (stage := try_parse_enum(CreateBackupStage, data.get("stage"))): _LOGGER.debug("Unknown create stage: %s", data.get("stage")) else: on_progress(CreateBackupEvent(reason=None, stage=stage, state=CreateBackupState.IN_PROGRESS)) if data.get("done") is True: backup_id = data.get("reference") create_errors.extend(data.get("errors", [])) backup_complete.set() # <-- This never gets called unsub = self._async_listen_job_events(backup.job_id, on_job_progress) try: await self._get_job_state(backup.job_id, on_job_progress) await backup_complete.wait() # <-- Blocks here forever finally: unsub() # Code after this point never executes ``` ### What We ~~Know~~ _Believe_ 1. ✅ Backup job was successfully created in Supervisor 2. ✅ Home Assistant Core subscribed to job events 3. ✅ Initial job state was fetched and processed (showing addon_repositories stage) 4. ✅ Supervisor completed the backup successfully with no errors 5. ❌ Home Assistant Core never received events after the initial addon_repositories event 6. ❌ Home Assistant Core is blocked at `backup_complete.wait()` with no timeout 7. ❌ The `on_job_progress` callback with `done: True` was never called ### Potential Causes _(I'll spare you this as I can't confirm it to be reasonable)_ ## Impact ### User Impact - **High:** Users cannot create backups through Home Assistant UI - Backup appears to hang with no feedback - No error message or indication of what went wrong - User can not restart Home Assistant, reboot is also blocked <img width="352" alt="Image" src="https://github.com/user-attachments/assets/8302d56c-2511-46fa-a7fc-280ad5d072c8" /> <img width="352" alt="Image" src="https://github.com/user-attachments/assets/cc990094-00d1-4e57-94ef-2f25a6284b36" /> ### System Impact - **Medium:** Home Assistant remains in "creating backup" state - Backup manager is blocked and cannot process other backup operations - Resources held by waiting coroutine are not released - No timeout mechanism to recover automatically ### Workarounds Currently no known user-facing workarounds. The backup does complete in Supervisor, but: - HA Core is unaware of completion - Backup is not registered in HA Core's backup manager - Backup cannot be accessed through HA Core UI - HA Core backup state must be manually reset ## Root Cause Assessment _(More conjecture from here on down that I can't fairly evaluate removed.)_ ### What version of Home Assistant Core has the issue? 2025.10.3 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Backup ### Link to integration documentation on our website _No response_ ### Diagnostics information [config_entry-backup-01K661PAHTFFV70GSA109ZJ7NN.json](https://github.com/user-attachments/files/23076861/config_entry-backup-01K661PAHTFFV70GSA109ZJ7NN.json) ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information _No response_

github.com/home-assistant/core

Backups fail due to lack of space without explanation

opened 04:40PM - 25 Feb 25 UTC

Obioban

no-stale integration: backup

### The problem Never had any issues with HA backup, until the revamp. Since th…en I have not had a single successful backup. To try to limit the scope of the issue, and isolate where the problem is, I tried turning off all the optionals-- media, add ons, encryption. No improvement. Is there some better way to diagnose this? It's been over a month now since I've had a successful backup (was hoping a path release would fix it), and I'm starting to get uncomfortable. HAOS running on a Pi5. Backing up to a synology. (semi related side note: it would be great if we could back up to an SD card installed in the Pi's SD card slot with HAOS). ### What version of Home Assistant Core has the issue? core-2025.2.5 ### What was the last working version of Home Assistant Core? 2025.1.X ### What type of installation are you running? Home Assistant OS ### Integration causing the issue none ### Link to integration documentation on our website none ### Diagnostics information _No response_ ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information _No response_

github.com/home-assistant/core

Backup (to HA Cloud) fails after 2025.12

opened 10:12AM - 10 Dec 25 UTC

1reven

integration: backup

### The problem After 2025.12, I get this whenever I try to run a backup: ```Lo…gger: homeassistant.components.backup Source: components/backup/config.py:571 integration: Backup (documentation, issues) First occurred: December 7, 2025 at 05:05:40 (4 occurrences) Last logged: 05:17:52 Error creating backup: Error creating backup: 'BackupManager.do_backup_partial' blocked from execution, system is not running - freeze ``` This occurs for automatic backups to my NAS and HA Cloud, but **also when running a minimal backup (without history) to only HA Cloud.** My latest backup was from the beta, I tried removing that, but didn't help. I also saw a huge spike in diskread from InfluxDB (1GB) this night at the same time as the backup would have tried to run, not sure if it is related. ### What version of Home Assistant Core has the issue? core-2025.12.1 ### What was the last working version of Home Assistant Core? core-2025.12.02b ### What type of installation are you running? Home Assistant OS ### Integration causing the issue _No response_ ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt Logger: homeassistant.components.backup Source: components/backup/config.py:571 integration: Backup (documentation, issues) First occurred: December 7, 2025 at 05:05:40 (4 occurrences) Last logged: 05:17:52 Error creating backup: Error creating backup: 'BackupManager.do_backup_partial' blocked from execution, system is not running - freeze ``` ### Additional information _No response_

cromelex · December 15, 2025, 8:22am

Thanks for the list. I’m going to look into it as my overnight backup is showing “uploading” again.
Looks like it successfully uploaded to NAS and Home Assistant Cloud so this might relate specifically to the new Backblaze integration.

Edit: or this might well relate to the fact that I added a new clan network interface. Saw this mentioned on one of the issues as well.

Maybe bad timing on my end as all 3 things I changed on my end happened in the same couple of days the issue started, so I can’t quite point out which is causing the issue.

cromelex · December 20, 2025, 9:35am

After a few more automated backups, the issue seems to only happen once I add Backblaze as a target destination.

Manual backups do upload so it’s oddly specific.

For the benefit of anyone who might have the same issue, literally toggling off Backblaze as a destination target for the automated backup makes it work.
No need to disable or do anything to the automation.

I’m going to try and gather a bit more details after Christmas and open a GitHub issue.

FlorianKempenich · December 21, 2025, 12:51am

I have the same issue with the Synology DSM backup location. It was working fine until 3 days ago.

cromelex · January 12, 2026, 4:21pm

Well, my issue (specific to Backblaze B2) seems to have been fixed in 2026.1.1 based on this: Add asyncio-level timeout to Backblaze B2 uploads by ElCruncharino · Pull Request #160468 · home-assistant/core · GitHub

Edit: it seems the issue isn’t actually fixed, my upload is still hanging.

Native HA Backups - Hanging on Uploading to locations

The native HA Backups is Hanging on Uploading to locations.

Observations and Settings

STEPS THAT FAILED

STEPS THAT WORKED

1. Identify the stuck backup

2. Delete or force-remove it

3. Restart Home Assistant Core (if backup job is ghosted)

3. Check Backup has failed

4. Check Restart is Working

5. Should be All OK