starred/caddy-cloudflare

Fork 0

mirror of https://github.com/CaddyBuilds/caddy-cloudflare.git synced 2026-04-26 12:35:55 +03:00

[GH-ISSUE #20] Cloudflare DDNS #7

New issue

Closed

opened 2026-02-27 19:08:49 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 19:08:49 +03:00

Owner

Originally created by @Brunio25 on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/CaddyBuilds/caddy-cloudflare/issues/20

Hey!
First of all, thanks for providing this image, it has been quite handy 😄
I was wondering if you would consider adding the https://github.com/caddy-dns/cloudflare Dyamic DNS Cloudflare module to this image. It seems to make sense since it would be a toolset for cloudflare specifically.

Thanks!

Originally created by @Brunio25 on GitHub (Jul 14, 2025). Original GitHub issue: https://github.com/CaddyBuilds/caddy-cloudflare/issues/20 Hey! First of all, thanks for providing this image, it has been quite handy 😄 I was wondering if you would consider adding the https://github.com/caddy-dns/cloudflare Dyamic DNS Cloudflare module to this image. It seems to make sense since it would be a toolset for cloudflare specifically. Thanks!

kerem closed this issue

2026-02-27 19:08:49 +03:00

kerem commented

2026-02-27 19:08:50 +03:00

Author

Owner

@vkartk commented on GitHub (Jul 28, 2025):

Hey @Brunio25 !

Thanks for the kind words.

Just to clarify: the github.com/caddy-dns/cloudflare module is actually already built into the image. If you take a look at the Dockerfile, you’ll see it’s included during the build process.

So I’m a little confused. Are you running into an issue where it seems like the module isn’t available?
Happy to help debug if that's the case!

Thanks again!
Karthik

@vkartk commented on GitHub (Jul 28, 2025): Hey @Brunio25 ! Thanks for the kind words. Just to clarify: the `github.com/caddy-dns/cloudflare` module is actually already built into the image. If you take a look at the [Dockerfile](https://github.com/CaddyBuilds/caddy-cloudflare/blob/main/Dockerfile), you’ll see it’s included during the build process. So I’m a little confused. Are you running into an issue where it seems like the module isn’t available? Happy to help debug if that's the case! Thanks again! Karthik

kerem commented

2026-02-27 19:08:50 +03:00

Author

Owner

@francislavoie commented on GitHub (Aug 18, 2025):

I think they were asking to also have https://github.com/mholt/caddy-dynamicdns which cloudflare can be plugged into.

But I'd also point out https://github.com/WeidiDeng/caddy-cloudflare-ip which can allow trusting Cloudflare IPs for trusted proxies

@francislavoie commented on GitHub (Aug 18, 2025): I think they were asking to also have https://github.com/mholt/caddy-dynamicdns which cloudflare can be plugged into. But I'd also point out https://github.com/WeidiDeng/caddy-cloudflare-ip which can allow trusting Cloudflare IPs for trusted proxies

kerem commented

2026-02-27 19:08:50 +03:00

Author

Owner

@vkartk commented on GitHub (Aug 19, 2025):

Hello @francislavoie,

Thank you for clarifying!

That makes more sense now, I would prefer not to build caddy-dynamicdns into the main caddy-cloudflare image since most people will either have static IP or are just using a dedicated DDNS client.

I’ll have caddy-cloudflare-ddns out soon.

As for caddy-cloudflare-ip, I personally think inbound ~~proxy trust~~ is much better done at the firewall, and it doesn't seem like that repo is being maintained very actively. But I can consider it if there’s enough interest.

@vkartk commented on GitHub (Aug 19, 2025): Hello @francislavoie, Thank you for clarifying! That makes more sense now, I would prefer not to build caddy-dynamicdns into the main caddy-cloudflare image since most people will either have static IP or are just using a dedicated DDNS client. I’ll have `caddy-cloudflare-ddns` out soon. As for `caddy-cloudflare-ip`, I personally think inbound <del>proxy trust</del> is much better done at the firewall, and it doesn't seem like that repo is being maintained very actively. **But I can consider it if there’s enough interest.**

kerem commented

2026-02-27 19:08:50 +03:00

Author

Owner

@francislavoie commented on GitHub (Aug 19, 2025):

No, proxy trust must be at the proxy. It's necessary for properly handing X-Forwarded-For headers etc. It's not a firewall thing. Also, it ensures your access logs have the correct IP in them instead of always appearing as if all requests come from Cloudflare.

That repo is maintained, it's just that there's nothing to maintain! All it does is fetch the list of IPs from https://www.cloudflare.com/ips-v4/ every hour and return that in a function. There's nothing else to do at all. As a Caddy maintainer, I give my stamp of a approval, Weidi is also one of the core maintainers, it's trusted.

Config looks like this:

{
	servers {
		trusted_proxies cloudflare
		client_ip_headers Cf-Connecting-Ip
	}
}

@francislavoie commented on GitHub (Aug 19, 2025): No, proxy trust _must_ be at the proxy. It's necessary for properly handing X-Forwarded-For headers etc. It's not a firewall thing. Also, it ensures your access logs have the correct IP in them instead of always appearing as if all requests come from Cloudflare. That repo _is_ maintained, it's just that there's nothing to maintain! All it does is fetch the list of IPs from https://www.cloudflare.com/ips-v4/ every hour and return that in a function. There's nothing else to do at all. As a Caddy maintainer, I give my stamp of a approval, Weidi is also one of the core maintainers, it's trusted. Config looks like this: ```caddyfile { servers { trusted_proxies cloudflare client_ip_headers Cf-Connecting-Ip } } ```

kerem commented

2026-02-27 19:08:50 +03:00

Author

Owner

@vkartk commented on GitHub (Aug 20, 2025):

That makes sense about proxy trust needing to be at the proxy itself for proper X-Forwarded-For handling and correct IP in logs.

Also good to know the caddy-cloudflare-ip module is stable and trusted by maintainers.

I’ll go ahead and have it built into both caddy-cloudflare and caddy-cloudflare-ddns starting with the next Caddy release.

@vkartk commented on GitHub (Aug 20, 2025): That makes sense about proxy trust needing to be at the proxy itself for proper `X-Forwarded-For` handling and correct IP in logs. Also good to know the `caddy-cloudflare-ip` module is stable and trusted by maintainers. I’ll go ahead and have it built into both **`caddy-cloudflare`** and **`caddy-cloudflare-ddns`** starting with the next Caddy release.

kerem commented

2026-02-27 19:08:50 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 19, 2025):

This issue has been automatically marked as stale due to inactivity. If no further activity occurs, it will be closed in 7 days.

@github-actions[bot] commented on GitHub (Sep 19, 2025): This issue has been automatically marked as stale due to inactivity. If no further activity occurs, it will be closed in 7 days.

kerem commented

2026-02-27 19:08:50 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 23, 2025):

This issue has been automatically marked as stale due to inactivity. If no further activity occurs, it will be closed in 7 days.

@github-actions[bot] commented on GitHub (Oct 23, 2025): This issue has been automatically marked as stale due to inactivity. If no further activity occurs, it will be closed in 7 days.

kerem referenced this issue

2026-02-27 19:08:52 +03:00

[PR #8] [MERGED] ci: Handle unavailable Caddy versions and update version checking #15