![]() |
Real Client IP Not Showing Behind Proxy - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: Real Client IP Not Showing Behind Proxy (/t-real-client-ip-not-showing-behind-proxy) |
Real Client IP Not Showing Behind Proxy - alchemy - 2024-04-15 Hey everyone, I'm having some trouble getting jellyfin to correctly register client IPs. I currently have it partially behind cloudflare for the sign-in etc, so html stuff only and no TOS issues. I am also reverse proxying through Caddy. Currently I have caddy built with the cloudflare trusted_proxies module and therefore have this directive in my config:
in my request logs for caddy I have the following, where remote_ip is a cloudflare ip, and all other entries are my true IP. handled request {"request": {
Though the requests look like this, in Jellyfin's UI I am still seeing cloudflare addresses attached to user activity. Jellyfin and Caddy are running on the same debian machine. I'm still not sure I entirely understand the "known proxies" configuration option in jellyfin. I'm hoping I wouldn't have to list the cloudflare proxies as this is 20 megabytes of text and the codebase suggests comparing these searches through a list. I've tried adding what should be my Caddy IP as jellyfin sees it (127.0.0.1) but this hasn't worked. Thanks so much for any help. RE: Real Client IP Not Showing Behind Proxy - TheDreadPirate - 2024-04-16 Known proxies would need to be 100.100.100.100. Once you've specified that it will use the "X-Forwarded-For" field for the client IP in the dashboard. RE: Real Client IP Not Showing Behind Proxy - alchemy - 2024-04-16 Ah I'm blind, I see now in the codebase that the known proxies list does indeed include support for CIDR blocks. Thanks so much! |