From 251b2b67d3e3311087eb5bfd260c3e1e7c93376b Mon Sep 17 00:00:00 2001 From: Fernando Date: Sun, 27 May 2018 03:53:28 -0400 Subject: [PATCH] Update link (#5440) Updated the link for "set up encryption using Let's Encrypt" for the latest one. Instead of sending the user to the outdated version with the link for the newest one. --- source/_docs/configuration/remote.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/configuration/remote.markdown b/source/_docs/configuration/remote.markdown index a323ff1c980..2313d9a41c2 100644 --- a/source/_docs/configuration/remote.markdown +++ b/source/_docs/configuration/remote.markdown @@ -15,7 +15,7 @@ The most common approach is to set up port forwarding from your router to port 8 A problem with making a port accessible is that some Internet Service Providers only offer dynamic IPs. This can cause you to lose access to Home Assistant while away. You can solve this by using a free Dynamic DNS service like [DuckDNS](https://www.duckdns.org/). -Remember: Just putting a port up is not secure. You should definitely consider encrypting your traffic if you are accessing your Home Assistant installation remotely. For details please check the [set up encryption using Let's Encrypt](/blog/2015/12/13/setup-encryption-using-lets-encrypt/) blog post, or this [detailed guide](/docs/ecosystem/certificates/lets_encrypt/) to using Let's Encrypt with HA. +Remember: Just putting a port up is not secure. You should definitely consider encrypting your traffic if you are accessing your Home Assistant installation remotely. For details please check the [set up encryption using Let's Encrypt](/blog/2017/09/27/effortless-encryption-with-lets-encrypt-and-duckdns/) blog post, or this [detailed guide](/docs/ecosystem/certificates/lets_encrypt/) to using Let's Encrypt with HA. Protect your communication with a [self-signed certificate](/cookbook/tls_self_signed_certificate/) between your client and the Home Assistant instance.