home-assistant.io/source/_addons/lets_encrypt.markdown
cogneato 73af490160 re-adding that the add-on makes use of port 80 (#4760)
I realized that the entire previous instruction should not have been removed and only the reference to port 443.
2018-03-06 11:06:07 +01:00

1.3 KiB

layout, title, description, date, sidebar, comments, sharing, footer, featured
layout title description date sidebar comments sharing footer featured
page Let's Encrypt Automatically manage your SSL certificate using Let's Encrypt. 2017-04-30 13:28 true false true true false

You should not use this if you are also using the [DuckDNS add-on]. The DuckDNS add-on has integrated Let's Encrypt support.

Setup and manage a Let's Encrypt certificate. This addon will create a certificate on the first run and will auto-renew if the certificate is within 30 days of expiration. This add-on uses port 80 to verify the certificate request. You will need to stop all other add-ons that also use this port.

{
  "email": "example@example.com",
  "domains": ["example.com", "mqtt.example.com", "hass.example.com"]
}

Configuration variables:

  • email (Required): Your email address for registration on Let's Encrypt.
  • domains (Required): A list of domains to create/renew the certificate.

{% linkable_title Home Assistant configuration %}

Use the following configuration in Home Assistant to use the generated certificate:

http:
  base_url: https://my-domain.tld:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

If you use another port such as 8123 or an SSL proxy, change the port number.