after updating to 249 i couldn’t access any addons page from the web, showing a generic error with only an “OK”.
access addons from local was ok.
I use Nginx Proxy Manager, so don’t know if it’s that but never had this issue, if it was not loading addons on web it also didn’t on local, so this is new.
had to roll-back to 247 ( with many troubles since it was forcing to spin up v.249 ) to be able to access addons from web.
Will stay with 247 for now.
That sounds like browser cache, which is heavier if you use https, try clearing the cache of the web page.
That sounds like the recorder integration, have a look at filtering or limiting the days to keep.
1 reply
I’m not able to update
20-10-21 12:37:40 ERROR (SyncWorker_4) [supervisor.docker.interface] Can't install homeassistant/armhf-hassio-supervisor:249 -> 404 Client Error: Not Found ("manifest for homeassistant/armhf-hassio-supervisor:249 not found: manifest unknown: manifest unknown").
anyone facing the same issue?
2 replies
You can’t choose what version of the supervisor you use.
You have the ability to roll it back, but it will automatically updates itself eventually. You cannot disable automatic updates, so even if you roll back it’s likely to just update itself back to the newest version in a short time. This is an intentional choice by the devs, who have stated many times that the supervisor will always update itself, when it wants to, with no plans to give the users control over these updates.
Try again now @deluxestyle
Has there been any talk of a feature to turn off all automatic updates? Would be incredibly useful for cases where HA is running on mobile data (like RV or boat) with tight data caps.
Right now the only work-around I know of is to modify the dns forwarding of the router to force HA’s update checker to fail.
1 reply
If you want that level of control, you should look into running the standalone container version.
Do Not Change. /etc/docker/key.json:
It must be. /etc/docker/daemon.json:
sudo nano /etc/docker/daemon.json
{
“log-driver”: “journald”,
“storage-driver”: “overlay2”
}
sudo systemctl restart docker
2 replies
Perhaps you are out of disk space.
Thx, i will fix it (its working anyway).
I could swear that the docs said to edit key.json instead of daemon.json…
And look here:
https://docs.docker.com/config/containers/logging/journald/
The file daemon.json doesnt exist, i suppose i will have to create it.
1 reply
I’m running ‘unsupported’ on Ubuntu 20.04.1 LTS currently. Supervisor auto-updated from 247 to 249 on me this am. Clicking the warning message showed a Docker error, and I was able to create the daemon.json file, rebooted my entire NUC and now that warning message is gone.
I still have:
but at least Docker error is gone…
When I do the changes Docker is not starting anymore. I am getting this error.
Running systemctl status docker.service gives this error (RESOLVED):
Edit:
After some playing around I found out that it does not like the storage-driver setting. After doing a docker info I found out it was installed with aufs. When changed to aufs it started as usual again.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-10-21 21:46:17 CEST; 14s ago
Docs: https://docs.docker.com
Process: 727 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 727 (code=exited, status=1/FAILURE)
systemd[1]: Failed to start Docker Application Container Engine.
systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
systemd[1]: Stopped Docker Application Container Engine.
systemd[1]: docker.service: Start request repeated too quickly.
systemd[1]: docker.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Docker Application Container Engine.
systemd[1]: docker.service: Start request repeated too quickly.
systemd[1]: docker.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Docker Application Container Engine.
This is the latest version of Docker CE 19.03.13 on Ubuntu 20.04.1
Well, my instance apparently also auto-updated the Supervisor.
Currently on 249, and it’s now complaining about an unsupported installation, because Network Manager is apparently missing.
Thing is, this is a stock Supervised install running on Debian (on a pve host), never fiddled with any settings, so I have no idea why this might have happened.
The suggested remediation on the Network Manager page is re-running the install script. Is it safe to do it in a production system? Will I lose any of my add-ons or data, if I run the script again? And most importantly, since the system was actually installed by that same script, will the error get fixed?
Thanks for any help you guys can give!
2 replies
If you rerun the script it will be fine. It will just change a couple of docker settings and restart the service which will fix the error.
1 reply
I am very new to home assistant only installing about a week ago, since the latest update I am unable to access any of my add-ons and am also unable to access the supervisor tab.
HA is installed on a Raspberry Pi4. Really unsure how I am going to fix this - any advice would be welcome.
I am not super technical so hopefully there is a simple solution.
Quick: reboot the device, might not work
Not quick: Create a separate thread on this forum, or join discord https://discord.gg/c5DvZ4e
In the new thread, or on discord, provide logs from the help page http://IP_OF_PI:4357
Thanks for the fast response, have tried several reboots with no success. Will try discord or new thread option.
I’ve just seen your answer on github ! Thanks ! 
Still thinks my stuff is broken:
20-10-22 12:05:04 ERROR (MainThread) [supervisor.utils.gdbus] Can't parse '[{"connection": {"autoconnect-priority": -999, "id": "eth0", "permissions": [], "timestamp": 1603368129, "type": "802-3-ethernet", "uuid": "bbf6ed2c-6b10-3bdd-a4e9-7267dc2ee883"}, "802-3-ethernet": {"auto-negotiate": false, "mac-address": [220, 166, 50, 101, 87, 26], "mac-address-blacklist": [], "s390-options": {}}, "ipv4": {"address-data": [{"address": "192.168.12.10", "prefix": 23}], "addresses": [[168601792, 23, 4262308032]], "dns": [51161280, 84715712], "dns-search": [], "gateway": "192.168.13.254", "method": "manual", "route-data": [], "routes": []}, "proxy": {}, "ipv6": {"address-data": [{"address": "2001:470:792d:1:12::10", "prefix": 64}], "addresses": [[[32, 1, 4, 112, 121, 45, 0, 1, 0, 18, 0, 0, 0, 0, 0, 16], 64, [32, 1, 4, 112, 121, 45, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1]]], "dns": [[32, 1, 4, 112, 121, 45, 0, 1, 0, 18, 0, 0, 0, 0, 0, 3], [0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x12, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05]], "dns-search": ["delaars12.loc"], "gateway": "2001:470:792d:1::1", "method": "manual", "route-data": [], "routes": []}}]
': '({'connection': {'autoconnect-priority': <-999>, 'id': <'eth0'>, 'permissions': <@as []>, 'timestamp': <uint64 1603368129>, 'type': <'802-3-ethernet'>, 'uuid': <'bbf6ed2c-6b10-3bdd-a4e9-7267dc2ee883'>}, '802-3-ethernet': {'auto-negotiate': <false>, 'mac-address': <[byte 0xdc, 0xa6, 0x32, 0x65, 0x57, 0x1a]>, 'mac-address-blacklist': <@as []>, 's390-options': <@a{ss} {}>}, 'ipv4': {'address-data': <[{'address': <'192.168.12.10'>, 'prefix': <uint32 23>}]>, 'addresses': <[[uint32 168601792, 23, 4262308032]]>, 'dns': <[uint32 51161280, 84715712]>, 'dns-search': <@as []>, 'gateway': <'192.168.13.254'>, 'method': <'manual'>, 'route-data': <@aa{sv} []>, 'routes': <@aau []>}, 'proxy': {}, 'ipv6': {'address-data': <[{'address': <'2001:470:792d:1:12::10'>, 'prefix': <uint32 64>}]>, 'addresses': <[([byte 0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x12, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10], uint32 64, [byte 0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01])]>, 'dns': <[[byte 0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x12, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03], [0x20, 0x01, 0x04, 0x70, 0x79, 0x2d, 0x00, 0x01, 0x00, 0x12, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05]]>, 'dns-search': <['delaars12.loc']>, 'gateway': <'2001:470:792d:1::1'>, 'method': <'manual'>, 'route-data': <@aa{sv} []>, 'routes': <@a(ayuayu) []>}},)
' - Expecting ',' delimiter: line 1 column 858 (char 857)
20-10-22 12:05:04 WARNING (MainThread) [supervisor.host.network] Can't update network information!
Something is not parsed correctly for your IPv6 DNS servers @SandJ open an issue https://github.com/home-assistant/supervisor/issues/new and add the logs there, as well a description of your setup, and if possible the configuration files for Network Manager and output of nmcli
Is there any downside to simply ignoring. I’m 100% fine w/ this route vs. messing w/ config settings. “If it ain’t broke, don’t fix it”. Just trying to ensure that it “ain’t broke” currently 
As far as I can tell, everything seems to be working fine, just getting the Operating System and Network Manager warning messages (posted above fwiw):
Which means, things can break/stop working.
Thanks 
I had a similar problem with Covid-19 not working. In the end I added an extra line for DNS to /etc/docker/daemon.json and then everything started working again.
{
"log-driver": "journald",
"dns": [ "8.8.8.8", "8.8.4.4", "Your Own Local DNS if you have one" ],
"storage-driver": "overlay2"
}
Hi all,
Now that we have rate limits on docker hub I am starting to get really annoyed with the impact of that to my setup. Of course I am considering paying docker for this but frankly speaking I am not liking that idea much because I don’t think the service this provides is priced fairly. Like I can get oodles of storage for a few dollars a month with Google, AWS etc and yet just for hosting and serving some metadata I’d have to pay Docker much more. So before I go there i am willing to burn some cycles and setup a local mirror on my home network. I would be doing that on my Qnap NAS and I am considering using Quay for this.
But before I put in the effort I’d like to know how hardcoded the docker hub is for homeassistant. If I mirror all relevant content including core homeassiant etc and add my local mirror to the supervisor will everything work? I would basically block my RPI running homeassistant from reaching docker after this and only have my mirror sync every 24 hours or so.
Please advise if this is possible and if anyone has tried this already I am keen learn from your work.
Many thanks!
