From b6ada31d4614041c7c70ecd44d28474fc19beca4 Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Sat, 6 Jul 2019 09:42:25 +0100 Subject: [PATCH] Quick removal of links to setting the password (#9795) API password is dead, we shouldn't be talking about it any more --- source/_docs/ecosystem/certificates/lets_encrypt.markdown | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/source/_docs/ecosystem/certificates/lets_encrypt.markdown b/source/_docs/ecosystem/certificates/lets_encrypt.markdown index 419a676890c..e9fbab0c19d 100644 --- a/source/_docs/ecosystem/certificates/lets_encrypt.markdown +++ b/source/_docs/ecosystem/certificates/lets_encrypt.markdown @@ -13,16 +13,11 @@ footer: true If you are using Hass.io or Hassbian, do not use this guide. Instead, use the [DuckDNS add-on](/addons/duckdns/) for Hass.io or the [DuckDNS suite](https://github.com/home-assistant/hassbian-scripts/blob/master/docs/suites/duckdns.md) for Hassbian to automatically maintain a subdomain including HTTPS certificates via Let's Encrypt.

-

-Before exposing your Home Assistant instance to the outside world it is ESSENTIAL that you have set a password following the advice on the [http](/components/http/) page. -

- - This guide was added by mf_social on 16/03/2017 and was valid at the time of writing. This guide makes the following assumptions: * You can access your Home Assistant instance across your local network, and access the device that it is on via SSH from your local network. * You know the internal IP address of your router and can access your router's configuration pages. - * You have already set up a password for your Home Assistant instance, following the advice on this page: [http](/docs/configuration/basic/) + * You have already secured your Home Assistant instance, following the advice on [this page](/docs/configuration/securing/) * You want to access your Home Assistant instance when you are away from home (ie, not connected to your local network) and secure it with a TLS/SSL certificate. * You have a basic understanding of the phrases I have used so far. * You are not currently running anything on port 80 on your network (you'd know if you were).