Cannot update Error: 502: Bad Gateway #617

dany250 · 2020-04-01T23:44:48Z

HassOS release with the issue:

currently running version 3.11
Supervisor logs:

20-04-01 22:43:23 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:43:23 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:43:23 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:43:28 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:43:28 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:43:28 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:43:33 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:43:33 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:43:33 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:43:38 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:43:38 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:43:38 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:43:41 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-04-01 22:43:43 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:43:43 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:43:43 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
20-04-01 22:44:53 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
20-04-01 22:44:53 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
20-04-01 22:44:57 ERROR (MainThread) [supervisor.utils.json] Can't read json from /data/addons/git/5f2994cf/repository.json: [Errno 2] No such file or directory: '/data/addons/git/5f2994cf/repository.json'
20-04-01 22:44:57 WARNING (MainThread) [supervisor.store.data] Can't read repository information from /data/addons/git/5f2994cf/repository.json
20-04-01 22:44:57 INFO (MainThread) [supervisor.store] Load add-ons from store: 65 all - 0 new - 0 remove
20-04-01 22:45:27 INFO (SyncWorker_15) [supervisor.docker.interface] Stop addon_a0d7b954_nodered application
20-04-01 22:45:27 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
20-04-01 22:45:41 INFO (SyncWorker_15) [supervisor.docker.interface] Clean addon_a0d7b954_nodered application
20-04-01 22:46:10 INFO (SyncWorker_12) [supervisor.docker.addon] Start Docker add-on hassioaddons/node-red-armv7 with version 6.1.4
20-04-01 22:46:11 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_nodered
20-04-01 22:46:14 INFO (MainThread) [supervisor.api.security] /dns/info access from a0d7b954_nodered
20-04-01 22:46:19 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:62289 ssl:None [Connection refused]
20-04-01 22:46:37 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for mqttuser2
20-04-01 22:46:37 INFO (MainThread) [supervisor.auth] Success login from mqttuser2
20-04-01 22:46:41 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:46:41 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:46:41 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
20-04-01 22:48:49 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:0 is not WSMsgType.TEXT
20-04-01 22:48:49 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
20-04-01 22:48:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:48:54 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:48:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
20-04-01 22:56:44 INFO (SyncWorker_11) [supervisor.docker.interface] Restart homeassistant/raspberrypi4-homeassistant
20-04-01 22:56:49 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str
20-04-01 22:56:49 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
20-04-01 22:56:52 ERROR (MainThread) [supervisor.homeassistant] Error on call https://172.30.32.1:8123/api/services/homeassistant/restart: None
20-04-01 22:56:52 ERROR (MainThread) [supervisor.api.proxy] Error on API for request services/homeassistant/restart
20-04-01 22:56:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:56:54 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:56:54 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:56:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:56:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:56:59 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:04 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:04 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:04 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:09 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:09 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:09 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:14 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:14 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:14 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:19 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:19 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:19 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:24 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:24 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:24 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:29 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:29 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:29 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:34 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:34 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:34 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:38 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for mqttuser
20-04-01 22:57:38 ERROR (MainThread) [supervisor.homeassistant] Error on call https://172.30.32.1:8123/api/: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]
20-04-01 22:57:38 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-04-01 22:57:38 INFO (MainThread) [supervisor.auth] Cache hit for mqttuser
20-04-01 22:57:39 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:39 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:39 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:44 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:44 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:44 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:49 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:49 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:49 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:54 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:54 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:57:54 ERROR (MainThread) [supervisor.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
20-04-01 22:57:58 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-04-01 22:57:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-04-01 22:57:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-04-01 22:58:00 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
20-04-01 23:06:34 INFO (MainThread) [supervisor.hassos] Fetch OTA update from https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi4-3.12.raucb
20-04-01 23:16:34 WARNING (MainThread) [supervisor.hassos] Can't fetch versions from https://github.com/home-assistant/operating-system/releases/download/3.12/hassos_rpi4-3.12.raucb: 
20-04-01 23:16:34 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<HassOS.update() done, defined at /usr/src/supervisor/supervisor/hassos.py:129> exception=HassOSUpdateError()>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/hassos.py", line 140, in update
    int_ota = await self._download_raucb(version)
  File "/usr/src/supervisor/supervisor/hassos.py", line 92, in _download_raucb
    raise HassOSUpdateError()
supervisor.exceptions.HassOSUpdateError

Journal logs:

Kernel logs:

Description of problem:
it shows ERROR:502: Bad Gateway every time i try to update from 3.11

The text was updated successfully, but these errors were encountered:

Semag · 2020-05-22T05:00:48Z

I also have this issue, but am on 3.12. Haven't been able to upgrade the OS since 3.13 came out,.

Mediacj · 2020-05-30T08:25:34Z

Me to same problem also from 3.12 to 4.8

ctm514 · 2020-06-01T22:28:07Z

Eu também estou com esse problema... versão 3.13 pra 4,8. Alguém sabe como resolver?

Bettinaglio · 2020-06-02T04:19:54Z

Same problem here when trying to upgrade from 3.13 to 4.8. Any solution?

Systemzustand
arch armv7l
chassis embedded
dev false
docker true
hassio true
host_os HassOS 3.13
installation_type Home Assistant
os_name Linux
os_version 4.19.114-v7
python_version 3.7.7
supervisor 226
timezone Europe/Rome
version 0.110.4
virtualenv false
Lovelace
dashboards 1
mode storage
resources 4
views 5

Semag · 2020-06-02T16:07:18Z

I ran a tcpdump while i ran the os update and it seems to grab the entire upgrade, then fails after that - there is definitely a ton of traffic passing. Is there anyway to manually download the OS upgrade an upgrade in place using a local file?

Example:

09:06:18.579391 IP homeassistant.home.35306 > s3-1-w.amazonaws.com.https: Flags [.], ack 65872, win 9774, length 0
09:06:18.579624 IP homeassistant.home.35306 > s3-1-w.amazonaws.com.https: Flags [.], ack 67304, win 9767, length 0
09:06:18.658610 IP s3-1-w.amazonaws.com.https > homeassistant.home.35306: Flags [.], seq 67304:70168, ack 1, win 124, length 2864
09:06:18.847574 IP s3-1-w.amazonaws.com.https > homeassistant.home.35306: Flags [.], seq 70168:71600, ack 1, win 124, length 1432
09:06:18.849707 IP homeassistant.home.35306 > s3-1-w.amazonaws.com.https: Flags [.], ack 67304, win 9782, options [nop,nop,sack 1 {70168:71600}], length 0
09:06:18.977519 IP s3-1-w.amazonaws.com.https > homeassistant.home.35306: Flags [.], seq 67304:68736, ack 1, win 124, length 1432
09:06:18.978939 IP homeassistant.home.35306 > s3-1-w.amazonaws.com.https: Flags [.], ack 68736, win 9773, options [nop,nop,sack 1 {70168:71600}], length 0

Semag · 2020-06-02T17:05:14Z

I did a little more digging and the TCP stream from AWS above is terminated by HomeAssistant (RST) - but the network looks good during the whole exchange. So something in the OS is dropping the connection in the middle of upgrade.

Mediacj · 2020-06-02T17:42:28Z

What helped for me was changing the Virtio network device to Intel E1000, reboot Hassos and tried to update again.
I still got the 502 error on the end but in system it tells me version 4.8 is installed and I get no update to 4.8 anymore. At last I changed the network device back to Virtio and all is working normally.

Semag · 2020-06-02T21:23:02Z

@Mediacj - are you running on a virtual machine?

Mediacj · 2020-06-03T09:04:03Z

Oh yes sorry, I am running it as a VM under Proxmox.

Semag · 2020-06-03T16:19:21Z

Thanks @Mediacj - is your adapter set to NAT in the VM? I'm running virtual box, but i have the adapter "bridged" from the host machine, so i can't change the device type right now. I'm going to try playing with changing it to NAT and some other options possibly.

Semag · 2020-06-03T18:34:14Z

@Mediacj - wow that is amazing. It worked!!!

For anyone else finding this, i changed the Virtualbox VM adapter to NAT. Obviously this is going to rip HA off the network and disable SSH access.

I had to login via a VNC window and run 'os update' - but it updated VERY fast, and then rebooted and came up on version 4.8.

I've now moved it back to a bridged ethernet adapter and all is good.

Mediacj · 2020-06-05T07:23:09Z

Ok great! My adapter is bridged to the host.

I just updated to version 4.9 without errors.

XxCabbyoO · 2020-06-07T18:48:23Z

same error 502 bad gateway from 3.13 to 4.9, using rpi4 2gb

after trying again to start the update:

20-06-07 18:40:14 WARNING (MainThread) [supervisor.hassos] Can't fetch versions from https://github.com/home-assistant/operating-system/releases/download/4.9/hassos_rpi4-4.9.raucb: Cannot connect to host github-production-release-asset-2e65be.s3.amazonaws.com:443 ssl:None [Operation timed out]
20-06-07 18:40:59 WARNING (MainThread) [supervisor.hassos] Can't fetch versions from https://github.com/home-assistant/operating-system/releases/download/4.9/hassos_rpi4-4.9.raucb: 
20-06-07 18:40:59 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<HassOS.update() done, defined at /usr/src/supervisor/supervisor/hassos.py:125> exception=HassOSUpdateError()>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/hassos.py", line 136, in update
    int_ota = await self._download_raucb(version)
  File "/usr/src/supervisor/supervisor/hassos.py", line 88, in _download_raucb
    raise HassOSUpdateError()
supervisor.exceptions.HassOSUpdateError

third try: Error: 502: Bad Gateway

any solution?

pvizeli · 2020-06-08T07:12:48Z

Geo-blocking? If yes, you need use maybe an VPN?

XxCabbyoO · 2020-06-08T11:18:41Z

Geo-blocking? If yes, you need use maybe an VPN?

how do you come up with geo blocking? how can that be the reason? Confusing for me
but yes my homeassistant instance runs locally without external access. But could I do other updates?

balloob · 2020-06-08T21:07:42Z

Wait, you've opened issue about that you can't reach the update server but forgot to mention that you're blocking external access in your initial post?

XxCabbyoO · 2020-06-10T14:32:51Z

sorry my fault, getting this error message when updating in the prod environment with external access too, not only in test:

via gui: Error: 502: Bad Gateway

LOG:

20-06-10 14:24:19 INFO (MainThread) [supervisor.hassos] Fetch OTA update from https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi4-4.10.raucb
20-06-10 14:24:45 WARNING (MainThread) [supervisor.hassos] Can't fetch versions from https://github.com/home-assistant/operating-system/releases/download/4.10/hassos_rpi4-4.10.raucb: 
20-06-10 14:24:45 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<HassOS.update() done, defined at /usr/src/supervisor/supervisor/hassos.py:125> exception=HassOSUpdateError()>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/hassos.py", line 136, in update
    int_ota = await self._download_raucb(version)
  File "/usr/src/supervisor/supervisor/hassos.py", line 88, in _download_raucb
    raise HassOSUpdateError()
supervisor.exceptions.HassOSUpdateError

try via terminal:

20-06-10 14:31:06 INFO (MainThread) [supervisor.api.security] /core/update access from core_ssh
20-06-10 14:31:06 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 4.10
20-06-10 14:31:06 INFO (SyncWorker_5) [supervisor.docker.interface] Update image homeassistant/raspberrypi4-homeassistant:0.110.7 to homeassistant/raspberrypi4-homeassistant:4.10
20-06-10 14:31:06 INFO (SyncWorker_5) [supervisor.docker.interface] Pull image homeassistant/raspberrypi4-homeassistant tag 4.10.
20-06-10 14:31:21 ERROR (SyncWorker_5) [supervisor.docker.interface] Can't install homeassistant/raspberrypi4-homeassistant:4.10 -> 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-06-10 14:31:21 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails

SAOPP · 2020-06-11T12:18:53Z

I have exactly the same problem now, I did not see this topic because of the name, and only now I saw a 502 error at my side too.

#738

XxCabbyoO · 2020-06-16T17:00:36Z

today the update from 3.13 to 4.10 suddenly worked. I haven't changed anything

SAOPP · 2020-06-17T11:52:05Z

Thanks, I will try today to update my other instance...

SAOPP · 2020-06-17T23:06:12Z

All fine now!

morfei1 · 2020-06-18T23:15:53Z

I've tried to update the supervisor 3.13 to 4.10 several times without success. The installation was cancelled with message: Error: 502: Bad Gateway. Rpi3b+, HA v0.111.4.

radostint · 2020-06-21T11:31:49Z

I got the same problem here, updating from 3.13 to 4.10. Tried at least 4-5 times but no luck. Every single try I get "Error: 502: Bad Gateway."

Update: Few more tries(think this one was 12th) and it finally updated.

Semag · 2020-06-23T15:55:09Z

FYI - i just did the update again.

Had issues (502 bad gateway) updating the OS. So I repeated my previous process:

Set the virtualmachine network adapter to NAT
Connect via VNC to the console
Issue an ha> os update
HA restarts, reset the network adapter to bridge.

Seems to work like a charm.

watermarkhu · 2020-06-25T14:42:39Z

Same issue from 3.13 to 4.10

watermarkhu · 2020-06-26T12:24:51Z

It may be caused by a time-out due to the long download time (>10 min).
I solved it by performing the update via a USB stick. Instructions here.

You'll need to:

Format a USB to FAT32/EXT4/NTFS and name it CONFIG (all capitals)
Download the correct hassos-xy.raucb for you. You can find the version your device tries to download in the system log.
Place hassos-xy.raucb in the root folder of your USB
Restart your device with the USB plugged in.

XxCabbyoO · 2020-07-06T09:29:01Z

The error reoccurs with the new update from 4.10 to 4.11 :(

Error: 502: Bad Gateway

20-07-06 09:23:55 WARNING (MainThread) [supervisor.hassos] Can't fetch versions from https://github.com/home-assistant/operating-system/releases/download/4.11/hassos_rpi4-4.11.raucb: 
20-07-06 09:23:55 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<HassOS.update() done, defined at /usr/src/supervisor/supervisor/hassos.py:125> exception=HassOSUpdateError()>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/hassos.py", line 136, in update
    int_ota = await self._download_raucb(version)
  File "/usr/src/supervisor/supervisor/hassos.py", line 88, in _download_raucb
    raise HassOSUpdateError()
supervisor.exceptions.HassOSUpdateError

labachev · 2020-07-07T09:20:06Z

Same here with the new update from 4.10 to 4.11

psycmos · 2020-07-08T11:44:22Z

Me too

cpuks · 2020-07-08T20:04:52Z

Same problem - HassOS 4.10 running in VM - can't update, everything else works fine...

balloob · 2020-07-08T23:12:35Z

Please use reactions instead of writing me too's.

facuzestoa · 2020-08-12T19:05:46Z

Same happening from 4.11 to 4.12.
Is there any way to increase this 10 min time-out?

I've finally downloaded the update hassos_rpi4-4.12.raucb , put it in a pen drive and used Import From USB on Supervisor/System/Host System Panel to update the Rpi4.

stale · 2020-10-12T00:09:07Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

olli-dot-dev · 2020-10-20T07:56:59Z

Still having the same problem running a RPI4:

Here's my recent error logs:

20-10-20 07:38:10 INFO (MainThread) [supervisor.hassos] Fetch OTA update from https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_rpi4-4.14.raucb
20-10-20 07:48:10 WARNING (MainThread) [supervisor.hassos] Can't fetch versions from https://github.com/home-assistant/operating-system/releases/download/4.14/hassos_rpi4-4.14.raucb: 
20-10-20 07:48:10 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-329133' coro=<HassOS.update() done, defined at /usr/src/supervisor/supervisor/hassos.py:125> exception=HassOSUpdateError()>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/hassos.py", line 136, in update
    int_ota = await self._download_raucb(version)
  File "/usr/src/supervisor/supervisor/hassos.py", line 88, in _download_raucb
    raise HassOSUpdateError()
supervisor.exceptions.HassOSUpdateError

bibikiwi · 2021-03-04T10:56:32Z

When this happens to me (I'm kinda getting used to updates via the web interface being flaky), I do it via the command line. That seems to work more reliably. Login to the device (a RPI in my case) via SSH and (as root) type ha core update or ha supervisor update.
P.S. It just says 'Command completed successfully.' and returns, so to keep an eye on what's happening, I also open 2 other SSH connections, with docker logs -f homeassistant (just to see when it restarts) and watch docker ps (to keep an eye on what containers are being restarted and what versions.

stale · 2021-05-12T09:03:16Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions · 2022-01-04T11:03:16Z

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

balloob mentioned this issue Jun 11, 2020

QCOW2: can't update from 4.8 to 4.9 #738

Closed

This comment has been minimized.

Sign in to view

stale bot added the wontfix label Oct 12, 2020

stale bot removed the wontfix label Oct 20, 2020

XxCabbyoO mentioned this issue Oct 29, 2020

Cant upgrade to 4.15 #944

Closed

agners added the os-update Problems related to operating system updates label Nov 3, 2020

stale bot added the wontfix label May 12, 2021

agners removed the wontfix label Oct 6, 2021

github-actions bot added the stale label Jan 4, 2022

github-actions bot closed this as completed Jan 11, 2022

Cannot update Error: 502: Bad Gateway #617

Cannot update Error: 502: Bad Gateway #617

Comments

dany250 commented Apr 1, 2020 • edited by balloob

Semag commented May 22, 2020

Mediacj commented May 30, 2020

ctm514 commented Jun 1, 2020

Bettinaglio commented Jun 2, 2020 • edited

Semag commented Jun 2, 2020

Semag commented Jun 2, 2020

Mediacj commented Jun 2, 2020

Semag commented Jun 2, 2020

Mediacj commented Jun 3, 2020

Semag commented Jun 3, 2020

Semag commented Jun 3, 2020

Mediacj commented Jun 5, 2020

XxCabbyoO commented Jun 7, 2020 • edited by balloob

pvizeli commented Jun 8, 2020

XxCabbyoO commented Jun 8, 2020 • edited

balloob commented Jun 8, 2020

XxCabbyoO commented Jun 10, 2020 • edited by balloob

SAOPP commented Jun 11, 2020

XxCabbyoO commented Jun 16, 2020

SAOPP commented Jun 17, 2020

SAOPP commented Jun 17, 2020

morfei1 commented Jun 18, 2020 • edited

radostint commented Jun 21, 2020 • edited

Semag commented Jun 23, 2020

watermarkhu commented Jun 25, 2020

watermarkhu commented Jun 26, 2020 • edited

XxCabbyoO commented Jul 6, 2020 • edited

labachev commented Jul 7, 2020

psycmos commented Jul 8, 2020

cpuks commented Jul 8, 2020

balloob commented Jul 8, 2020

This comment has been minimized.

facuzestoa commented Aug 12, 2020 • edited

stale bot commented Oct 12, 2020

olli-dot-dev commented Oct 20, 2020

bibikiwi commented Mar 4, 2021

stale bot commented May 12, 2021

github-actions bot commented Jan 4, 2022

dany250 commented Apr 1, 2020 •

edited by balloob

Bettinaglio commented Jun 2, 2020 •

edited

XxCabbyoO commented Jun 7, 2020 •

edited by balloob

XxCabbyoO commented Jun 8, 2020 •

edited

XxCabbyoO commented Jun 10, 2020 •

edited by balloob

morfei1 commented Jun 18, 2020 •

edited

radostint commented Jun 21, 2020 •

edited

watermarkhu commented Jun 26, 2020 •

edited

XxCabbyoO commented Jul 6, 2020 •

edited

facuzestoa commented Aug 12, 2020 •

edited