mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Server has already started issue #6791
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @iamironz on GitHub (Mar 3, 2025).
Description of the bug
The container spontaneously enters a boot loop, with logs showing "Server has already started" error due to a duplicate instance binding to port 8096, despite no changes in the container’s configuration or network.xml.
Reproduction steps
What is the current bug behavior?
The container initiates multiple instances where one instance attempts to bind to port 8096 while another is already running, causing the error:
What is the expected correct behavior?
The container should start once, bind to port 8096, and not attempt a duplicate startup.
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.10.6
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
Docker engine info:
network.xml file content:
@felix920506 commented on GitHub (Mar 3, 2025):
You are not using the official image. The official image is
jellyfin/jellyfin:latest. You should report this issue to https://www.linuxserver.io@iamironz commented on GitHub (Mar 3, 2025):
The same issue reproduces on official one @felix920506 , please re-open.
@felix920506 commented on GitHub (Mar 3, 2025):
This is most likely an issue with your specific instance or environment. If the container won't even start you won't be the first one to report it given how long 10.10.6 has been out. Please head to our forum or chat rooms for troubleshooting. https://jellyfin.org/contact
@bkromrey commented on GitHub (Mar 4, 2025):
@iamironz I ran into the exact same error today. Disabling the ListenBrainz plugin allowed my instance to function normally once more.
@hartman8227 commented on GitHub (Mar 5, 2025):
My instance went down with this as well this morning. My docker compose has
jellyfin/jellyfinas the docker image. I was also running the ListenBrainz Plugin v5.1.1.3. The error in my logs were almost verbatem the same as @iamironz .Following @bkromrey suggestion. I tarballed all of the plugins in
config/pluginsas backup and the deleted all of the directories for versions of ListenBrainz starting with 5, leaving me on version 4.0.0.2 Then restarted the container.Container started normally and Jellyfin came online. ListenBrainz autoupdated to v5.1.2.1. I restarted the container again and the issue did not repeat.
Edit: Looking further I found a bug report on the ListenBrainz plugins repo: https://github.com/lyarenei/jellyfin-plugin-listenbrainz/issues/121#issuecomment-2692645545
Simply deleting the directory
ListenBrainz_5.1.1.3should be sufficient.