My main motivation to switch was that emby seemed to be buggy on the client side, keeping track of what episode of what tv show and season I was on. I'm hoping jellyfin helps with that.

On the server side, I wanted to keep both servers running. But there were port conflicts. It was difficult for me to find in the Jellyfin docs the right config file to set the ports. So I ended up changing the emby ports. (Since I could find the emby config files.)

diff /var/lib/emby/config/system.xml.orig /var/lib/emby/config/system.xml 
9,12c9,12
&lt;   8096
&lt;   8920
&lt;   8096
&lt;   8920
***
>   18096
>   18920
>   18096
>   18920

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 5 points 6 months ago

You can avoid port conflicts by using containers, you can let Jellyfin use its default but map it to something else externally

[–] jaybone 2 points 6 months ago (1 children)

Uh, that did not insert a code block very well.

diff /var/lib/emby/config/system.xml.orig /var/lib/emby/config/system.xml 
9,12c9,12
&lt;   8096
&lt;   8920
&lt;   8096
&lt;   8920
***
>   18096
>   18920
>   18096
>   18920

[–] jaybone 3 points 6 months ago

And it still didn't.

[–] [email protected] 2 points 6 months ago

Did you have a question?

I use Jellyfin in a docker container. With docker you can change themapping of ports within the container to the ports on the host machine, so if I needed to change the ports that's how I'd do it. No idea how it's done with Jellyfin installed natively though.