2024-08-25, 10:46 PM
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.
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.