Unable to update to HAOS 18.3

Hello HA community. Today I tried to upgrade to Home Assistant Operating System 18.3 from 18.2 and got the error below.

Has anyone else experienced this?

Failed to perform the action update/install. Error updating Home Assistant Operating System: Can't fetch OTA update from https://os-artifacts.home-assistant.io/18.3/haos_generic-x86-64-18.3.raucb: 400, message='Got more than 8190 bytes when reading: b"default-src \\'none\\'; base-uri \\'self\\'; child-src github.githubassets.com github.com/assets-cdn/worker/...".', url='https://github.com/home-assistant/operating-system/releases/download/18.3/haos_generic-x86-64-18.3.raucb

Thanks for posting the link and looks like a wider issue. I’ll hold off on the update until a solution is found.

or try to update from the CLI or SSH

Yup just ran into the same issue today. Tried to update Home Assistant OS on my Raspberry Pi 4 from 17.3 to 18.3 and got this error. Hoping for a fix. :grin:

From the built in Terminal raises the same error:

[core-ssh ~]$ ha os update
Processing… Done.

Error: Can’t fetch OTA update from https://os-artifacts.home-assistant.io/18.3/haos_generic-x86-64-18.3.raucb: 400, message='Got more than 8190 bytes when reading: […]

Following the link does download something. It seems that SSH from outside might be the workaround? Or wait for a fix upstream…

Wait for a fix.

And how should this fix reach us?

I’m not complaining, but I had 9 updates today including HACS, Apps and HA 2026.10.4 and they all went off without a hitch. I did the HA update last, which I realized after the fact I should not have in this case. I am reading multiple posts about broken updates the last 24 hours and wonder why I didn’t have any issues.

I do also wonder, could be i.e browser/browser-extension related, generous “Content-Security-Policy” etc :grin:
I.E ive notice other “issues” with uBlock Origin enabled in HA, so this i always has disabled on my HA-Address, and im running HTTP installs only

On the other hand, i could just have installed “just in time” before Github raised their settings, and as You “just in time” after they “reverted” their settings ( as they seems to have, maybe just before HA relased 2026.10.4 )