If you are using the built in Reverse Proxy of Synology as I suggested your NAS will handle certificate renewal (no need for the Let’s Encrypt addon). You can add as many subdomains you like under Subject Alternative Name.
You will have an unencrypted connection between Synology’s build in Nginx and HA, but as that is using loopback network interface you have other problems if someone breaks into your nas…
So, just change base_url to something like this, and let Synology handle the rest.
FWIW, I found the LetsEncrypt on Synology meant i had to manually renew every month or three, and I guess I got lazy?
I use the nginx/letsencrypt-companion, but since we cannot set the environment on the homeassistant container to drive the nginx/companion, I use a socat-based proxy: depends on homeassistant, has the environment variables to drive LetsEncrypt certificate automation, and socat-forwards tcp/80 to the homeassistant tcp/8123. It’s all hands-off from that point.
I recall also that the Synology/LetsEncrypt didn’t let me do wildcard Subject-Alternative, so I’d need to manually change it every time I added a container. It’s partly laziness, partly risk-of-forgetting, so this workflow allows me to keep the LetsEncrypt certs in the same docker-compose.yaml config in a “gitops” workflow.
Hi all,
First off all thank you very much, @fredrike for putting in so much time and effort next to a demanding job and a long commute!
I’ll try to be as brief as possible. I’m a complete newb but have read all posts above.
Fresh install from Synocommunity, Latest Docker version (18.09.0-0506), followed instructions in first comments. Everything works great.
UNTIL
My Nas (DS1019+) reboots. Then the hass.io package is running, but none of the Docker containers has turned on. The “hassio_supervisor” container continuous to spawn and disappear. When I try to start the “homeassistant” container manually, the message reads: [Docker API failed. Please visit Docker Log for more information.]
When I manually try to start the “hassio_supervisor” container, it reads [container {“message”: “No such container: hassio_supervisor”} does not exist.]
Basically, all I can do is uninstall the Hassio Package from the package center. When I re-install, I’m good until my nas reboots. Then the containers are corrupt again.
I hope someone can help me get around this issue.
Update question:
I orginally installed this via the Dropbox package.
Just added the SynoCommunity link and see an option there for Hass.io Beta to be Updated.
Is it as simple as clicking ‘Update’? Do I need to Stop the currently Running Hass.io before Updating?
Any way to backup the current package just in case before doing so?
I already made a Snapshot in the Hass.io Supervisor tab.
Thanks!
We are all newb . Thanks for reading through the whole thread.
I’ve never heard about such a problem, can you get an other Docker image to stay active between reboots?
Yes, but you will not gain anything new (the package on SynoCommunity) is the same as the one I had posted here. There is no need to do anything else but better safe than sorry.
Hi @fredrike, thanks for your reply. This weekend I switched to using home-assistant(core) rather than Hass.io. I thought it would be a lot more difficult than it really is. Currently, I have about 10 docker containers running while my synology reboots every night. (Due to a memory/cpu leak in sonarr and mono) All of them are fine when I check on them in the morning.
So, since i’m the only one reporting such an issue, and I’ve since moved on, maybe don’t worry about it too much? If you are going to persue this; let me know if there is anything I can do to help.
So it is not a graceful reboot, it is a crash on the NAS. That might explain things. It seems like the Synology Docker package have some issues with containers created outside of DSM (the Hass.io package is creating it’s own containers) and remembering them.
One fix for you might be to do a graceful reboot before it crashes and from that hope that it will work.
Or, change Sonarr installation, I’m running linuxserver/sonarr:latest and it is quite stable for me.
Sorry for being unclear. I’ve created a daily task that reboots the NAS every night. This way I’m certain the CPU load will remain normal.
Thank you for the advice on running Sonarr. I’ll deffinitly look into that soon!
(I’ve been using the synocommunity app but I thnk the problem is with Mono)
I would have hoped that the synology Docker app would shutdown “gracefully” when I command the NAS to reboot. But I’ll admit that I don’t know enough about any of this.
Currently, I create my dockercontainers and install the images through commandline. Basically, I follow the instructions of Bearded Tinker on Youtube. https://youtu (.) be/pcnvmAOah_Y
Perhaps if I create the hass.io dockers in the same way, I will have less of an issue? Anyway, I’d prefer to run hass.io when possible since it’s a lot easier to use. (I miss the snapshots!) However, my setup is really coming along and I’ve learned a lot in the past weekend. So I’m good for now.
Thank you for the quick response! I was wondering if the SynoCommunity version would update me as Hass.io Supervisor shows me as being on 0.104.3. There is an option to update Core to 0.105.3 in the Supervisor but I wasn’t sure if that was a better way to do it with your install or if I should do it from ‘outside’ by updating the package via SynoCommunity.
All upgrades of hass-core and hass (previously called hassio) should be done via the Supervisor tab.
The only benifit to change to the Synocommunity package is to get a notification the the potentially next version (we still need to investigate what is going on with the network configuration of our NASes with this package, any news @mikepflu?).
I have this Hass.io on my NAS, and it works great! I only have one question for you. I installed the Mosquitto MQTT using Hass.io, and when I need to reboot my NAS its a chaos! The problem is that the MQTT broker is starting after the major containers I have, and they all fail to start because the MQTT is not available.
Do you know how to fix this?
It’s possible to give a high priority to mqtt?
I am trying to install Hassio on my synology model 418play. Docker is not natively supported on this model. i have manually install it. Docker is running with 3 -4 container with no issue. When I try installing HASSIO from synology community I got docker package missing error. Need some help.
Thanks
.
. Thanks for reading through the whole thread.