From c0e1270c434635d627c9d876cee35f29797bdc6c Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Tue, 29 May 2018 16:40:44 +0200 Subject: [PATCH] Put content in a warning box and update links --- source/_docs/configuration/remote.markdown | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/source/_docs/configuration/remote.markdown b/source/_docs/configuration/remote.markdown index 8d3208389d6..f0d981b116e 100644 --- a/source/_docs/configuration/remote.markdown +++ b/source/_docs/configuration/remote.markdown @@ -9,14 +9,18 @@ sharing: true footer: true --- -If you're interested in logging in to Home Assistant while away, you'll have to make your instance remotely accessible. Remember to follow the [securing checklist](/docs/configuration/securing/) before doing this. +If you're interested in logging in to Home Assistant while away, you'll have to make your instance remotely accessible. + +

+Remember to follow the [securing checklist](/docs/configuration/securing/) before doing this. +

The most common approach is to set up port forwarding (for any port) from your router to port 8123 on the computer that is hosting Home Assistant. General instructions on how to do this can be found by searching ` port forwarding instructions`. You can use any free port on your router and forward that to port 8123. 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/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. +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 Home Assistant. -Protect your communication with a [self-signed certificate](/cookbook/tls_self_signed_certificate/) between your client and the Home Assistant instance. +Protect your communication with a [self-signed certificate](/docs/ecosystem/certificates/tls_self_signed_certificate/) between your client and the Home Assistant instance. -For another way to access your Home Assistant frontend, check out [the instructions how to use Tor](/cookbook/tor_configuration/). +For another way to access your Home Assistant frontend, check out [the instructions how to use Tor](/docs/ecosystem/tor/).