Hi,

I have here a problem with a new Jellyfin setup.

Linuxserver and BBergie Docker do not start because there is already another Docker mapped to the  Port.

binhex Jellyfin does start, but I am unable to passthrough my iGPU and according to multiple Forum Posts it seems that the easiest Solution is to switch to the official Jellyfin Image.

 

 

Whenever I start Jellyfin I get the error:
 

[21:28:22] [INF] [1] Main: Kestrel is listening on 0.0.0.0
[21:28:22] [ERR] [1] Jellyfin.Networking.AutoDiscoveryHost: Unable to bind to 0.0.0.0:7359
System.Net.Sockets.SocketException (98): Address already in use
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at Jellyfin.Networking.AutoDiscoveryHost.ListenForAutoDiscoveryMessage(IPAddress listenAddress, CancellationToken cancellationToken)
[21:28:23] [WRN] [1] Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: The WebRootPath was not found: /wwwroot. Static files may be unavailable.
[21:28:23] [ERR] [1] Microsoft.Extensions.Hosting.Internal.Host: Hosting failed to start
System.IO.IOException: Failed to bind to address http://0.0.0.0:8096: address already in use.
.....
.......
.............
   at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable`1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List`1 exceptions, Func`3 operation)
[21:28:23] [ERR] [1] Main: Kestrel failed to start! This is most likely due to an invalid address or port bind - correct your bind configuration in network.xml and try again
[21:28:23] [FTL] [1] Main: Error while starting server
System.IO.IOException: Failed to bind to address http://0.0.0.0:8096: address already in use.

 

Due to this error I changed the IP and Ports of this Jellyfin, but it does not seem to be propagated to the system.

 

 

 

This is already the third or fourth install of this Container.

I set the settings when I installed the Container.

At the beginning it also wrongly opened Emby instead of the Jellyfin Address, but after a Server restart it was properly saved.

 

Can you please tell me why this happens?

The template is more or less broken because youre running in host mode.

Changed exposed ports in host network mode doesnt work. (you need to modify the container itself to work with it)

You need to swap the container ports ()

back to what theyre supposed to be and then change the network at least to bridge


Edit:

Regardless of Hostmode. In your appdata for the Jellyfin container you should find the network.xml

for the http and https port you can actually map the correct ports for host mode, the auto discovery via port 1900 sadly not

example to of the modified entries in the xml

  <InternalHttpPort>12901</InternalHttpPort>
  <InternalHttpsPort>12902</InternalHttpsPort>
  <PublicHttpPort>12901</PublicHttpPort>
  <PublicHttpsPort>12902</PublicHttpsPort>

 

Edited November 17, 20241 yr by Mainfrezzer

18 hours ago, Mainfrezzer said:

The template is more or less broken because youre running in host mode.
 

Thanks for your answer!

 

I tried to switch to Bridge, but it produces an error when I am building the image..

 

I just deleted all occurances of Jellyfin (there were entries from 2022...) and redownloaded it.

 

WhenI change to Bridge Mode and keep the Ports then I get the Error:

Quote

docker: Error response from daemon: driver failed programming external connectivity on endpoint Jellyfin (f321b85fe57eefc5c6d33a6d352523683705943fe602c285f35987d65a37610e): Error starting userland proxy: listen tcp4 0.0.0.0:8096: bind: address already in use.

The command failed.

 

There is no network.xml in any of the folders.

 

I stopped Emby and started Jellyfin. Now when I change the ports in Emby, I get the error with "failed to bind".

 

-> Why is it not possible to properly change the Docker Settings?

 

btw: I upgraded from 6.9 to 6.12.13 recently. 

Do I have to do an Docker update or something like that?

Edited November 18, 20241 yr by Torlew

25 minutes ago, Torlew said:

 

 

-> Why is it not possible to properly change the Docker Settings?

 

It is, as long as the template didnt get broken by choosing host mode, because it rewrites the port mappings.



its important that the container ports stay the default while you can change the textbox freely, in bridge mode.