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.

  • zerodawn@leaf.danceOPEnglish
    1·
    3 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.

  • frongt@lemmy.zipEnglish
    3·
    3 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.worksEnglish
    2·
    3 days ago

    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.danceOPEnglish
      2·
      3 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.