34

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!

top 13 comments
sorted by: hot top controversial new old
[-] scottmeme@sh.itjust.works 23 points 5 months ago

Be careful about using video over the cloudflare proxy, they will come after you if you are using a TON of bandwidth

[-] notdeadyet@lemmy.dbzer0.com 3 points 5 months ago

Do you know of a way to have a global caddy setting to only allow Cloudflare IPs, but "exempt" Jellyfin?

(I posted my caddy cloudflare section down below which only works as a global setting)

[-] scottmeme@sh.itjust.works 8 points 5 months ago* (last edited 5 months ago)

You would change it from orange cloud to gray cloud to disable the proxy in your domain DNS settings.

Specifically for the jellyfin subdomain.

That would be the correct solution IMO.

[-] Auli@lemmy.ca 1 points 5 months ago

I thought that is was not against their TOS now.

[-] scottmeme@sh.itjust.works 0 points 5 months ago* (last edited 5 months ago)

I haven't heard any such thing unless you are paying for their video CDN which isn't cheap

[-] Toes@ani.social 6 points 5 months ago
[-] notdeadyet@lemmy.dbzer0.com 3 points 5 months ago

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

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.

[-] DarkSirrush@lemmy.ca 3 points 5 months ago

Authelia has a page on cloudflare, does this help at all? Note that I use traefik as my reverse proxy and am not using any of cloudflares advanced features.

https://www.authelia.com/integration/proxies/forwarded-headers/#cloudflare

[-] notdeadyet@lemmy.dbzer0.com 1 points 5 months ago

Thanks for the suggestion. I followed that and it didn't solve the problem sadly.

[-] Decronym@lemmy.decronym.xyz 1 points 5 months ago* (last edited 5 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
CF CloudFlare
DNS Domain Name Service/System
IP Internet Protocol

3 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

[Thread #802 for this sub, first seen 14th Jun 2024, 03:05] [FAQ] [Full list] [Contact] [Source code]

this post was submitted on 13 Jun 2024
34 points (97.2% liked)

Selfhosted

40406 readers
264 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS