I would like to use the /linuxserver/letsencrypt container to automate SSL for all of my docker containers (HA, Node-RED, and Unifi). I had LetsEncrypt setup and running via the add-on when I was running HA on a Pi with Hass.IO, but my situation is more complex now that I’m running on a NUC (Ubuntu) with Docker.
The documentation for /linuxserver/letsencrypt above is really well done and pretty straightforward. I think I could pull off creating the container successfully, but I’m struggling with the part where I utilize the certifications created in other containers. It’s under the “Using certs in other containers” section.
I’m comfortable using the “easier” method outlined within that section:
Mount the letsencrypt config folder in other containers (ie. -v /path-to-le-config:/le-ssl) and in the other containers, use the cert location /le-ssl/keys/letsencrypt/
But I’m not sure what I actually need to do to do that. To mount the letsencrypt folder in my other containers, what additional command do I run when building those containers? That’s what I can’t quite figure out.
TIA for any help!
Thank you! Looks like this might get me there!
Just wanted to say that this worked PERFECTLY! Thank you!
Only issue I have is not being able to use Node-RED when connected via DuckDNS. A Node-RED config issue/bug/fact, nothing on this end I don’t think.
Thread: Node Red with Duckdns/Let's Encrypt isn't executing locally. Please help a novice?
Glad it worked. Can’t advise on node red as I don’t use it.
However, if your system permits, I would suggest trying the node red official docker
https://nodered.org/docs/platforms/docker
And once working add it to letsencrypt docker like the rest.
Yep, that all works fine. I mean, Node-RED works great, it’s in a Docker container, and I can access it via HTTPS just like I can Unifi, HA, etc. The issue is that the connection between Node-RED and HA is relative, meaning when I connect locally w/o SSL and the HA server listed in Node-RED is the local address, it works fine. But when I connect via SSL/DuckDNS, the local server address for HA in Node-RED no longer works (for obvious reasons). An alternative would be to use the DuckDNS address but then I’m routing that connection over the net instead of locally on the NUC.
I’m sure I’ll figure it out!
If I understood that’s correct. The solution is to only use https. So HA would be for instance hass.duck…
And node red would be node.duc… and your respective references use those addresses.
Yes, but then I’m relying on a connection to the internet to keep my automations running (right?). In the current setup, I just need to make sure both containers are up and running. Or would it still route locally even with the https node.duckdns…?