CloudflareSSL

A small Docker container that generates Let's Encrypt certificates for Unraid using the Cloudflare API allowing to avoid "this page is not secure" warnings…

  • Security
  • Tools & Utilities
A small Docker container that generates Let's Encrypt certificates for Unraid using the Cloudflare API allowing to avoid "this page is not secure" warnings when connecting to Unraid locally.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • 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.

43/100 Fair

Maintained
68last commit 96 days ago
Popular
187 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM

Availability: platform listings confirmed today, links checked 27 days ago

GitHub stars
7
Open issues
0
Last commit
2026-08-16
Latest release
0.3.0
License
GPL-3.0
Activity
stale

Checked 9 days ago - source: GitHub (tenasi/cloudflaressl)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

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

First-install notes

  • First install The container runs Certbot with the Cloudflare DNS challenge, obtaining a trusted Let's Encrypt certificate for Unraid without opening inbound ports or running a reverse proxy. Set your Cloudflare API credentials as environment variables as documented in the README; the image is based on serversideup/docker-certbot-dns-cloudflare. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I request one certificate for multiple domains in this container?

Yes, set CERTBOT_DOMAINS to a comma-separated list of domains for the certificate.

How do I handle slow DNS propagation when the DNS challenge runs?

Set CLOUDFLARE_PROPAGATION_SECONDS to the wait time, in seconds, after setting the DNS TXT records before validation. The default is 10 seconds.

How do I change the name of an existing certificate?

Set CERTBOT_CERT_NAME to the certificate name to update or modify. CERTBOT_EXPAND is deprecated, and CERTBOT_CERT_NAME is the replacement.

How can I make the container run once instead of renewing periodically?

Set RENEWAL_INTERVAL to 0 to disable renewal checks and only run once. Otherwise it checks every 43200 seconds, or 12 hours, by default.

Does issuing these certificates require exposing ports or running a proxy?

No, it uses a DNS challenge via the Cloudflare API to request Let's Encrypt certificates for Unraid without exposing ports or running a proxy.

What Cloudflare credentials does the container use?

Set CLOUDFLARE_API_TOKEN to a Cloudflare API token for DNS authentication, or point CLOUDFLARE_CREDENTIALS_FILE to a credentials file such as the default /cloudflare.ini. Treat the token like a password because it can modify DNS records.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads