x-forwarded-for IP for docker compose stack?

[fhireman]

Hi there,

I've been running jellyfin for about half a year now on my own server and recently port forwarded it so my parents can enjoy it as well.
I've seen my internal Docker network IP pop up in the logs on the Jellyfin dashboard but not the actual external IP from my parents.

Normally this would be the x-forwarded-for header that gets passed automatically through Caddy as a reverse proxy but I'm unsure how to tell Jellyfin to use this header IP instead of the Docker internal network one?

My compose stack looks like this right now:

Code:

services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    container_name: jellyfin
    volumes:
      - /home/jellyfin/config:/config
      - /home/jellyfin/cache:/cache
      - /mnt/media:/media
    expose:
      - "8096"
    devices:
      - /dev/dri/renderD129:/dev/dri/renderD129
    environment:
      - PUID=1000
      - PGID=993
    group_add:
      - "993"
    networks:
      - jellyfin-net
    restart: unless-stopped

  caddy:
    image: caddy:latest
    container_name: caddy
    ports:
      - "80:80"
    volumes:
      - ./conf:/etc/caddy
    depends_on:
      - jellyfin
    networks:
      - jellyfin-net
    restart: unless-stopped

networks:
  jellyfin-net:
    driver: bridge

I saw that a lot of the logs that have IPs in them were in the /home/jellyfin/config dir so I assume I need to point my Fail2Ban jail to these logfiles to pick up on failed logins?


Thanks in advance!

[bitmap]

Add your docker IP to the known proxies, which should help.

[fhireman]

Thanks, will try.
Saw that it does require a baseURL to be set before it works but I'll try it out