Core Update 2026.5.1 will not update

[SmileyRG]

The problem

Here is the supervisor log after running the core update:
2026-05-10 12:16:00.409 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/green-homeassistant:2026.5.0 to ghcr.io/home-assistant/green-homeassistant:2026.5.1
2026-05-10 12:16:00.843 WARNING (MainThread) [supervisor.docker.manifest] Failed to get token from https://ghcr.io/token: 403
2026-05-10 12:16:00.923 WARNING (MainThread) [supervisor.docker.manifest] Failed to fetch manifest for ghcr.io/home-assistant/green-homeassistant:2026.5.1 - 401
2026-05-10 12:16:00.924 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/green-homeassistant with tag 2026.5.1.
2026-05-10 12:16:01.584 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/green-homeassistant:2026.5.1: [403] Head "https://ghcr.io/v2/home-assistant/green-homeassistant/manifests/2026.5.1": denied: denied
2026-05-10 12:16:01.586 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
2026-05-10 12:16:01.663 INFO (MainThread) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/green-homeassistant:2026.5.1']

worked with CHAPGPT and ran command and could see both 2026.5.0 and 2026.5.1 but after restart the system would not switch and load 2026.5.1

What version of Home Assistant Core has the issue?

2026.5.0 to 2026.5.1

What was the last working version of Home Assistant Core?

2026.5.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

None

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

ha core info:
➜  ~ ha core info
arch: aarch64
audio_input: null
audio_output: null
backups_exclude_database: false
boot: true
duplicate_log_file: false
image: ghcr.io/home-assistant/green-homeassistant
ip_address: xxx.xx.xx.x
machine: green
port: 8123
ssl: false
update_available: true
version: 2026.5.0
version_latest: 2026.5.1
watchdog: true

HA Supervisor Info:
arch: aarch64
auto_update: true
channel: stable
country: US
debug: false
debug_block: false
detect_blocking_io: false
diagnostics: true
feature_flags:
  supervisor_v2_api: false
  unix_socket_core_api: false
healthy: true
ip_address: xxx.xx.xx.x
logging: info
supported: true
timezone: America/New_York
update_available: false
version: 2026.04.2
version_latest: 2026.04.2
wait_boot: 5

CHATGPT was concerned that supervisor version was not in the 2026.5 range.

Additional information

CHATGPT seemed to be in a loop. When I performed the last supervisor update, I had to create a token in Github which recently expired. I updated the token but not sure if this has anything to do with the current issue with core not updating to 2026.5.1. Thru CHATGPT I was able to pull down the 2026.5.1 and ran an command that showed both files (2026.5.0 and 2026.5.1) were present but it seemed that ha would not switch to the new core on restart. Thanks in advance for any assistance.

[grumpyvwman]

Mine does the same have you found how to fix this

[SmileyRG]

Sorry but no. Until your comment, I felt it was just me since I did not see anyone else with the same issue. Usually, I am not the only one with the issue.

I have tried ChatGPT but at times it seems the suggestions go in a circle. The last time it stated the issue is my ISP (TMobile Home Internet), but I have been using the same internet / ISP for about 2 yrs. Not sure I trust the answer. The proposed solution is to use VPN bridge, but it would require hardware which I do not have and would need to purchase ($100).

If I am understanding the responses I receive from SSH/Terminal to the commands that AI suggests, I can get the images to download and I can see both Images, but it does not 'switch' to the 2026.5.1 image at restart.

I do not understand the full handshake that is going on during a 'normal' core update, but the token denied message in supervisor log seems to indicate a connection failure with GitHub yet with commands in SSH/Terminal and can get the image download to work. Maybe the manual restart after the manual download of the images causes another 'token' check which fails but I am not sure what that handshake is.

Please let me know if you find anything.

[WatsonDue2]

It seems an issue with dns or ipv6. In my case, I was able to update my HA disabling AdGuard.

[SmileyRG]

I disabled ipv6 and set dns to 1.1.1.1 and 8.8.8.8. No help. I will check but I do not believe I run AdGuard. Thanks for the suggestions.

[WatsonDue2]

It might be some other filter: I use AdGuard, but it might be PiHole or another firewall or ad blocker.
Hope you'll be able to solve it soon!

[SandroC01]

I'm also having trouble updating.

Supervisor log:

