Update to latest HA version failing .... first update after moving to Nabu Casa

Tags: #<Tag:0x00007f326dc78278> #<Tag:0x00007f326dc78110>

Hi,

I have been using HA on HASSIO (on ubuntu) with the duckdns/let’s encrypt addon for the last year - last week I start using Nabu Casa - works very good I am very pleased with it.
Since yesterday I am trying to upgrade (from 0.98.5) to v 0.99.3, but nothing seems to happen; I find the following in the log: I scanned the forum, found some remarks on disk-space; but this is not the issue. (to double-check, I cleaned out some backups, but same issue)
When I changed to the Nab-casa solution, I changed my configuration.yaml:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
#http:
#  base_url: !secret base_url
#  ssl_certificate: !secret ssl_certificate
#  ssl_key: !secret ssl_key
http:
  base_url: http://192.168.0.7:8123

And changed the config of all my addons to “ssl”: false
Everything is working correctly, but for the upgrade to 0.99.3 !
Any idea what this might be ?

19-09-30 18:40:06 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-09-30 18:40:53 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.99.3
19-09-30 18:40:53 INFO (SyncWorker_15) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.98.5 to homeassistant/qemux86-64-homeassistant:0.99.3
19-09-30 18:40:53 INFO (SyncWorker_15) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.99.3.
19-09-30 18:40:53 ERROR (SyncWorker_15) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.99.3 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:49782->[::1]:53: read: connection refused").
19-09-30 18:40:53 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

regards,

Chris

You don’t need any http: config at all when using nabucasa.

It looks like DNS is your issue. Can you check with hassio dns info and hassio dns logs?

I remove the http: part & did a reboot - same problem - dns info & log looks ok

dns info
host: 172.30.32.3
latest_version: "1"
locals: []
servers:
- dns://8.8.8.8
- dns://1.1.1.1
version: "1"

dns log

2019-09-30T23:19:17.035+02:00 [INFO] 172.30.32.1:51809 - 2911 "A IN api.spotify.com. udp 33 false 512" NOERROR qr,rd,ra 106 0.014088884s                    │···········
2019-09-30T23:19:17.036+02:00 [INFO] 172.30.32.1:51809 - 3179 "AAAA IN api.spotify.com. udp 33 false 512" NOERROR qr,rd,ra 159 0.014625315s                 │···········
2019-09-30T23:19:17.052+02:00 [INFO] 172.30.32.1:53395 - 7330 "A IN www.youtube.com. udp 33 false 512" NOERROR qr,rd,ra 436 0.020168463s                    │···········
2019-09-30T23:19:17.052+02:00 [INFO] 172.30.32.1:53395 - 7520 "AAAA IN www.youtube.com. udp 33 false 512" NOERROR qr,rd,ra 136 0.020631368s                 │···········
2019-09-30T23:19:17.148+02:00 [INFO] 172.30.32.1:51373 - 10889 "AAAA IN api.spotify.com. udp 33 false 512" NOERROR qr,rd,ra 159 0.016819413s                │···········
2019-09-30T23:19:17.148+02:00 [INFO] 172.30.32.1:51373 - 10508 "A IN api.spotify.com. udp 33 false 512" NOERROR qr,rd,ra 106 0.016916584s                   │···········
2019-09-30T23:19:17.538+02:00 [INFO] 172.30.32.1:38355 - 58226 "AAAA IN px1.tuyaeu.com. udp 32 false 512" NOERROR qr,rd,ra 129 0.015976829s                 │···········
2019-09-30T23:19:17.538+02:00 [INFO] 172.30.32.1:38355 - 57549 "A IN px1.tuyaeu.com. udp 32 false 512" NOERROR qr,rd,ra 122 0.016262105s                    │···········
2019-09-30T23:19:18.212+02:00 [INFO] 172.30.32.1:60634 - 4601 "AAAA IN px1.tuyaeu.com. udp 32 false 512" NOERROR qr,rd,ra 129 0.015031265s                  │···········
2019-09-30T23:19:18.215+02:00 [INFO] 172.30.32.1:60634 - 3854 "A IN px1.tuyaeu.com. udp 32 false 512" NOERROR qr,rd,ra 122 0.018627447s                     │···········
2019-09-30T23:19:18.938+02:00 [INFO] 172.30.32.1:45325 - 40066 "AAAA IN px1.tuyaeu.com. udp 32 false 512" NOERROR qr,rd,ra 129 0.015390292s                 │···········
2019-09-30T23:19:18.942+02:00 [INFO] 172.30.32.1:45325 - 39653 "A IN px1.tuyaeu.com. udp 32 false 512" NOERROR qr,rd,ra 122 0.019165075s                    │···········
2019-09-30T23:19:22.804+02:00 [INFO] 172.30.32.1:60646 - 5819 "A IN hassio.local.hass.io. udp 38 false 512" NOERROR qr,aa,rd 74 0.000079262s                │···········
2019-09-30T23:19:22.804+02:00 [INFO] 172.30.32.1:43172 - 28581 "AAAA IN hassio.local.hass.io. udp 38 false 512" NOERROR qr,aa,rd 38 0.000126034s            │···········

