Switching from Emby to Jellyfin - Roku client - Ubuntu server
from jaybone@lemmy.world to jellyfin@lemmy.ml on 29 Dec 2023 06:57
https://lemmy.world/post/10084607

Some questions and comments on my experience.

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
<   8096
<   8920
<   8096
<   8920
---
>   18096
>   18920
>   18096
>   18920

#jellyfin

threaded - newest

jaybone@lemmy.world on 29 Dec 2023 07:01 next collapse

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
<   8096
<   8920
<   8096
<   8920
---
>   18096
>   18920
>   18096
>   18920
jaybone@lemmy.world on 29 Dec 2023 07:03 collapse

And it still didn’t.

entropicdrift@lemmy.sdf.org on 29 Dec 2023 08:41 next collapse

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.

Sasha@lemmy.blahaj.zone on 29 Dec 2023 08:43 collapse

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