2024-09-26, 01:15 PM
(This post was last modified: 2024-09-26, 01:38 PM by pxr5. Edited 1 time in total.)
I think I may have misunderstood how this works and that Jellix needs to be run on the same server as Jellyfin. I've just spun up a container on my Synology NAS (where Jellyfin is installed) and it works fine with the same compose file. I have another instance of Jellyfin running on a MiniPC and pointed the same container at that IP address and it doesn't work. So all is good my end.
I'm now wondering how I could access Jellfix remotely as I use a reverse proxy normally. Maybe just another entry in the Caddy file for 192.168.1.43:3000 - I'll do some testing when I get chance.
Only movies though, is that right?
I'm now wondering how I could access Jellfix remotely as I use a reverse proxy normally. Maybe just another entry in the Caddy file for 192.168.1.43:3000 - I'll do some testing when I get chance.
Only movies though, is that right?
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+