Skip to content

Commit 251b2b6

Browse files
ferazambujafabaff
authored andcommitted
Update link (home-assistant#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.
1 parent 51eee86 commit 251b2b6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

source/_docs/configuration/remote.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The most common approach is to set up port forwarding from your router to port 8
1515

1616
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/).
1717

18-
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.
18+
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.
1919

2020
Protect your communication with a [self-signed certificate](/cookbook/tls_self_signed_certificate/) between your client and the Home Assistant instance.
2121

0 commit comments

Comments
 (0)