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