2025-02-17, 10:30 PM
If LAN client's don't need direct access to Jellyfin (not through reverse proxy) you should remove the port publishing for port 8096. Assuming that Caddy and Jellyfin are on the same bridge network, port publishing is not needed. This would reduce the number of times traffic needs to jump between the host and bridge network stacks.
Can you share the current state of your caddy and Jellyfin docker compose and the caddyfile?
Can you share the current state of your caddy and Jellyfin docker compose and the caddyfile?
Jellyfin 10.10.6 (Docker)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)