From 3e8e205ff7e131ee146fd8cb051e871179b48151 Mon Sep 17 00:00:00 2001 From: mn Date: Mon, 11 Mar 2019 19:09:54 +0100 Subject: [PATCH] Generate Let's Encrypt certificate for Duck DNS sub sub domains (#8882) * Generate Let's Encrypt certificate for Duck DNS sub sub domains Needed to do this when using the NGINX Home Assistant SSL proxy for customized servers. * Minor change --- source/_addons/duckdns.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/source/_addons/duckdns.markdown b/source/_addons/duckdns.markdown index d1726880996..9a63a87dbd2 100644 --- a/source/_addons/duckdns.markdown +++ b/source/_addons/duckdns.markdown @@ -69,3 +69,15 @@ You'll need to forward the port you listed in your configuration (8123 in the ex Ensure that you allocate the Home Assistant system a fixed IP on your network before you configure port forwarding. You can do this either on the computer itself (see the [install guide](/hassio/installation/) or via a static lease on your router. Restart Home Assistant for the configured changes to take effect. When you access the Home Assistant frontend you will now need to use `https`, even when accessing local instances, for example at `https://192.168.0.1:8123`. + +## {% linkable_title Generate Let's Encrypt certificate for Duck DNS sub sub domains %} + +To generate certificates for nr.my-domain.duckdns.org update the domain JSON settings to: + +```json +{ + ... + "domains": ["my-domain.duckdns.org","*.my-domain.duckdns.org"], + ... +} +```