Whenever I update a Generic Hassio installation, I always see this error. The update continues and is a success, so I have learn’t to ignore it, but why does it appear?
I’m running this with an SSL certificate installed for a subdomain and the NGINX Home Assistant SSL proxy Add-on installed.
Have the same issue and setup, but running Nginx reverse proxy on a separate server.
Has anyone else seen this issue? Can’t seem to find a way to solve it 
I am also getting this error. Just started fairly recently. So just started digging but looks to be an issue between nginx (which i run on a different box) reverse proxy and my hassio setup.
I’m getting the same error. Any idea how to solve it?
Also same Error here, HA is running behind nginx proxy with Lets Encrypt certificate.
Did anyone manage to do the update?
Same issue here. using the Nginx plugin running on pi4. Any fixes yet? One difference for me, it doesn’t update my version. If I log in from the local network using 192.168.1.111 it works and I don’t get the error.
Getting the same issue. Mine did upgrade if you just let it sit. Been seeing it for a while now.
Here is my supervisor log
20-03-23 17:23:32 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.107.5
20-03-23 17:23:32 INFO (SyncWorker_4) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.106.6 to homeassistant/qemux86-64-homeassistant:0.107.5
20-03-23 17:23:32 INFO (SyncWorker_4) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.107.5.
20-03-23 17:25:37 INFO (MainThread) [supervisor.host.info] Update local host information
20-03-23 17:25:37 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
20-03-23 17:25:38 INFO (MainThread) [supervisor.host.services] Update service information
20-03-23 17:25:38 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
20-03-23 17:25:39 INFO (MainThread) [supervisor.host.network] Update local network DNS information
20-03-23 17:25:39 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
20-03-23 17:25:39 INFO (MainThread) [supervisor.host.sound] Update PulseAudio information
20-03-23 17:27:40 INFO (SyncWorker_4) [supervisor.docker.interface] Stop homeassistant application
20-03-23 17:28:08 INFO (SyncWorker_4) [supervisor.docker.interface] Clean homeassistant application
20-03-23 17:28:09 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-03-23 17:28:12 INFO (SyncWorker_1) [supervisor.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.107.5
20-03-23 17:28:57 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-03-23 17:28:57 INFO (MainThread) [supervisor.homeassistant] Successful run Home Assistant 0.107.5
20-03-23 17:29:08 INFO (SyncWorker_4) [supervisor.docker.interface] Cleanup images: ['homeassistant/qemux86-64-homeassistant:0.106.6']
20-03-23 17:38:57 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
I am running Nginx also. Do you think the supervisor (new name) could be killing the it’s process as part of the update, then the internet connection is down till the update is finished?
Should we open a ticket?
Same issue…
@penright did you manage to fix it or did you manage to open the official ticket?
Thanks.
same for me for the 0.108.8 update.
I need to reboot my pi afther all update
Same issue with Nginx and Letsencrypt Add-ons installed.
HassOS 3.13
Supervisor 222
Ha 0.109.5 to 0.109.6
Thing is that the update continues, just have to be patient.
Same issue here. Update eventually goes through. Using Nginx Proxy Manager and Letsencrypt Add-on as well.
Had the same issue, except with an OS update, oddly enough HA updates don’t seem to have this issue for me. As a work around I found you can SSH into the host, and run the following command, which will apply the update and reboot the host with no nginx errors:
ha os update
I assume the same would work for HA updates, but with:
ha core update
Not a solution, but it is a work around.
Same issue, but it does seem to update regardless. 
I’ve got the same error with “Nginx Proxy Manager” when I make a snapshot.
So I’ve created this issue :
I had same problem.
Workaround I found. I accessed Hass.io using internal IP address and I update from there.
The fix outlined below worked for me.
Specifically, I added this section to my nginx configuration and validated via snapshot & upgrade of HA.
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 600;