Additional info: all my addons update correctly!

**** CORRECTION **** I CANNOT INSTALL/UPDATE ADDONS

19-10-01 05:10:17 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
19-10-01 05:12:06 INFO (SyncWorker_18) [hassio.docker.interface] Update image homeassistant/amd64-addon-check_config:3.0 to homeassistant/amd64-addon-check_config:3.1
19-10-01 05:12:06 INFO (SyncWorker_18) [hassio.docker.interface] Pull image homeassistant/amd64-addon-check_config tag 3.1.
19-10-01 05:12:06 ERROR (SyncWorker_18) [hassio.docker.interface] Can't install homeassistant/amd64-addon-check_config:3.1 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:36211->[::1]:53: read: connection refused").
19-10-01 05:40:18 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token

19-10-01 07:39:28 INFO (MainThread) [hassio.addons] Create Home Assistant add-on data folder /data/addons/data/a0d7b954_airsonos
19-10-01 07:39:28 INFO (SyncWorker_2) [hassio.docker.interface] Pull image hassioaddons/airsonos-amd64 tag 2.1.1.
19-10-01 07:39:28 ERROR (SyncWorker_2) [hassio.docker.interface] Can't install hassioaddons/airsonos-amd64:2.1.1 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:46625->[::1]:53: read: connection refused").

I am not at work - but should I try to update without nabu-casa active or remove it (cloud: in configuration.yaml) ? If I remove it temporarily, can I add it again and use the same token etc …

Chris

I have de-activated nabu casa, removed the Duck-dns addon, but I still cannot update addons or update HA …
example below: update of Check Home Assistant configuration to 3.1

19-10-01 19:05:47 INFO (SyncWorker_15) [hassio.docker.interface] Update image homeassistant/amd64-addon-check_config:3.0 to homeassistant/amd64-addon-check_config:3.1
19-10-01 19:05:47 INFO (SyncWorker_15) [hassio.docker.interface] Pull image homeassistant/amd64-addon-check_config tag 3.1.
19-10-01 19:05:47 ERROR (SyncWorker_15) [hassio.docker.interface] Can't install homeassistant/amd64-addon-check_config:3.1 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:37061->[::1]:53: read: connection refused").
19-10-01 19:07:03 INFO (MainThread) [hassio.api.security] /snapshots access from cebe7a76_hassio_google_drive_backup

update to latest home-assistant version result in this:

19-10-01 19:14:14 INFO (MainThread) [hassio.host.network] Update local network DNS information
19-10-01 19:14:14 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
19-10-01 19:14:50 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.99.3
19-10-01 19:14:50 INFO (SyncWorker_19) [hassio.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.98.5 to homeassistant/qemux86-64-homeassistant:0.99.3
19-10-01 19:14:50 INFO (SyncWorker_19) [hassio.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.99.3.
19-10-01 19:14:50 ERROR (SyncWorker_19) [hassio.docker.interface] Can't install homeassistant/qemux86-64-homeassistant:0.99.3 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:54506->[::1]:53: read: connection refused").
19-10-01 19:14:50 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

Can anyone point me in correct direction, where to search or what to check ?

Chris

Had also the 500 Server Error. For me, this helped:

ssh into Hassio and type

hassio su repair

the try a normal update via the HA gui

1 Like

donpillo,

Thanks for the proposal, I say the option before (is marked Beta), but I have just tried it but it deleted a number of my active and in-active addons - they did no longer appear in the addon page, but they were still working ?! And I still have the same problems …
I am currently restoring my last backup.

thx for your reaction,

Chris

WOW! Such a simple solution… I have been fighting the HA login repose of “Unable to Connect” after it accepts my password and this FIXED IT!!!

You wont believe how many forums I have read and tried with no luck!

THANK YOU!!