this post was submitted on 14 Sep 2025
4 points (100.0% liked)

Jellyfin: The Free Software Media System

7499 readers
15 users here now

Current stable release: 10.10.7

Community Standards

Website

Forum

GitHub

Documentation

Feature Requests

Matrix (General Information & Help)

Matrix (Announcements)

Matrix (General Development)

Matrix (Off-Topic) - Come get to know the team and blow off steam!

Matrix Space - List of all the available rooms on Matrix.

Discord - Bridged to our Matrix rooms

founded 5 years ago
MODERATORS
 

I'm not sure where else to ask this other than maybe self-hosted, so let me know if I'm in the wrong place. I'm trying to overcome a minor issue with Jellystat. Coming from Plex, I used Tautulli fairly heavily, and one of the features I'd use for various internal monitoring was the IP address tracking. Jellystat has IP address tracking, but unfortunately, due to the structure of my network, it only shows the address of my firewall when the connection is coming from outside my network.

I'm fairly sure this isn't an issue with Plex, since their site does the authentication and the service exits through NAT port forwarding, but with Jellyfin, I use a reverse proxy to route all external traffic as needed. I'm open to additional software or different methods of tracking, but I'm not sure where to start. Any advice would be appreciated.

top 5 comments
sorted by: hot top controversial new old
[–] Certainly_No_Brit@discuss.tchncs.de 4 points 6 days ago* (last edited 6 days ago)

A reverse proxy should include an X-Forwarded-For header in every proxied http request (or you have to configure the proxy to include it). JellyStat gets all info about the sessions from Jellyfin, where you can set trusted proxies in the Networking section.

Look at this documentation: https://jellyfin.org/docs/general/post-install/networking/reverse-proxy

[–] frongt@lemmy.zip 3 points 6 days ago

You will need to configure your proxy to pass that information, and your analytics to read it. Usually this is the x-forwarded-for header.

[–] NeryK@sh.itjust.works 2 points 6 days ago (1 children)

You should make Jellyfin aware of your reverse-proxy IP address or hostname: (in my case localhost as the reverse proxy is running on the same machine).

How to send the X-Forwarded-For header depends on your reverse-proxy. In Caddy which I use, it does it by default.

[–] zerodawn@leaf.dance 2 points 6 days ago

This was the second half of the fix that I needed. I filled this box with the address that shows when external connections would authenticate or play, and set "forwardfor" at the proxy, then the information came through. Thank you for this.

[–] zerodawn@leaf.dance 1 points 6 days ago

Turns out it was as simple as checking a box in my reverse proxy settings to enable "forwardfor" now to wait and see if the information actually gets passed through or if I have to do as NeryK suggests and enter the address in Jellyfin.