Hi, i was looking for an already available image that included the cloudflare module to avoid building it myself locally or create yet another image on the Docker registry and i found yours!

It's just what i needed the only problem i have is that i'm trying to deploy it on a RPi 4 wich is an arm based system and your image only has builds for x64, i was wondering if you could add multi-arch support images

Thanks again

Forgive my ignorance, as I'm working on migrating from Namecheap registrar + DNS using Nginx Proxy Manager, to Namecheap registrar + Cloudflare DNS using Caddy.

Does this project have the ability to work with https://github.com/lucaslorentz/caddy-docker-proxy? That way I can define my desired subdomains using labels in my existing docker-compose.yaml file?

Additionally, is there a full example of a Caddyfile?

I think this should work:

tls {$CLOUDFLARE_EMAIL} { 
  dns cloudflare {$CLOUDFLARE_API_TOKEN}
}

Based on

https://caddyserver.com/docs/caddyfile/concepts#environment-variables

Does this image handle certificate renewal automatically? I set it up a few months ago and I'm getting emails from the Let's Encrypt Certificate Bot warning me that my certificates will soon expire (in 11 days). If not, do you know of how to manually force a renewal? Thanks

Caddy 2.7.2 is not recommended for use.

Hey @SlothCroissant

2.4.5 seems to be broken on Ubuntu Hosts. See here --> caddyserver/caddy#4118
Woke up this morning with this exact issue using your image.

Since your image does not provide tagged versions, I was unable to revert back to 2.4.3. So I edited a Dockerfile real quick to build caddy-cloudflaredns with 2.4.3. Worked perfectly. Sharing this here in case other people experience the same issue.

Issue is some random Go error like the follwing:

qtls.ClientHelloInfo doesn't match caddy

Solution for now:

1. Create a new folder.
2. nano Dockerfile
3. Paste:

FROM caddy:2.4.3-builder AS builder

RUN caddy-builder \
    github.com/caddy-dns/cloudflare

FROM caddy:2.4.3

COPY --from=builder /usr/bin/caddy /usr/bin/caddy

4. Build it:
   docker build -t caddyemergency .

5. Change your container image from slothcroissant/caddy-cloudflaredns to caddyemergency:latest

Run it, you should be fine. After caddy updates the main image with a fixed version, you may revert back to using slothcroissant/caddy-cloudflaredns

I didn't fill in an email address but still completed the DNS challenge and got the certificate,

i applied 3 domains ，2 succesed from let encrypt，the last one failed with “"error":"HTTP 404 urn:ietf:params:acme:error:malformed - Certificate not found"}”

then caddy tried ZeroSSL ，it succeed but with the msg “missing email address for ZeroSSL; it is strongly recommended to set one for next time”

I'd like to ask,

1. if I don't set email, what negative impact will it have?

2. Does this email address necessarily have to be The Cloudflare Email Address?

3. what should i do now？