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
**** 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 …
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 ?
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.