rebooting after ha supervisor options --auto-update=false wont change anything. If someone have HA on docker, can try to login to CLI with generated in github token, and try to update again.
@mailmafernandez @Moe1 @consultorjaison @nle @BertQuodge @piedro @Simon16 @DrThomas @Quax1507
Guys, do some effort to read the important stuff in a thread and the Solution!
1 Like
@jayjay @GilZock @Cirion @a33z @Isengo1989 @malosaa @stjimmy93 @KingRichard @thebuzz @Alxkk88
Guys, do some effort to read the important stuff in a thread and the Solution!
2 Likes
@BobWin @wbravin @niouflex49 @SharkyFive @MRK747 @kooswillem @stridger @brad.trout
Guys, do some effort to read the important stuff in a thread and the Solution!
After rebooting, the system restarted but still with the same problem
I got 2 different errors wen i want to upgrade to 2024.11.3.
Not at the same time but the error changed from the first to the second after a while.
Actie update/install kon niet warden uitgevoerd. Error updating Home Assistant Supervisor: Update of Supervisor failed: Can't install ghcrio/home-assistant/amd64-hassio-supervisor:2024.11.3: 500 Server Error for http+dockerillocalhost/v1.47/images/createotag=2024.11.3&fromlmage=ghcrio%2Fhome-assistant%2Famd64-hassio-supervisor&platform=linux%2Famd64 Internal Server Error (loomanyrequests: retry-after: 880.569ps, allowed: 44000/minute')
Actie update/install kon niet worden uitgevoerd. Error updating Home Assistant Supervisor: Update of Supervisor failed: Can't install ghcmo/home-assistant/amd64-hassio-supervisor:2024.11.3 404 Client Error for http+dockerillocalhost/v1.47/images/ghcrio/home-assistant/amd64-hassio-supervisor:2024.11.3/json: Not Found ("No such image: ghcrio/home-assistant/amd64-hassio-supervisor:2024.11.31
Got the same error with both messages - its a GitHub issue so we all need some patience
1 Like
5 Likes
This works, but you’ll need the SSH-addon in order to do it.
PS: You might need to do it repeatedly until the download has completed fully 
'It is a github issue".
Could also be a DDOS attack. Or too many HA instances all re-trying the update causing the downtime?
What does the "retry-after’ mean in this error message? Will it automatically retry after 475µs?
(“toomanyrequests: retry-after: 475.287µs, allowed: 44000/minute”)
I assume it’s just a response from github informing that this page is rate limited.
Maybe I just don’t understand the flow. But if the update fails because of GitHub why is the supervisor getting affected by it. Can’t it just stay on previous version until GitHub allows connections again. ? Just seems strange it breaks the system if it can’t fetch the data needed.
1 Like
Same - i thought I make an error configuring and restored my backup from last night - same issue
[core-ssh ~]$ ha supervisor update
Processing… Done.
Error: Update of Supervisor failed: Can’t install ghcr.io/home-assistant/aarch64-hassio-supervisor:2024.11.3: 404 Client Error for http+docker://localhost/v1.47/images/ghcr.io/home-assistant/aarch64-hassio-supervisor:2024.11.3/json: Not Found (“No such image: Package aarch64-hassio-supervisor · GitHub”)
I assume what you are saying is that once the load issue at gethub is fixed the update will start working?
Is that what your saying? Because just saying it is a gethub issue makes me want to ask how do I fix that?
It doesn’t work with SSH Addon too.
Error: Update of Supervisor failed: Can’t install ghcr.io/home-assistant/aarch64-hassio-supervisor:2024.11.3: 500 Server Error for http+docker://localhost/v1.47/images/create?tag=2024.11.3&fromImage=ghcr.io%2Fhome-assistant%2Faarch64-hassio-supervisor&platform=linux%2Farm64: Internal Server Error (“toomanyrequests: retry-after: 330.597µs, allowed: 44000/minute”)
I think it error is about new system update
Today I have a day off and wanted to run a new installation. After getting an error I ended up here.
So it’s more of a github issue.
same for me!
