Site updated at 2018-02-15 21:31:27 UTC
This commit is contained in:
parent
6eb11af047
commit
74121d2541
27 changed files with 74 additions and 74 deletions
|
@ -77,7 +77,7 @@
|
|||
<hr class="divider">
|
||||
<p>If your Home Assistant instance is only accessible from your local network you can still protect the communication between your browsers and the frontend with SSL/TLS.
|
||||
<a href="/blog/2015/12/13/setup-encryption-using-lets-encrypt/">Let’s encrypt</a> will only work if you have a DNS entry and remote access is allowed.
|
||||
The solution is to use a self-signed certificate. As you most likely don’t have a certification authority (CA) your browser will conplain about the security. If you have a CA then this will not be an issue.</p>
|
||||
The solution is to use a self-signed certificate. As you most likely don’t have a certification authority (CA) your browser will complain about the security. If you have a CA then this will not be an issue.</p>
|
||||
<p>To create a certificate locally, you need the <a href="https://www.openssl.org/">OpenSSL</a> command-line tool.</p>
|
||||
<p>Change to your Home Assistant <a href="/getting-started/configuration/">configuration directory</a> like <code class="highlighter-rouge">~/.homeassistant</code>. This will make it easier to backup your certificate and the key. Run the command shown below.</p>
|
||||
<p>The certificate <strong>must</strong> be <code class="highlighter-rouge">.pem</code> extension.</p>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue