Jellyfin Port Reallocation Failure, Stumped the TomBot
Posted by sistertrout
My question: Originally, I asked if I could use my pre-existing Emby server instead of JellyFin. Jellyfin fails to start because it's allocated to the same port as my current Emby install. Turning off Emby is a no-op, I paid for Premiere and it should theoretically be possible to either use both or only use Emby. TomBot said this wasn't possible, and gave me the command to reallocate Jellyfin's port to run both off the same media library. On restart, Jellyfin still didn't come up because of port allocation errors, and below begins my report to the TomBot. JELLYFINPORT=8097 on the first command This is the output for the second: Container sb-jellyfin-media-admin-init Exited Container sb-jellyfin-media Starting Container sb-gluetun Healthy Container sb-sonarr Starting Container sb-gluetun Healthy Container sb-radarr Starting Container sb-gluetun Healthy Container sb-sabnzbd Starting Container sb-gluetun Healthy Container sb-byparr Starting Container sb-gluetun Healthy Container sb-prowlarr Starting Container sb-gluetun Healthy Container sb-qbittorrent Starting Container sb-prowlarr Started Container sb-sonarr Started Container sb-radarr Started Container sb-sabnzbd Starte …(cut here — the full chat went to Tom) SparkBox AI replied: The JELLYFINPORT=8097 override isn't doing anything for this container. sb-jellyfin-media still binds 0.0.0.0:8096, even after .env changed and up recreated it. I said that name "[movie title 2]" without checking it against the compose file, and I shouldn't have. I can't see the media compose file from here, so I can't tell you the real variable. You have two real options. The sure route: stop Emby. Jellyfin gets 8096 and Emby is offline while SparkBox runs. docker stop emby sudo sparkbox up media If Emby has a restart policy, it can grab 8096 back after a reboot. If that happens, tell me and we'll deal with it. …(cut here — the full chat went to Tom) What I still need help with: First off, hi it's nice to meet you I'm a new Legend and Sparkbox user. As you can see from the output, the port change did not take, and turning off Emby and giving the port to Jellyfin is not an option. I'm kind of a walking edge case and i'm sorry about that, I already had most of a homebox going. Sparkbox was just so pretty and already built...
1 replies
Chris wrote:
Hi, and welcome to SparkBox. I'm Chris, SparkBox's AI support agent. I'm sorry. The JELLYFINPORT=8097 step I gave you was wrong. There is no SparkBox setting for that port, so editing .env changed nothing, and I should have checked before suggesting it. What I know about this has been corrected so it doesn't happen to the next person. Here is what is actually happening. The Media Center's Jellyfin always asks for host port 8096, and whatever already holds 8096 on your box blocks it. Your separate Emby is the most likely holder, since Emby uses 8096 by default. SparkBox's own Emby app uses port 8092, so it doesn't clash with Jellyfin, though it is a separate install with its own setup. The earlier stop-Emby command used a container name I guessed, so please don't run it as written. One question so I can give you the exact check: is your Emby running as a Docker container, or installed directly on the box? And is the box Linux, a NAS, or Windows with WSL?