• 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 Jellyfin logs not showing real IP of users

     
    • 0 Vote(s) - 0 Average

    Jellyfin logs not showing real IP of users

    tanton
    Offline

    Junior Member

    Posts: 4
    Threads: 2
    Joined: 2025 May
    Reputation: 0
    #1
    2025-05-17, 07:43 PM
    Hello 

    I have setup jellyfin behind caddy reverse proxy for external access and it works great. However, all users are shown the docker network ip (172.17.0.1) and not the actual ip. I have put the same IP in the known proxies setting but it's still not showing actual ip. Here is the Caddyfile section of jellyfin

    }

    jellyfin.domain.com {
        reverse_proxy 192.168.1.x:8096
    }

    Here is the logs from caddy

    {"level":"error","ts":1747510332.4433181,"logger":"http.log.error","msg":"dial tcp 192.168.1.x:8096: connect: connection refused","request":{"remote_ip":"172.17.0.1","remote_port":"51466","client_ip":"172.17.0.1","proto":"HTTP/2.0","method":"GET","host":"jellyfin.domain.com","uri":"/ScheduledTasks?IsEnabled=true","headers":{"Authorization":["REDACTED"],"User-Agent":["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36"],"Accept":["application/json"],"Sec-Ch-Ua":["\"Chromium\";v=\"136\", \"Google Chrome\";v=\"136\", \"Not.A/Brand\";v=\"99\""],"Sec-Fetch-Site":["same-origin"],"Dnt":["1"],"Sec-Fetch-Mode":["cors"],"Accept-Language":["en-US,en;q=0.9"],"Accept-Encoding":["gzip, deflate, br, zstd"],"Priority":["u=1, i"],"Sec-Ch-Ua-Platform":["\"Windows\""],"Sec-Ch-Ua-Mobile":["?0"],"Sec-Fetch-Dest":["empty"]},"tls":{"resumed":false,"version":772,"cipher_suite":4865,"proto":"h2","server_name":" jellyfin.domain.com"}},"duration":0.000554603,"status":502,"err_id":"866vwhqnp","err_trace":"reverseproxy.statusError (reverseproxy.go:1390)"}
    bitmap
    Offline

    Community Moderator

    Posts: 809
    Threads: 9
    Joined: 2023 Jul
    Reputation: 26
    #2
    2025-05-17, 08:06 PM
    Caddy is throwing out the x-forwarded-for headers because they're coming from untrusted IPs. I wish I knew enough about Caddy to figure out what needs to be done to get the real IPs. I gathered you can add each IP you trust as a trusted proxy, but that seems absolutely bonkers -- maybe it's your public IP or domain admin servers? In essence, you need to stop Caddy from tossing this value.
    Jellyfin 10.10.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage

    [Image: AIL4fc84QG6uSnTDEZiCCtosg7uAA8x9j1myFaFs...qL0Q=w2400]
    theguymadmax
    Offline

    Community Moderator

    Posts: 1,075
    Threads: 0
    Joined: 2024 Jun
    Reputation: 58
    #3
    2025-05-17, 08:22 PM
    (2025-05-17, 07:43 PM)tanton Wrote: Hello 

    I have setup jellyfin behind caddy reverse proxy for external access and it works great. However, all users are shown the docker network ip (172.17.0.1) and not the actual ip. I have put the same IP in the known proxies setting but it's still not showing actual ip. Here is the Caddyfile section of jellyfin

    }

    jellyfin.domain.com {
        reverse_proxy 192.168.1.x:8096
    }

    You need to enter the host ip in known proxies, which would be 192.168.1.x  
    After you make the change, restart the server, to apply changes.
    Generator
    Offline

    Junior Member

    Posts: 37
    Threads: 0
    Joined: 2025 May
    Reputation: 3
    #4
    2025-05-17, 09:37 PM
    Add caddy to the same docker network as jellyfin, and add the container hostname (ex: caddy) to known proxies
    https://jellyfin.org/docs/general/post-i...wn-proxies

    You can add by IP, but recommend to set the container a static IP
    tanton
    Offline

    Junior Member

    Posts: 4
    Threads: 2
    Joined: 2025 May
    Reputation: 0
    #5
    2025-05-17, 11:25 PM
    (2025-05-17, 08:22 PM)theguymadmax Wrote: You need to enter the host ip in known proxies, which would be 192.168.1.x  
    After you make the change, restart the server, to apply changes.

    I have tried. Still didn't work.

    (2025-05-17, 09:37 PM)Generator Wrote: Add caddy to the same docker network as jellyfin, and add the container hostname (ex: caddy) to known proxies
    https://jellyfin.org/docs/general/post-i...wn-proxies

    You can add by IP, but recommend to set the container a static IP

    I just tried to add jellyfin to the same caddy network, I put caddy as known proxy and also tried the caddy network ip range but still didn't work.
    pxr5
    Offline

    Member

    Posts: 52
    Threads: 3
    Joined: 2024 Jan
    Reputation: 3
    Country:United Kingdom
    #6
    2025-05-18, 06:36 PM
    ^ You must restart the server for after adding the caddy ip to known proxies. Also do a hard reset on your browser. My caddy file is the same as yours and I had to do the add proxy/restart server/hard reset before it worked. I added this for my proxy: 192.168.1.xxx/24
    Jellyfin1 - 10.10.3 (Docker) Synology NAS (transcoding off)
    Jellyfin2 - 10.10.3 Minix ZX100-0db MiniPC, Intel N100 (transcoding on)
    Storage - x3 Synology NAS (22TB)
    Reverse Proxy - Caddy v2 running on a Pi3b+
    « 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