2025-04-09, 05:20 PM
I have 2 instances of Jellyfin running. One, bare metal on a Win11 Pro MiniPC and the other in docker on a Synology NAS. Both are behind a reverse proxy running directly on a Raspberry Pi. The Caddyfile contains the same commands for each Jellyfin server. I've set the trusted proxies on both instances of Jellyfin to 192.168.1.100/24 - which is the IP address of the Pi running Caddy. Everything works OK and both instances reports the correct IP address of the remote connection and not of the Pi running Caddy.
I looked at some information on Caddy and it seems that the headers are forwarded by default so my simple Caddy file appears to be fine without any extra forward headers.
It's important to restart the Jellyfin server for this to kick in properly as without a reboot the remote connections will incorrectly report the ip of the caddy proxy.
I looked at some information on Caddy and it seems that the headers are forwarded by default so my simple Caddy file appears to be fine without any extra forward headers.
It's important to restart the Jellyfin server for this to kick in properly as without a reboot the remote connections will incorrectly report the ip of the caddy proxy.
Jellyfin1 - 10.10.7 (Docker) Synology NAS (transcoding off)
Jellyfin2 - 10.10.7 Minix ZX100-0db MiniPC, Intel N100 (transcoding on)
Storage - x3 Synology NAS (22TB)
Reverse Proxy - Caddy v2 running on a Pi3b+
Jellyfin2 - 10.10.7 Minix ZX100-0db MiniPC, Intel N100 (transcoding on)
Storage - x3 Synology NAS (22TB)
Reverse Proxy - Caddy v2 running on a Pi3b+