DuckDNS docs: json instead of YAML

[Mark-81]

The doc page for DuckDNS configuration shows how to configure the service:

{
  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  },
  "token": "sdfj-2131023-dslfjsd-12321",
  "domains": ["my-domain.duckdns.org"]
}

but this is a json syntax, not YAML. So, where I need to put this code?

[flamingm0e]

It goes in the add-on config.

It doesn’t go in your Home Assistant configuration.

Are you using hassio or home assistant installed another way? If you are running hassio did you install the duckdns add-on?

[Mark-81]

Ah ok, it wasn’t very clear to me.
I installed HA using Python in VirtualEnv on a Debian - no hass.io.

[silvrr]

This is the official documentation for your install method,

Installing TLS/SSL using Let's Encrypt

This one is easier to implement IMO

A more lightweight Let's Encrypt + DuckDNS setup

I wrote a quick tutorial on how to set up Let’s Encrypt and DuckDNS without needing to expose Port 80 to the outside world using the “dehydrated” script instead of the heavy weight certbot tool. https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt The advantage of using DNS challenges is that I do not need to worry about what runs on port 80 (in my case it’s emulated_hue for Google Home) when doing the certificate renewal. I hope it’s useful for others.

[flamingm0e]

@Mark-81

Ah ok, it wasn’t very clear to me.

If you are looking at something for Home Assistant and the page is under /addons/ it is referring to hassio addons which are not available on any other platform at this time, other than hassio.