You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I replace X-Forwarded-For with X-Real-IP, then the server is able to read client real IP. I don't know if this is caused by caddy or dns-over-https.
The text was updated successfully, but these errors were encountered:
Doh-server is programmed to require the client IP to be a globally routable IP. (In other words, if your server is in the same private network with your client, doh-server may see something like 192.168.114.191 and decide to ignore that, since it cannot help with GeoDNS.)
Can you check whether the submitted X-Forwarded-For IP is a globally routable one?
If there are multiple X-Forwarded-For IPs, doh-server deletes any non-global IPs and then chooses the farthest one on the proxy chain for GeoDNS.
Using
caddy
as reverse proxy and Cloudflare as CDN service.Cannot read client real IP with header
X-Forwarded-For
Part of caddy configuration:
If I replace
X-Forwarded-For
withX-Real-IP
, then the server is able to read client real IP. I don't know if this is caused bycaddy
ordns-over-https
.The text was updated successfully, but these errors were encountered: