Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions source/_addons/lets_encrypt.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -16,21 +16,15 @@ You should not use this if you are also using the [DuckDNS add-on]. The DuckDNS

Setup and manage a [Let's Encrypt](https://letsencrypt.org/) certificate. This will create a certificate on the first run and will auto-renew if the certificate is within 30 days of expiration.

<p class='note warning'>
This add-on uses ports 80/443 to verify the certificate request. You will need to stop all other add-ons that also use these ports. If you don't need a port (like with https you don't need port 80) you can remove this from network config.
</p>

```json
{
"challenge": "https",
"email": "example@example.com",
"domains": ["example.com", "mqtt.example.com", "hass.example.com"]
}
```

Configuration variables:

- **challenge** (*Optional*): Default it use 443 ('https') you can change it to 'http' for use port 80.
- **email** (*Required*): Your email address for registration on Let's Encrypt.
- **domains** (*Required*): A list of domains to create/renew the certificate.

Expand All @@ -45,6 +39,6 @@ http:
ssl_key: /ssl/privkey.pem
```

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

[DuckDNS add-on]: /addons/duckdns/