Selfhosted

40329 readers

419 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Jellyfin, Caddy, and Cloudflare Real IP (lemmy.dbzer0.com)

submitted 5 months ago by notdeadyet@lemmy.dbzer0.com to c/selfhosted@lemmy.world

13 comments fedilink hide all child comments

Hello everyone,

I currently have Jellyfin running through Caddy and Cloudflare as reverse proxies.

I have tried everything and can't seem to get Jellyfin to report anything but the Cloudflare IP for clients.

Does anyone have a similar setup and could help me troubleshoot this? I can share whatever configs I am using as required.

Thanks!

you are viewing a single comment's thread
view the rest of the comments

[–] Toes@ani.social 6 points 5 months ago (1 children)

Track the CF-Connecting-IP field instead of the IP address to get the client.

https://developers.cloudflare.com/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/

[–] notdeadyet@lemmy.dbzer0.com 3 points 5 months ago (2 children)

I have followed that guide which let me to a few GitHub issues.

Here is what I have put in my config:

servers {
        trusted_proxies cloudflare {
                        interval 12h
                        timeout 15s
                }
        trusted_proxies static private_ranges
        client_ip_headers Cf-Connecting-Ip X-Forwarded-For
        }
}

I have also added all Cloudflare IPs in Jellyfin's known proxies:

103.21.244.0/22, 103.22.200.0/22, 103.31.4.0/22, 104.16.0.0/13, 104.24.0.0/14, 108.162.192.0/18, 131.0.72.0/22, 141.101.64.0/18, 162.158.0.0/15, 172.64.0.0/13, 173.245.48.0/20, 188.114.96.0/20, 190.93.240.0/20, 197.234.240.0/22, 198.41.128.0/17

Yet, I'm still not seeing the real IPs.

[–] SteveTech@programming.dev 2 points 5 months ago

I have also added all Cloudflare IPs in Jellyfin's known proxies

You should only need to add the IP of the last proxy before reaching Jellyfin, which would be Caddy.

[–] Toes@ani.social 1 points 5 months ago (1 children)

Using a whitelist in this manner with cloudflare may be challenging as this list can potentially change. They do have means to query it though. https://developers.cloudflare.com/api/operations/cloudflare-i-ps-cloudflare-ip-details Additionally, have you considered ipv6 support?

if you haven't solved the problem yet, I would consider switching to Apache for your reverse proxy and using mod_remoteip.

[–] notdeadyet@lemmy.dbzer0.com 2 points 5 months ago

I might have to switch, as much as I like the simplicity of Caddy, I keep running into issues like this unfortunately.