Supervisor connectivity timeout

Configuration
1

My supervisor logs are filled with these warnings.

21-03-04 17:35:07 WARNING (MainThread) [supervisor.host.network] Can't update connectivity information: Error: Timeout was reached

Does anyone have an idea what is causing this? I am also noticing errors when I attempt to update integrations/addon or update the core/supervisor itself. The only way to fix it is to restart the homeassistant host and quickly initiate the update after rebooting the system.

I then get this error when I attempt to update the supervisor.

21-03-04 18:20:01 INFO (SyncWorker_3) [supervisor.docker.interface] Downloading docker image homeassistant/amd64-hassio-supervisor with tag 2021.03.4.
21-03-04 18:20:17 ERROR (SyncWorker_3) [supervisor.docker.interface] Can't install homeassistant/amd64-hassio-supervisor:2021.03.4 -> 500 Server Error for http+docker://localhost/v1.40/images/create?tag=2021.03.4&fromImage=homeassistant%2Famd64-hassio-supervisor: Internal Server Error ("Get "https://registry-1.docker.io/v2/homeassistant/amd64-hassio-supervisor/manifests/2021.03.4": Get "https://auth.docker.io/token?scope=repository%3Ahomeassistant%2Famd64-hassio-supervisor%3Apull&service=registry.docker.io": context deadline exceeded").
21-03-04 18:20:17 ERROR (MainThread) [supervisor.supervisor] Update of Supervisor failed!
21-03-04 18:20:17 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.UPDATE_FAILED - ContextType.SUPERVISOR / None
1 Like
2

Try to reboot system.

1 Like
3

I have tried that multiple times, with no success.

1 Like
5

I’m seeing the same thing in a new clean installation of HomeAssistant OS. No addons or system updates work, all times out or just stalls until I reboot. The installation itself and all integrations I have tested seem to work though, this affects only the supervisor for me.
I’m using hassos_rpi3-64-5.13.img.xz on a RaspberryPi3A+

6

I have this exact issue on the same hardware!

7

I’ve been getting this for weeks as well. I downloaded a new VHD and restored from a backup and after a few hours the problem returned.

About a week later I brought down another VHD and created a new server and instead of restoring from backup I decided to build new. Without any crazy modifications done to the new system it started logging the same message. I was probably only 1/3 of the way to completing the new build. Outside of regular addons like MQTT, SAMBA I only had the Blue Iris custom addon from HACs running.

THis also prevents me from updating until I reboot and the message goes away. Someone mentioned it might be a time issue on the server, but that all looked good.