jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2017-09-03 19:53:57 UTC

Browse source
This commit is contained in:
Travis CI 2017-09-03 19:53:57 +00:00
parent 72d9d84eaf
commit b03c36dd59
26 changed files with 66 additions and 66 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/ecosystem/certificates/lets_encrypt/index.html
View file

@ -97,7 +97,7 @@ Before exposing your Home Assistant instance to the outside world it is ESSENTIA
<li>2 - Set up port forwarding without TLS/SSL and test connection</li>
<li>3 - Set up a DuckDNS account</li>
<li>4 - Obtain a TLS/SSL certificate from Let’s Encrypt</li>
<li>5 - Check the incoming conection</li>
<li>5 - Check the incoming connection</li>
<li>6 - Clean up port forwards</li>
<li>7 - Set up a sensor to monitor the expiry date of the certificate</li>
<li>8 - Set up an automatic renewal of the TLS/SSL certificate</li>
@ -270,7 +270,7 @@ $ chmod a+x certbot-auto
</code></pre>
</div>
<p>Did all of that go without a hitch? Wahoo! Your Let’s Encrypt certificate is now ready to be used with Home Assistant. Move to step 5 to put it all together</p>
<h3><a class="title-link" name="5---check-the-incoming-conection" href="#5---check-the-incoming-conection"></a> 5 - Check the incoming conection</h3>
<h3><a class="title-link" name="5---check-the-incoming-connection" href="#5---check-the-incoming-connection"></a> 5 - Check the incoming connection</h3>
<p class="note">
Following on from Step 4 your SSH will still be in the certbot folder. If you edit your configuration files over SSH you will need to change to your <code class="highlighter-rouge">homeassistant</code> folder:
<code class="highlighter-rouge">