redxef/certbot-duckdns
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
No description
18 commits 1 branch 0 tags 52 KiB
Shell 86%
Dockerfile 14%
Find a file
redxef 4d6fc272ac
Remove deprecate --manual-public-ip-logging-ok flag.
2023-10-28 01:50:45 +02:00
ci Update ci. 2022-11-21 15:19:34 +01:00
etc/periodic Fix cron. 2021-03-15 20:22:21 +01:00
.dockerignore Add ci. 2022-03-10 15:54:41 +01:00
certbot-auth Resolve #1, remove misleading log output. 2022-03-10 16:12:50 +01:00
certbot-cleanup Better waiting for record updating. 2020-10-29 23:30:49 +01:00
certbot-duckdns Remove deprecate --manual-public-ip-logging-ok flag. 2023-10-28 01:50:45 +02:00
Dockerfile Add Volume for /etc/letsencrypt. 2022-03-10 16:12:13 +01:00
duckdns Fixed timout and other stuff. 2020-10-30 11:58:53 +01:00
README.md Add complete example. 2022-03-10 16:12:30 +01:00
start-certbot-duckdns.sh Fix cron. 2021-03-15 20:22:21 +01:00

README.md

Certbot with duckdns wildcard certificate

Just run it with the correct environment variables and enjoy.

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:

docker run --rm \
    -e DUCKDNS_DOMAIN=redxef \
    -e DUCKDNS_TOKEN=<your ddns token> \
    -e LE_EMAIL=noreply@example.com \
    redxef/certbot-duckdns

DUCKDNS_DOMAIN=redxef

Yields 2 certificates, the first being for redxef.duckdns.org and the second being for *.redxef.duckdns.org. These certificates can be found under the following locations respectively:

  • /etc/letsencrypt/live/redxef.duckdns.org/
  • /etc/letsencrypt/live/redxef.duckdns.org-0001/

ENV Variables

  • DUCKDNS_DOMAIN: The domain to update, ex: DUCKDNS_DOMAIN=redxef for redxef.duckdns.org
  • DUCKDNS_TOKEN: Your duckdns api token
  • LE_EMAIL: Your email for certificate related notifications

SOURCE

gitea.redxef.at/redxef/certbot-duckdns