Certbot DNS Cloudflare

Certbot DNS Cloudflare is a Certbot plugin that obtains and renews Let's Encrypt security certificates for domains on Cloudflare using the Domain Name System…

  • Infrastructure
  • Network Services
  • Tools & Utilities
Certbot DNS Cloudflare is a Certbot plugin that obtains and renews Let's Encrypt security certificates for domains on Cloudflare using the Domain Name System (DNS) challenge, so self-hosted site operators can automate certificate renewal without exposing a web validation endpoint.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

30/100 Low

Maintained
0last commit 792 days ago
Popular
3029 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
95no serious findings, CI, tests

Based on 4 of 5 factors.

GitHub stars
29
Open issues
7
Last commit
2024-09-20
Activity
stale

Checked 3 days ago - source: GitHub (cloudflare/certbot-dns-cloudflare)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Authenticator vs installer flags Certbot commands choose an authenticator (how it proves you own the domain) and an installer (how it puts the certificate into a web server). For DNS Cloudflare, the DNS authenticator is what proves ownership, and an installer is only needed if you also want Certbot to configure a web server; choosing the wrong combination can leave the certificate unissued or not installed. source
  • Keep live certificate files in place Certbot issues certificate files that web server configs may reference under /etc/letsencrypt/live/, such as fullchain.pem and privkey.pem. If you move, rename, or delete those files, HTTPS for the site can stop working until they are restored. source
  • Treat cli.ini as global settings If you use Certbot's cli.ini file, remember that its options apply to every certificate request and renewal. Keep it to stable defaults, because settings meant for one domain can accidentally affect other domains. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Is Certbot useful if my domain already uses Cloudflare?

If your site routes directly through Cloudflare DNS, Certbot can be the better fit. If you use Cloudflare Tunnel, Cloudflare certificates are fine.

Why does HTTP-01 fail when the site is behind Cloudflare?

Let's Encrypt cannot reach port 80 directly when the server is behind Cloudflare. In that setup, DNS validation is the relevant method.

Do I need an installer when using the Cloudflare DNS authenticator?

No; the DNS authenticator is what proves ownership. An installer is only needed if you also want Certbot to configure a web server.

What happens if I move or delete the issued certificate files?

HTTPS can stop working until the files are restored. Keep web-server-referenced files under /etc/letsencrypt/live/, such as fullchain.pem and privkey.pem, in place.

Are cli.ini settings per domain?

No; options in cli.ini apply to every certificate request and renewal. Use it for stable global defaults rather than domain-specific settings.

Answers sourced from gist.github.com, github.com, www.reddit.com

Community

Collected 48 days ago - public community threads