Synolgy Running Jellyfin (while emby is running). With WORM protected drive

[jelly3388]

I'm posting this to both Synology and Jellyfin forums. Who helps best?

I have an emby server running right now on a synology NAS (920+). I would like to get a Jellyfin Server set up along side Emby. Jellyfin's Google/Andriod TV app crashes (Not trying to fix that). I fixed that by running an Emby server instead. But Jellyfin has more (free) features. I'm intresed in redownloading subtitles (lost them converting to .mp4, offline playback, and transcoding

MY PROBLEM:
Trying to get both servers running at once (adding Jellyfin). Installing via community packages on Synolgy there is no way to customize the port. Since they both use the same port I cannot run both via this method. I have emby running this way. Docker won't work either. When in container manager (docker) and I try to use the GUI to add a mounted folder the folder does not show up. I'm using WORM (write once bit locker attack protection) for the video files. This is the issue. I tried making two new folders I put a video in for testing. The same settings one with WORM one not. The WORM folder cannot be located in the GUI via container manager's add folder button in advanced settings.

I see three possible approaches to solve this problem and get both Emby and Jellyfin running at the same time (adding Jellyfin). I don't know enough Execute any of them.

1. Some how feed the video folder locattion to container manager through environmental variables. Not sure it is possible. But I think I can add new ones from the gui.
2.modify the file from synocommunity that installs Jellyfin. And modify the file to change the port. And then I think the modified file could be side loaded.

3. (haven't attempted yet) Host Jellyfin in a Ubuntu VM. I would be comfortable doing most of this. However I think I would run into issues making the VM see the files on the host NAS. (The video files should remain there).

If anyone has any ideas on making this work via any method listed or another alternative that would be very helpful.

[Efficient_Good_5784]

I would skip out on running the SynoCommunity Jellyfin app and instead use the Container Manager for running the official Jellyfin image directly.

As you found out, Emby and Jellyfin share the same port number. I never used the SynoCommunity app, but most likely it forces you to use port 8096.
Using Docker, you can specify which port you want Jellyfin to be accessible from.

Furthermore, you can't access the folders you want from the GUI. You can try to directly declare them by using Docker Compose by writing out the full path to the directories that you need.

I made a guide for using Container Manager to launch Jellyfin: https://forum.jellyfin.org/t-guide-runni...er-compose

If you follow the guide, where the ports are declared in the compose file, you would simply do somethings like this as an example:
    - 8097:8096/tcp
With this declaration, you have made Jellyfin be accessible from port 8097 meaning that you won't get that port conflict when another service is using 8096.

[jelly3388]

this solution looks promising I'll report back when I get a chance to try it.