Getting this error. Any thoughts?
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/16.1/haos_ova-16.1.raucb: Response payload is not completed: «ContentLengthError: 400, message='Not enough data to satisfy content length header!>. SSLError(1, ‘[SSL] record layer failure (_ssl.c:2648)’)
Hello brandonballard1,
What server are you running. The Yellow has had some difficulties in some cases with this.
Running in Hyper V. Everything works great other than the OS update, even the core updates.
Having the same issue on a RPi CM4 build, seems to download most of the update (https://os-artifacts.home-assistant.io/16.1/haos_rpi4-64-16.1.raucb) but then fails with the “Can’t fetch OTA” error
Sounds like the connection got interrupted. Either it tried to renegotiate TLS or something mangled the stream and the TLS API just gave up. I’d suggest getting a packet capture and seeing which of those it is. It’s more likely the latter. I’m not sure exactly how this does the download but I’d be suspicious of whether it’s streaming the file to disk or holding in memory. Either way, running out of space in one of those would be a problem of course. Might be worth proactively checking those out (disk space, available memory).
I’ve got the exact same error and experience. HA core updates had some trouble too, but with a system reboot the core update did fine (update 7.4 to 8.3). HA OS is not willing to install and I receive the same error:
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/16.1/haos_generic-x86-64-16.1.raucb: Response payload is not completed: <ContentLengthError: 400, message=‘Not enough data to satisfy content length header.’>
Available memory is 92% and diskspace is 99%. The rest I don’t understand of the post of @erict7 
Nearly empty or nearly full? Nearly empty would be surprising to me as you’d need to have a few hundred GB on disk and usually HA is installed on a micro-system (minimal compute, RAM, disk).
You have the same top-level error as the first post, but you haven’t said if you have the same underlying error. Does your message include the “[SSL] record layer failure” as well? You might need/want to turn on debug level logging to get more info.
Has anyone attempted a manual install as referenced in the developer docs? My test system is a VM as opposed to my prod system which is physical so no way to test myself. This method doesn’t require creating a CONFIG USB installer, just a download via curl and install (I assume to the inactive boot slot).
Didn’t use the word available twice, so I understand your question. And yes, it is 99% available diskspace. Not commen, but I started Home Assistant 1,5 years ago on a old system because the lack of a good Pi. Will later change to a Pi 5 or someting.
For me the solutions was to create a seperate policy route for my HA server to route all trafic trought a different netwerk interface. The question remain why it’s only needed for HAOS and not the Core updates, but that’s another topic.