• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Networking & Access SOLVED: Client IPs with reverse proxy not showing correct

     
    • 0 Vote(s) - 0 Average

    SOLVED: Client IPs with reverse proxy not showing correct

    th0str
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Jan
    Reputation: 0
    #1
    2025-01-13, 05:57 PM
    I have an issue with client IPs on reverse proxy.

    When accessing my jellyfin server from jellyfin.mydomain.zxz all my client IP are listed as my gateways IP address (192.168.1.1) - regardless of the clients are located on my local network or as a remote connection. But they show correctly then accessing the server locally.

    Im using Traefik 3.3.1 and Jellyfin 10.10.3

    My network settings are as following:

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <BaseUrl />
      <EnableHttps>false</EnableHttps>
      <RequireHttps>false</RequireHttps>
      <InternalHttpPort>8096</InternalHttpPort>
      <InternalHttpsPort>8920</InternalHttpsPort>
      <PublicHttpPort>8096</PublicHttpPort>
      <PublicHttpsPort>8920</PublicHttpsPort>
      <AutoDiscovery>true</AutoDiscovery>
      <EnableUPnP>false</EnableUPnP>
      <EnableIPv4>true</EnableIPv4>
      <EnableIPv6>false</EnableIPv6>
      <EnableRemoteAccess>true</EnableRemoteAccess>
      <LocalNetworkSubnets />
      <LocalNetworkAddresses>
        <string>192.168.1.200</string>
      </LocalNetworkAddresses>
      <KnownProxies>
        <string>traefik</string>
      </KnownProxies>
      <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
      <VirtualInterfaceNames>
        <string>veth</string>
      </VirtualInterfaceNames>
      <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
      <PublishedServerUriBySubnet />
      <RemoteIPFilter />
      <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
    </NetworkConfiguration>
    Go to solution
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2025-01-13, 06:00 PM
    You have to add 192.168.1.1 as a known proxy. "traefik" in that field doesn't do anything. If traefik is on a different box, you may need to add additional IPs to known proxies (comma separated).
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    th0str
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Jan
    Reputation: 0
    #3
    2025-01-13, 06:13 PM
    (2025-01-13, 06:00 PM)TheDreadPirate Wrote: You have to add 192.168.1.1 as a known proxy.  "traefik" in that field doesn't do anything.  If traefik is on a different box, you may need to add additional IPs to known proxies (comma separated).

    That is also my guess but don't change anything if I set 192.168.1.1 as a know proxy. Clients are still reporting with the same IP.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2025-01-13, 06:33 PM
    Did you restart Jellyfin? IIRC, everything in the network section requires a restart to apply the change.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    th0str
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Jan
    Reputation: 0
    #5
    2025-01-13, 07:28 PM
    Yes I have restarted server after making the changes in Network settings
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2025-01-13, 07:42 PM
    Is the x-forwarded-for header set in traefik?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    th0str
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Jan
    Reputation: 0
    #7
    2025-01-15, 05:38 PM
    I found the issue. Cloudflare did not forward headers and after I fixed that, the IPs showed up correctly
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #8
    2025-01-15, 06:00 PM
    For the record, using cloudflare to proxy video and audio streams is against their TOS. We recommend you switch to DNS only in the cloudflare dashboard.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode