Hey everyone, I’ve been diving into setting up Home Assistant with SSL encryption using DuckDNS, and I wanted to share my journey in case it helps someone else. I’ve been using DuckDNS for a while now, and it’s been a reliable solution for exposing my HA instance to the internet. However, I recently encountered an issue where I could no longer access my HA instance via HTTPS, though HTTP worked fine. The browser threw an error saying it couldn’t connect, even though the DuckDNS addon logs showed everything was working as expected. The SSL certificate was valid, and the port forwarding hadn’t changed since my last setup a year ago. I decided to take a closer look at my configuration.yaml file and realized that the base URL and SSL certificate paths were still pointing to the correct locations. After some research, I came across a suggestion to restart the DuckDNS addon, which I hadn’t considered doing despite restarting HA multiple times. Lo and behold, that simple step resolved the issue! It’s a good reminder that sometimes the most straightforward solutions are the ones we overlook. I thought I’d share this in case someone else runs into a similar situation. Happy configuring everyone! 