[solved]Unable to reach https://xxx.duckdns.org:8123. But http (without the s) works

1

[edit] Solved! I apparently just needed restart. I thought I had done it a couple of time already.

I had a working install of Home Assistant complete with working duckdns and encryptiion via the duckdns addon. I started fresh on different computer, copy and pasted my configuartion.yaml, made sure it was still valid. I then installed the new duckdns addon.

Now I’m no longer able to reach my installation via https://xxx.duckdns.org:8123. I am, however, able to reach it via http://xxx.duckdns.org:8123. That is, just http, not https.

The browser error I get when going to the https URL is “Unable to connect to Home Assistant.”, and I see the home assistant icon. In the lock information, I see it’s secure w/ letsencrypt.

So the duckdns addon seems to be working (and I can see it’s working in the addon log, all OK no errors). And port forward works, not changed since the last install. The previous version of HA was a year old, did the way we’re supposed to define the base URL change?

My configuration.yaml:

http:
  base_url: https://xxxx.duckdns.org:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
2

I am having the same problem, was the base_url the issue?

3

no, the URL is fine, I just needed to restart the system I guess? Although, I’m pretty sure I restarted it a couple of times after making that change to HTTP. So…I’m not sure what finally fixed it.