I have been struggling with this for weeks now. Scoured Reddit, Github, and Dischord as well as everything I could find on community.home-assistant.io. Still no luck. Most recently, I ran “hassio su repair” which, contrary to the “Command completed successfully” message on the CLI, generated the following logs:
19-11-24 22:19:34 INFO (MainThread) [hassio.hassos] Repair HassOS CLI 14
19-11-24 22:19:34 INFO (SyncWorker_6) [hassio.docker.interface] Pull image homeassistant/armv7-hassio-cli tag 14.
19-11-24 22:19:49 ERROR (SyncWorker_6) [hassio.docker.interface] Can't install homeassistant/armv7-hassio-cli:14 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)").
19-11-24 22:19:49 ERROR (MainThread) [hassio.hassos] Repairing of HassOS CLI fails
19-11-24 22:19:49 INFO (MainThread) [hassio.supervisor] Repair Supervisor 192
19-11-24 22:19:49 INFO (MainThread) [hassio.core] Finished repairing of Hass.io Environment
I have seen suggestions that it might be a memory issue although I am dubious of that explanation as it is a brand new RPi without anything else running on it.
I have also seen that I need to forward port 443 on my router to port 8123. I am not clear on this either as I can access the GUI at “hassio.local:8123” although I am not sure it is actually able to receive external traffic on that port. Further, I am on AT&T/Uverse and their routers reserve port 443.
Any suggestions as to how to resolve this problem?
Mixed issues here. What was the original error in the logs after a failed update?
External access to your server is not related. If you’re accessing it locally no ports need to be forwarded. So you can save that one for later. Your server should still be able to get updates and pull down other addons.
The repair command is used to fix a specific docker related issue that can crop up with the overlay. If you can still access the frontend, try to install an addon, and if it fails go to the Hassio > system page and check for an error and share it here.
Thanks, @cogneato. I’ve posted a couple different blegs for help on the various platforms and you actually responded to the first one which was on Discord. Following are the logs I posted then from the “System” page of the GUI:
19-11-10 00:42:26 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.101.2
19-11-10 00:42:26 INFO (SyncWorker_6) [hassio.docker.interface] Update image homeassistant/raspberrypi4-homeassistant:0.101.1 to homeassistant/raspberrypi4-homeassistant:0.101.2
19-11-10 00:42:26 INFO (SyncWorker_6) [hassio.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 0.101.2.
19-11-10 00:42:41 ERROR (SyncWorker_6) [hassio.docker.interface] Can't install homeassistant/raspberrypi4-homeassistant:0.101.2 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)").
19-11-10 00:42:41 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
19-11-10 00:49:06 INFO (SyncWorker_11) [hassio.docker.interface] Pull image homeassistant/armv7-addon-configurator tag 3.6.
19-11-10 00:49:21 ERROR (SyncWorker_11) [hassio.docker.interface] Can't install homeassistant/armv7-addon-configurator:3.6 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)").
...
20-04-26 00:39:27 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 219
20-04-26 00:39:27 INFO (SyncWorker_2) [supervisor.docker.interface] Pull image homeassistant/armv7-hassio-supervisor tag 219.
20-04-26 00:46:10 ERROR (SyncWorker_2) [supervisor.docker.interface] Can't install homeassistant/armv7-hassio-supervisor:219 -> 500 Server Error: Internal Server Error ("error parsing HTTP 408 response body: invalid character '<' looking for beginning of value: "<html><body><h1>408 Request Time-out</h1>\nYour browser didn't send a complete request in time.\n</body></html>\n\n"").
20-04-26 00:46:10 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor fails!
20-04-26 00:46:10 CRITICAL (MainThread) [supervisor.core] Can't update supervisor! This will break some Add-ons or affect future version of Home Assistant!
This is on raspberry Pi 4.
I have also tried
ha su repair
ha su update
With the same error.
~ $ ha info
arch: armv7
channel: stable
hassos: "3.13"
homeassistant: 0.108.3
hostname: homeassistant
logging: info
machine: raspberrypi4
supervisor: "217"
supported_arch:
- armv7
- armhf
timezone: Australia/Sydney
Hello, same situation here.I have stopped being able to update the system, the addons or install any new addon. The error is the same as that indicated by jorourke.
I have had power outages and I assumed that it would have been corrupted, but right now with a clean installation, I still cannot install any addon to start configuring:
20-04-26 11:02:23 INFO (MainThread) [supervisor.ingress] Load 0 ingress session
20-04-26 11:02:23 INFO (MainThread) [supervisor.secrets] Load Home Assistant secrets: 1
20-04-26 11:02:23 INFO (MainThread) [__main__] Run Supervisor
20-04-26 11:02:23 INFO (MainThread) [supervisor.api] Start API on 172.30.32.2
20-04-26 11:02:23 INFO (MainThread) [supervisor.utils.gdbus] Call de.pengutronix.rauc.Installer.Mark on /
20-04-26 11:02:23 INFO (MainThread) [supervisor.hassos] Rauc: A - marked slot kernel.0 as good
20-04-26 11:02:23 INFO (MainThread) [supervisor.addons] Phase 'initialize' start 0 add-ons
20-04-26 11:02:23 INFO (MainThread) [supervisor.core] Supervisor reboot detected
20-04-26 11:02:23 INFO (MainThread) [supervisor.tasks] All core tasks are scheduled
20-04-26 11:02:23 INFO (MainThread) [supervisor.hwmon] Started Supervisor hardware monitor
20-04-26 11:02:23 INFO (MainThread) [supervisor.core] Supervisor is up and running
20-04-26 11:02:23 INFO (MainThread) [supervisor.host.info] Update local host information
20-04-26 11:02:23 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-04-26 11:02:23 INFO (MainThread) [supervisor.host.services] Update service information
20-04-26 11:02:23 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-04-26 11:02:23 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-04-26 11:02:23 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-04-26 11:02:38 WARNING (MainThread) [supervisor.tasks] Watchdog found a problem with Home Assistant Docker!
20-04-26 11:02:38 INFO (SyncWorker_9) [supervisor.docker.interface] Start homeassistant/raspberrypi4-homeassistant
20-04-26 11:02:59 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-04-26 11:05:19 INFO (SyncWorker_9) [supervisor.docker.interface] Pull image homeassistant/armv7-addon-samba tag 9.2.0.
20-04-26 11:05:34 ERROR (SyncWorker_9) [supervisor.docker.interface] Can't install homeassistant/armv7-addon-samba:9.2.0 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)").
I see there is an alert with Home Assistant Docker, but I don’t know if it is related
Raspberry Pi 4 with hassos_rpi4-3.13.img.gz
I don’t know what to check, can anyone give us any idea?
@jibnacho I think the problem might be that the base version of Hassos on the rpi4 is broken. You need to go in an override the MTU size for the main ip link interface.
Eg.
ssh ssh -p 22222 [email protected]
ha > login
ip link list
ip link set dev eth0 mtu 900
nmcli con reload
I had the similar problem after i did a fresh installed of HA in VM where i can’t install any addon. I followed your instruction to set the MTU to 900, and it resolved my problem. However, i have questions regarding the MTU settings.
When i checked my router, the MTU is set to 1480. Does that mean i have to set the MTU in Hassos to less than 1480? Initial MTU setting in Hassos is 1500.
Also, i noticed the MTU setting in Hassos seems to always default to 1500 after i rebooted, even though i have set it to 900 before rebooting. I did the nmcli con reload after changing the MTU but result still the same.
)