2026-05-13 10:27:09.826 INFO (MainThread) [supervisor.host.network] Updating local network information
2026-05-13 10:27:48.925 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2026-05-13 10:27:48.946 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2026.5.1
2026-05-13 10:27:48.947 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2026.5.0 to ghcr.io/home-assistant/qemux86-64-homeassistant:2026.5.1
2026-05-13 10:27:49.954 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2026.5.1.
2026-05-13 10:27:50.928 INFO (MainThread) [supervisor.docker.manager] Stopping homeassistant application
2026-05-13 10:27:51.058 INFO (MainThread) [supervisor.api.proxy] [d5369777_music_assistant] Home Assistant WebSocket API closed
2026-05-13 10:28:20.500 INFO (MainThread) [supervisor.docker.manager] Cleaning homeassistant application
2026-05-13 10:28:22.160 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2026-05-13 10:28:22.525 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2026.5.1
2026-05-13 10:28:22.525 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2026-05-13 10:28:27.538 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
2026-05-13 10:28:27.538 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
2026-05-13 10:28:27.538 INFO (MainThread) [supervisor.resolution.module] Create new issue update_rollback - core / None
2026-05-13 10:28:27.540 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2026.5.0
2026-05-13 10:28:27.540 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2026.5.1 to ghcr.io/home-assistant/qemux86-64-homeassistant:2026.5.0
2026-05-13 10:28:46.596 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2026.5.0.
2026-05-13 10:28:47.653 INFO (MainThread) [supervisor.docker.manager] Cleaning homeassistant application
2026-05-13 10:28:47.719 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
2026-05-13 10:28:48.064 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2026.5.0
2026-05-13 10:28:48.065 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2026-05-13 10:29:06.896 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2026-05-13 10:29:06.941 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2026-05-13 10:29:08.136 INFO (MainThread) [supervisor.homeassistant.api] Connected to Core via TCP http://172.30.32.1:8123
2026-05-13 10:29:08.136 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='NOT_RUNNING', offline_db_migration=False)
2026-05-13 10:29:28.965 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqtt_user'
2026-05-13 10:29:29.063 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
2026-05-13 10:30:58.939 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='RUNNING', offline_db_migration=False)
2026-05-13 10:30:58.939 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
2026-05-13 10:30:58.940 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2026.5.0
2026-05-13 10:31:56.152 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2026-05-13 10:31:56.153 INFO (MainThread) [supervisor.api.proxy] WebSocket access from d5369777_music_assistant
2026-05-13 10:31:56.161 INFO (MainThread) [supervisor.api.proxy] [d5369777_music_assistant] Home Assistant WebSocket API proxy running

[sutudu]

Same here. Error updating from 2026.5.0 to 2026.5.1 on a HA OS on Raspberry pi 4:
2026-05-14 09:46:31.476 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/raspberrypi4-64-homeassistant with version 2026.5.1
2026-05-14 09:46:31.476 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
2026-05-14 09:46:41.513 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
2026-05-14 09:46:41.514 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
2026-05-14 09:46:41.519 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2026.5.0

[agners]

@SandroC01 @sutudu can you share the Core logs around the same time? This typically means the Supervisor detected that Core simply stopped, or was not able to connect to Home Assistant Core after the upgrade, so it went safe and rolled back.

Your cases are different though, and probably warrant a separate issue since the original report does not report a rollback, but an issue downloading the update itself.

[sutudu]

Just tried again. Here are the core logs

latest.txt
Please let me know if I should create a new one

[SandroC01]

@agners
Maybe this part?

Found 2 non-daemonic threads.
[12:39:56] INFO: Home Assistant Core finish process exit code 0
[12:39:56] INFO: Home Assistant Core service shutdown
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
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 12, in
from .backup_restore import restore_backup
File "/usr/src/homeassistant/homeassistant/backup_restore.py", line 17, in
from .const import version as HA_VERSION
ImportError: cannot import name 'version' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)
[12:40:01] INFO: Home Assistant Core finish process exit code 1
[12:40:01] INFO: Home Assistant Core service shutdown
s6-rc: info: service legacy-services: stopping
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

[SmileyRG]

With assistance from someone on Discord, I performed a reset of HA Green and then restored a backup that was made prior to the reset. Supervisor did update to 2026.05.0 but Core is still stuck on 2026.5.0 and will not update. The error in the supervisor log appears to be the same as before. I removed the router VPN that I had setup for HA and also re-disabled ipv6 and set ipv4 DSN to 8.8.8.8 and 1.1.1.1 I have performed several reboots (not restarts) and Core update still fails with the same messages. Does anyone have any suggestions?

[SandroC01]

I was able to update to version 2026.5.2 without any problems.

[agners]

@SandroC01 not sure where this issue stemmed from, almost looks like the Core update corrupted locally on your end 🤷 Glad you've been able to resolve your issue. Seems unrelated to the issue OP posted though.

@sutudu that too doesn't look like a download issue like OP. Some upnp config entry got stuck. Please open as new issue if you still encounter this.

[agners]

@SmileyRG wrt VPN, did you reroute all Internet traffic? GHCR uses fastly CDN afaik.

My best guess is still that your ISP/internet connectivity somehow messes with GitHub container registry downloads.