2018-02-22 18:08:48 ERROR (MainThread) [homeassistant.config] Invalid config for [http]: not a file for dictionary value @ data[âhttpâ][âssl_certificateâ]. Got â/certs/live/mydomain.duckdns.org/fullchain1.pemâ
not a file for dictionary value @ data[âhttpâ][âssl_keyâ]. Got â/certs/live/mydomain.duckdns.org/privkey1.pemâ.
i recently moved from venv to docker on my raspi3. works well except the SSL certs issue that I can see few other have the same problem.
how do you plan to upgrade your HASS? do you destroy the container and recreate? or update HASS within the container?
also, i made changes to the original container, such as ability to shutdown another linux computer, that requires generating ssh key and transfer it across the other linux computer. any suggestion what to do so that I dont have to keep generating keys everytime i destory and create new container?
Itâs a container. You donât modify the contents of the container. To update you just docker-compose downdocker-compose pulldocker-compose up -d.
If you arenât running docker compose, just docker kill, docker rm, docker pull homeassistant/hhome-assistant, and the docker command you used to create it
I had run HA in a container for a while before Tradfri came out, then it wasnât working so I had moved away from it. This post inspired me to get everything working in containers again. Everything is back up, but 2 of my scripts are nonfunctional. Does anyone have experience with the following:
Using GIT to pull configs from a docker container? (configs are committed to repo, then pulled down with a script through HASS)
Upgrade the HASS container from a script triggered within HASS? (This might be impossible. not sure)
This can be a little tricky but you can do this with a combo. Ha-dockermon combined with a docker container that is mounted to the same volume bind mount as your ha config. So a single docker container that does a git pull, and call the start/restart of that script from home assistant with ha-dockermon switch.
Maybe a script that SSHes into the host itself, does a docker pull, then automates the docker kill, rm, and start?
yep i got that, I have -v bind mounts to host directory where HASS config are stored. However, to allow the container to shutdown/suspend another computer, you need to allow the container (HASS within the container) to be able to connect via ssh to a linux machine and execute a command remotely.
If you run https://www.rancher.com as your docker manager, you can import the catalogue, and run home-assistant and some dependant services with a single click.
Itâs using the /docker/ha-config/certs directory from the try before that one when i used:
I donât know why it worked.
Iâm just happy it did.
Itâs just unfortunate that one success brings the next challenge because now the ssl-cert-check command i use doesnât find the new certs because the command is being run from inside the HA container on a command installed outside the container on the host. or at least thatâs why Iâm thinking it doesnât work. i really have no ideaâŚ