certbot-duckdns/README.md

38 lines
1.1 KiB
Markdown
Raw Normal View History

2020-10-29 16:38:49 +01:00
# Certbot with duckdns wildcard certificate
Just run it with the correct environment variables and enjoy.
2020-11-01 13:09:42 +01:00
Because of a limitation on duckdns it is not possible to
request a certificate which works for both the domain and
wildcard subdomains. Because of this we request 2 certificates,
one for the domain and one wildcard cert.
**Example:**
2022-03-10 16:12:30 +01:00
```
docker run --rm \
-e DUCKDNS_DOMAIN=redxef \
-e DUCKDNS_TOKEN=<your ddns token> \
-e LE_EMAIL=noreply@example.com \
redxef/certbot-duckdns
```
2020-11-01 13:09:42 +01:00
`DUCKDNS_DOMAIN=redxef`
Yields 2 certificates, the first being for redxef.duckdns.org and the
2022-03-10 15:55:58 +01:00
second being for \*.redxef.duckdns.org. These certificates can be found
2020-11-01 13:09:42 +01:00
under the following locations respectively:
- `/etc/letsencrypt/live/redxef.duckdns.org/`
- `/etc/letsencrypt/live/redxef.duckdns.org-0001/`
2020-10-29 16:38:49 +01:00
## ENV Variables
- DUCKDNS_DOMAIN: The domain to update, ex: DUCKDNS_DOMAIN=redxef for redxef.duckdns.org
2021-03-15 20:22:21 +01:00
- DUCKDNS_TOKEN: Your duckdns api token
2020-10-29 16:38:49 +01:00
- LE_EMAIL: Your email for certificate related notifications
2022-03-10 15:55:58 +01:00
## SOURCE
[gitea.redxef.at/redxef/certbot-duckdns](https://gitea.redxef.at/redxef/certbot-duckdns)