From 02f60a507df2409fd19a1346d0205cd953362832 Mon Sep 17 00:00:00 2001 From: Sebastiaan Date: Thu, 24 Nov 2016 14:16:20 +0100 Subject: [PATCH] Update tls_self_signed_certificate.markdown (#1491) Fixed link to https://home-assistant.io/blog/2015/12/13/setup-encryption-using-lets-encrypt/ --- source/_cookbook/tls_self_signed_certificate.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_cookbook/tls_self_signed_certificate.markdown b/source/_cookbook/tls_self_signed_certificate.markdown index cd2748a702d..61ced56bf55 100644 --- a/source/_cookbook/tls_self_signed_certificate.markdown +++ b/source/_cookbook/tls_self_signed_certificate.markdown @@ -10,7 +10,7 @@ footer: true ha_category: Infrastructure --- -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. [Let's encrypt](blog/2015/12/13/setup-encryption-using-lets-encrypt/) 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. +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. [Let's encrypt]({{site_root}}/blog/2015/12/13/setup-encryption-using-lets-encrypt/) 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. To create locally a certificate you need the [OpenSSL](https://www.openssl.org/) command-line tool.