You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the last update happened this night the Jellyfin app is stuck at deploying. Logs says that the binding address/port is already in use, but at least the host is not using that port (verified with netstat -tulpn | grep LISTEN )...Can't get a working shell into the container, so can't really check if the process using that port is running or not.
Container log:
...
2024-05-15 11:00:54.842970+02:00[09:00:54] [ERR] [1] Microsoft.Extensions.Hosting.Internal.Host: Hosting failed to start
2024-05-15 11:00:54.843009+02:00System.IO.IOException: Failed to bind to address http://192.168.1.35:8096: address already in use.
2024-05-15 11:00:54.843073+02:00---> Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use
2024-05-15 11:00:54.843092+02:00---> System.Net.Sockets.SocketException (98): Address already in use
2024-05-15 11:00:54.843099+02:00at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
2024-05-15 11:00:54.843105+02:00at System.Net.Sockets.Socket.Bind(EndPoint localEP)
2024-05-15 11:00:54.843112+02:00at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportOptions.CreateDefaultBoundListenSocket(EndPoint endpoint)
2024-05-15 11:00:54.843147+02:00at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
...
2024-05-15 11:00:54.843303+02:00[09:00:54] [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
2024-05-15 11:00:54.843309+02:00[09:00:54] [FTL] [1] Main: Error while starting server
2024-05-15 11:00:54.843319+02:00System.IO.IOException: Failed to bind to address http://192.168.1.35:8096: address already in use.
...
Output of midclt call chart.release.get_instance jellyfin | jq '.config':
Yes works with disabled hostnet, at least it's a temp. workaround for now. Let's see when a update of upstream Jellyfin is made available. Thanks for the help!
Since the last update happened this night the Jellyfin app is stuck at deploying. Logs says that the binding address/port is already in use, but at least the host is not using that port (verified with
netstat -tulpn | grep LISTEN
)...Can't get a working shell into the container, so can't really check if the process using that port is running or not.Container log:
Output of
midclt call chart.release.get_instance jellyfin | jq '.config'
:And the network.xml of Jellyfin looks like this (nothing changed here):
The text was updated successfully, but these errors were encountered: