weidideng / caddy-cloudflare-ip Goto Github PK

heya, I'm building this with:

FROM caddy:builder AS builder

RUN xcaddy build \
	--with github.com/WeidiDeng/caddy-cloudflare-ip

FROM caddy:latest

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

But am getting this error when launching:

invalid IP address: 'cloudflare': ParseAddr("cloudflare"): unable to parse IP

Thsi is my Caddifile

{
	servers {
		trusted_proxies static 192.168.0.10 cloudflare {
			interval 12h
			timeout 15s
		}
	}
}

Hello,

Apologies, I have been researching for many hours, but haven't been able to find more information about this.

"trusted_proxies": {
  "source": "cloudflare",
  "interval": "12h",
  "timeout": "15s"
},

I understand under Caddy I can use this section above to fetch a list of trusted proxies. But why do I need caddy-cloudflare-ip when I have already enabled CloudFlare's proxy?

I'm planning to use Caddy with Xray to create the following VPN protocols that utilise Cloudflare CDN.

VLESS+gRPC+TLS
VLESS+WS+TLS
Trojan+gRPC+TLS
VMess+WS+TLS

Many Thanks

Hello, I've noticed, that if this plugin tries to refresh the list of trusted IPs (i.e. at startup), when no internet connection is available, the entire caddy server will hang until it is manually restarted.

This module is great.

Would it be possible to also add support for Caddy's remote_ip matcher as well?

It would be great if I would use the same up to date list of cloudflare proxy IPs to also reject requests not originating from cloudflare as well.

Thanks.

Hi, I would like to use this as a base for Caddy module for Bunny.net CDN provider. Could you add a license to this code?

After some google searching I have not come across examples of using this plugin properly. After entering the trusted_proxies cloudflare under servers, how are we to implement the checking of cloudflare proxies for something like a reverse_proxy?

{
	http_port 80
	https_port 443

	servers {
		trusted_proxies cloudflare {
			interval 12h
			timeout 15s
		}
	}
}

domain.example.com {
	route {
		reverse_proxy 192.168.1.100:8080
	}
}