After several days of trial and error, I finally managed to set up SSL for my Home Assistant instance running on Synology Docker! It was a bit of a learning curve, but I wanted to share my experience in case it helps anyone else out there.
First, I followed a guide that suggested using DuckDNS for domain setup. I created a domain and set up DDNS as instructed. The tricky part was configuring the reverse proxy in the Synology Control Panel. I kept getting errors about port numbers and domain conflicts. At one point, I thought I had messed up the entire setup because the SSL certificate entry looked incomplete in the Control Panel. It just said ‘For: -’, which was a bit unsettling. However, I noticed it did mention ‘registered R3’ and ‘RSA/ECC’, which matched the other Synology entries, so I decided to proceed.
The breakthrough came when I realized I needed to adjust the port forwarding settings in my router. After ensuring ports 80 and 443 were correctly forwarded to my Synology NAS, I retried the reverse proxy setup. This time, it worked like a charm! I could finally access my Home Assistant instance securely via HTTPS.
One thing I still need to figure out is how to tell Home Assistant to use the generated SSL certificates. I exported all the PEM files from Synology, but I’m not entirely sure which ones are applicable. If anyone has experience with this, I’d love to hear your insights!
Overall, the process taught me a lot about SSL configurations and reverse proxies. It’s incredibly satisfying to have a fully secure and accessible Home Assistant setup now. I hope this post can serve as a helpful reference for others tackling similar challenges!