2025-04-14, 08:41 PM
Since it sounds like you are running Jellyfin in a VPS, we aren't concerned about "local" clients, right?
What you can try doing is switch Jellyfin to bridge networking, put it in caddy_net, and then have caddy use the bridge IP for reverse proxy.
Since Caddy is handling all connections, it makes sense to keep Jellyfin fully isolated in the bridge network. You don't even need to expose or publish any Jellyfin ports.
What you can try doing is switch Jellyfin to bridge networking, put it in caddy_net, and then have caddy use the bridge IP for reverse proxy.
Since Caddy is handling all connections, it makes sense to keep Jellyfin fully isolated in the bridge network. You don't even need to expose or publish any Jellyfin ports.
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]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
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