From 52aa872d309d151b7e57164054466dd3a4cd7652 Mon Sep 17 00:00:00 2001 From: Fabian Affolter Date: Tue, 21 Jun 2016 09:01:31 +0200 Subject: [PATCH] Update example --- .../2015-12-13-setup-encryption-using-lets-encrypt.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_posts/2015-12-13-setup-encryption-using-lets-encrypt.markdown b/source/_posts/2015-12-13-setup-encryption-using-lets-encrypt.markdown index 9f1e04ed9a7..f9a35585998 100644 --- a/source/_posts/2015-12-13-setup-encryption-using-lets-encrypt.markdown +++ b/source/_posts/2015-12-13-setup-encryption-using-lets-encrypt.markdown @@ -94,8 +94,8 @@ The final step is to point Home Assistant at the generated certificates. Before ```yaml http: api_password: YOUR_SECRET_PASSWORD - ssl_certificate: /etc/letsencrypt/live/hass.example.com/fullchain.pem - ssl_key: /etc/letsencrypt/live/hass.example.com/privkey.pem + ssl_certificate: /etc/letsencrypt/live/hass-example.duckdns.org/fullchain.pem + ssl_key: /etc/letsencrypt/live/hass-example.duckdns.org/privkey.pem ``` You can now navigate to https://hass-example.duckdns.org and enjoy encryption!