diff --git a/source/_addons/configurator.markdown b/source/_addons/configurator.markdown
index b8f340bace0..52cffaf06bc 100644
--- a/source/_addons/configurator.markdown
+++ b/source/_addons/configurator.markdown
@@ -7,6 +7,7 @@ sidebar: true
 comments: false
 sharing: true
 footer: true
+featured: true
 og_image: /images/hassio/screenshots/addon-hass-configurator.png
 ---
 
diff --git a/source/_addons/duckdns.markdown b/source/_addons/duckdns.markdown
index 5ef39695406..d84c655c35b 100644
--- a/source/_addons/duckdns.markdown
+++ b/source/_addons/duckdns.markdown
@@ -10,7 +10,7 @@ footer: true
 featured: true
 ---
 
-[Duck DNS](https://duckdns.org/) is a free service which will point a DNS (sub domains of duckdns.org) to an IP of your choice.
+[Duck DNS](https://duckdns.org/) is a free service which will point a DNS (sub domains of duckdns.org) to an IP of your choice. This add-on includes support for Let's Encrypt and will automatically create and renew your certificates.
 
 ```json
 {
diff --git a/source/_posts/2015-12-13-setup-encryption-using-lets-encrypt.markdown b/source/_posts/2015-12-13-setup-encryption-using-lets-encrypt.markdown
index f9a35585998..a896c618ada 100644
--- a/source/_posts/2015-12-13-setup-encryption-using-lets-encrypt.markdown
+++ b/source/_posts/2015-12-13-setup-encryption-using-lets-encrypt.markdown
@@ -11,6 +11,10 @@ categories: How-To
 og_image: /images/blog/2015-12-lets-encrypt/letsencrypt-secured-fb.png
 ---
 
+<p class='note'>
+The instructions in this blog post are outdated. Please have a look at the <a href='/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/'>new instructions</a>.
+</p>
+
 Exposing your Home Assistant instance outside of your network always has been tricky. You have to set up port forwarding on your router and most likely add a dynamic DNS service to work around your ISP changing your IP. After this you would be able to use Home Assistant from anywhere but there is one big red flag: no encryption.
 
 This tutorial will take you through the steps to setup a dynamic DNS for your IP and allow trusted encrypted connection to it - for free using [DuckDNS] and [Let's Encrypt].
diff --git a/source/_posts/2017-09-27-effortless-encryption-with-lets-encrypt-and-duckdns.markdown b/source/_posts/2017-09-27-effortless-encryption-with-lets-encrypt-and-duckdns.markdown
new file mode 100644
index 00000000000..b0e78bcf681
--- /dev/null
+++ b/source/_posts/2017-09-27-effortless-encryption-with-lets-encrypt-and-duckdns.markdown
@@ -0,0 +1,41 @@
+---
+layout: post
+title: "Effortless encryption with Let's Encrypt and DuckDNS"
+description: "Get Home Assistant encrypted in less than 5 minutes."
+date: 2017-09-27 00:05:00 +0000
+date_formatted: "September 27, 2017"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories: How-To
+og_image: /images/blog/2015-12-lets-encrypt/letsencrypt-secured-fb.png
+---
+
+When Let's Encrypt launched we were estatic: finally an easy and free way for our users to securely access their homes remotely. Let's Encrypt signifianctly lowered the bar to get and renew SSL certificates. However, this process could still be quite an obstacle for our users. It required opening ports on the router and remembering to renew the certificate every so often.
+
+Thanks to a [blog post][splitbrain] by Andreas Gohr I realized that DuckDNS supports setting TXT records, making it compatible with the DNS-01 challenge of Let's Encrypt. The DNS-01 challenge is using the DNS record of the domain instead of interacting with the server. This means that it's not needed for the user to open any ports!
+
+I have worked together with [Pascal Vizeli][pvizeli] on updating the DuckDNS add-on for Hass.io and today we're proud to announce it now includes automatic generation and updating of Let's Encrypt certificates for your DuckDNS domain. The only thing that you have to add to your DuckDNS configuration is that you accept their [terms of service][terms] and point Home Assistant at the generated certificates and you're good to go. No other work is required.
+
+To get started today, start with making sure that you have [Hass.io installed][hassio]. After that, go to the Hass.io panel in Home Assistant, open the add-on store, scroll down to DuckDNS and install it. In the DuckDNS settings change "accept_terms" to true and start it.
+
+Next up is to configure Home Assistant with the config below and restart it. You're now good to go! Make sure to use the right protocol when browsing to your instance: `https://<your_domain>.duckdns.org`. Happy secure controlling your house!
+
+```yaml
+# Example configuration.yaml entry for the HTTP component
+http:
+  ssl_certificate: /ssl/fullchain.pem
+  ssl_key: /ssl/privkey.pem
+```
+
+If you're not using Hass.io, check out the [blog post][splitbrain] by Andreas for instructions.
+
+If you enjoy the free service provided by DuckDNS and Let's Encrypt, consider donating to their cause:
+
+ - [Become a Patreon of DuckDNS](https://www.patreon.com/user?u=3209735)
+ - [Donate to Let's Encrypt](https://letsencrypt.org/donate/)
+
+[splitbrain]: https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt
+[terms]: https://letsencrypt.org/repository/
+[pvizeli]: https://github.com/pvizeli
+[hassio]: /hassio/