DuckDNS & Lets encrypt problem

Hey Guys,

I have tried getting this add on to work for ages now but it never seems to work for me. I think the SSL works because if I try to access my Hass.io instance locally via IP I get the warning about the SSL certificate not matching. However, if I try to use the address I have configured in DuckDNS and my config.yaml it seems to fail (But does reach my router).

Can someone tell me where I have gone wrong, please?

config.yaml:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
http:
  base_url: https://12345.duckdns.org:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

DuckDNS addon:

{
  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  },
  "token": "12345.token.goes.here",
  "domains": [
    "12345.duckdns.org"
  ],
  "seconds": 300
}

My router portforwarding configuration:

Remove the :8123 from your base_url, according to your port forwarding rules your external url is using port 443 (which doesn’t need to be tacked on the end for https requests).

Make sure that you are using https in the url you type in to the browser and are not adding any port numbers to the end.

Make sure the paths in your http: component are correct (ie, should it have the /ssl/ on the front?)

Make sure the port forwarding rule is correct, I’ve never seen one with a computer name before, it’s usually your internal ip address that should go there.

And finally, I don’t know how that specific addon works but you may need to add a port forward rule for outside 80 to 80 on your homeassistant box.

Hope this helps.

1 Like