Jellyfin Forum
Jellyfin Server not binding to LAN address - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: Jellyfin Server not binding to LAN address (/t-jellyfin-server-not-binding-to-lan-address)

Pages: 1 2

Jellyfin Server not binding to LAN address - penis - 2024-05-14

I installed jellyfin a week ago, running on debian. Everything worked fine until i dist-upgraded my system (including jellyfin)
Now, jellyfin is no longer works directly after booting. It only works if I run
Code:
sudo systemctl restart jellyfin

I checked the logs and found this. It only binds to 127.0.0.1 for some reason.

Code:
[09:01:22] [INF] Defined LAN addresses: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
[09:01:22] [INF] Defined LAN exclusions: []
[09:01:22] [INF] Using LAN addresses: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
[09:01:22] [INF] Using bind addresses: ["127.0.0.1"]


Later in the logs, this happens:

Code:
jellyfin[484]: [09:01:34] [ERR] An error occurred while accessing the plugin manifest: https://repo.jellyfin.org/files/plugin/manifest.json
jellyfin[484]: System.Net.Http.HttpRequestException: Resource temporarily unavailable (repo.jellyfin.org:443)
jellyfin[484]:  ---> System.Net.Sockets.SocketException (11): Resource temporarily unavailable
jellyfin[484]:    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
jellyfin[484]:    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
jellyfin[484]:    at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken canc>
jellyfin[484]:    at Jellyfin.Networking.HappyEyeballs.HttpClientExtension.AttemptConnection(AddressFamily addressFamily, SocketsHttpConnectionContext context, CancellationToken canc>
jellyfin[484]:    at Jellyfin.Networking.HappyEyeballs.HttpClientExtension.OnConnect(SocketsHttpConnectionContext context, CancellationToken cancellationToken)
jellyfin[484]:    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellatio>
jellyfin[484]:    --- End of inner exception stack trace ---
jellyfin[484]:    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellatio>
jellyfin[484]:    at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
jellyfin[484]:    at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
jellyfin[484]:    at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem)
jellyfin[484]:    at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
jellyfin[484]:    at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken canc>
jellyfin[484]:    at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
jellyfin[484]:    at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
jellyfin[484]:    at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellati>
jellyfin[484]:    at Microsoft.Extensions.Http.Logging.LoggingScopeHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cance>
jellyfin[484]:    at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean dispos>
jellyfin[484]:    at System.Net.Http.Json.HttpClientJsonExtensions.<FromJsonAsyncCore>g__Core|12_0[TValue,TJsonOptions](HttpClient client, Task`1 responseTask, Boolean usingResponseH>
 

So it seems like the jellyfin service is trying to start before the system even got to connect to LAN. After restarting the service with systemctl, the logs show a successful bind to the network IP
Code:
jellyfin[933]: [09:11:44] [INF] Defined LAN addresses: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
jellyfin[933]: [09:11:44] [INF] Defined LAN exclusions: []
jellyfin[933]: [09:11:44] [INF] Using LAN addresses: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
jellyfin[933]: [09:11:44] [INF] Using bind addresses: ["127.0.0.1", "192.168.0.177"]

How can I fix this?

RE: Jellyfin Server not binding to LAN address - TheDreadPirate - 2024-05-14

Is your Jellyfin installed in a VM? If so, I'm wondering if it is ignoring the virtual NICs.

Can you share your full log via pastebin?

RE: Jellyfin Server not binding to LAN address - penis - 2024-05-14

(2024-05-14, 01:35 PM)TheDreadPirate Wrote: Is your Jellyfin installed in a VM?  If so, I'm wondering if it is ignoring the virtual NICs.

Can you share your full log via pastebin?

No VM or anything, hardware would be way too weak 
Here's the log: https://pastebin.com/U6bByDDh
First start is automatically after boot, second start is me manually restarting it via systemctl

RE: Jellyfin Server not binding to LAN address - TheDreadPirate - 2024-05-14

Did you specify a bind address in Dashboard > Networking?

Can you share the contents of /etc/jellyfin/network.xml?

RE: Jellyfin Server not binding to LAN address - penis - 2024-05-14

(2024-05-14, 02:45 PM)TheDreadPirate Wrote: Did you specify a bind address in Dashboard > Networking?

Can you share the contents of /etc/jellyfin/network.xml?

Only for testing purposes, reverted this change already. Contents of the file should be back to the defaults (which worked before upgrading) 
Here's the network.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <BaseUrl />
  <EnableHttps>false</EnableHttps>
  <RequireHttps>false</RequireHttps>
  <InternalHttpPort>8096</InternalHttpPort>
  <InternalHttpsPort>8920</InternalHttpsPort>
  <PublicHttpPort>8096</PublicHttpPort>
  <PublicHttpsPort>8920</PublicHttpsPort>
  <AutoDiscovery>true</AutoDiscovery>
  <EnableUPnP>false</EnableUPnP>
  <EnableIPv4>true</EnableIPv4>
  <EnableIPv6>false</EnableIPv6>
  <EnableRemoteAccess>true</EnableRemoteAccess>
  <LocalNetworkSubnets />
  <LocalNetworkAddresses/>
  <KnownProxies />
  <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
  <VirtualInterfaceNames>
    <string>veth</string>
  </VirtualInterfaceNames>
  <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
  <PublishedServerUriBySubnet />
  <RemoteIPFilter />
  <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
</NetworkConfiguration>
I feel like this could be a problem with the systemd service.
It does contain the following line but doesn't appear to have an effect
Code:
After = network-online.target


RE: Jellyfin Server not binding to LAN address - TheDreadPirate - 2024-05-14

Can you stop jellyfin, delete network.xml, and start jellyfin? It will regenerate the file with defaults. A couple other people weird network issues and deleting this file helped them.

RE: Jellyfin Server not binding to LAN address - penis - 2024-05-14

(2024-05-14, 04:29 PM)TheDreadPirate Wrote: Can you stop jellyfin, delete network.xml, and start jellyfin?  It will regenerate the file with defaults.  A couple other people weird network issues and deleting this file helped them.

Nothing changed unfortunately, im calling that it's a debian issue

Update: it was a debian issue

had to replace this line
Code:
allow-hotplug enp4s0
with
Code:
auto enp4s0


this makes me honestly doubt the good reputation about debians stability, if an update breaks your networking randomly

RE: Jellyfin Server not binding to LAN address - Novus - 2024-05-15

I think that I have the same issue but with Windows. Local Host is working but no other computers in the network can´t connect. Chrome says "ERR_CONNECTION_TIMED_OUT"
I deleted the network.xml but the problem is still there.

Windows 11 with Jellyfin localy installed the Host has HyperV running and the main "Networkcard" is a HyperV Virtual Networkcard.
Everthing ran fine with 10.8.13 until yesterday when I upgraded to 10.9.1

Any tips?

Code:
[2024-05-15 09:16:39.384 +02:00] [INF] [15] Emby.Server.Implementations.ScheduledTasks.TaskManager: "Aktualisiere Plugins" Completed after 0 minute(s) and 3 seconds
[2024-05-15 09:18:30.176 +02:00] [INF] [6] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "127.0.0.1" request
[2024-05-15 09:18:34.109 +02:00] [INF] [15] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "127.0.0.1" closed
[2024-05-15 09:20:25.895 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
[2024-05-15 09:20:25.899 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions: []
[2024-05-15 09:20:25.902 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
[2024-05-15 09:20:25.906 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Using bind addresses: []
[2024-05-15 09:20:25.914 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Remote IP filter is "Allowlist"
[2024-05-15 09:20:25.916 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Filter list: []
[2024-05-15 09:20:28.969 +02:00] [WRN] [9] Jellyfin.Networking.Manager.NetworkManager: "127.0.0.1": Only loopback "127.0.0.1" returned, using that as bind address.
[2024-05-15 09:20:32.196 +02:00] [INF] [22] Emby.Server.Implementations.Session.SessionManager: Sending shutdown notifications
[2024-05-15 09:20:32.208 +02:00] [INF] [9] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "127.0.0.1" closed
[2024-05-15 09:20:32.225 +02:00] [INF] [17] Jellyfin.Networking.PortForwardingHost: Stopping NAT discovery

Code:
<?xml version="1.0" encoding="utf-8"?>
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <BaseUrl />
  <EnableHttps>false</EnableHttps>
  <RequireHttps>false</RequireHttps>
  <InternalHttpPort>8096</InternalHttpPort>
  <InternalHttpsPort>8920</InternalHttpsPort>
  <PublicHttpPort>8096</PublicHttpPort>
  <PublicHttpsPort>8920</PublicHttpsPort>
  <AutoDiscovery>true</AutoDiscovery>
  <EnableUPnP>false</EnableUPnP>
  <EnableIPv4>true</EnableIPv4>
  <EnableIPv6>false</EnableIPv6>
  <EnableRemoteAccess>true</EnableRemoteAccess>
  <LocalNetworkSubnets />
  <LocalNetworkAddresses />
  <KnownProxies />
  <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
  <VirtualInterfaceNames>
    <string>veth</string>
  </VirtualInterfaceNames>
  <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
  <PublishedServerUriBySubnet />
  <RemoteIPFilter />
  <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
</NetworkConfiguration>


RE: Jellyfin Server not binding to LAN address - honneamise - 2024-05-15

Howdy all, I am having this issue with jellyfin not starting because port 8096 is in use, but there is nothing showing as using that port. I am running Ubuntu 22.04, kept up to date, jellyfin installed via apt, nginx in front as a reverse proxy, with Lets Encrypt certs. It has been running perfectly for about 18-20 months, and yesterday while watching a video, the system updated and now it will not start:

[2024-05-15 20:33:27.203 +10:00] [ERR] 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 20:33:27.203 +10:00] [FTL] Error while starting server
System.IO.IOException: Failed to bind to address http://127.0.0.1:8096: address already in use.

Is there something that has changed in the jellyfin update that has caused this issue to crop up?
(2024-05-15, 11:10 AM)honneamise Wrote: Howdy all, I am having this issue with jellyfin not starting because port 8096 is in use, but there is nothing showing as using that port.  I am running Ubuntu 22.04, kept up to date, jellyfin installed via apt, nginx in front as a reverse proxy, with Lets Encrypt certs.  It has been running perfectly for about 18-20 months, and yesterday while watching a video, the system updated and now it will not start:

[2024-05-15 20:33:27.203 +10:00] [ERR] 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 20:33:27.203 +10:00] [FTL] Error while starting server
System.IO.IOException: Failed to bind to address http://127.0.0.1:8096: address already in use.

Is there something that has changed in the jellyfin update that has caused this issue to crop up?

Quick update, I have tried deleting the network.xml as per some other posts, but the file did not regenerate automatically, so i restored the file.  I have also made changes to the actual port number in the jellyfin and nginx configs, but no go, same result as above.

RE: Jellyfin Server not binding to LAN address - TheDreadPirate - 2024-05-15

(2024-05-15, 07:39 AM)Novus Wrote: I think that I have the same issue but with Windows. Local Host is working but no other computers in the network can´t connect. Chrome says "ERR_CONNECTION_TIMED_OUT"
I deleted the network.xml but the problem is still there.

Windows 11 with Jellyfin localy installed the Host has HyperV running and the main "Networkcard" is a HyperV Virtual Networkcard.
Everthing ran fine with 10.8.13 until yesterday when I upgraded to 10.9.1

Any tips?

Code:
[2024-05-15 09:16:39.384 +02:00] [INF] [15] Emby.Server.Implementations.ScheduledTasks.TaskManager: "Aktualisiere Plugins" Completed after 0 minute(s) and 3 seconds
[2024-05-15 09:18:30.176 +02:00] [INF] [6] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "127.0.0.1" request
[2024-05-15 09:18:34.109 +02:00] [INF] [15] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "127.0.0.1" closed
[2024-05-15 09:20:25.895 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Defined LAN addresses: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
[2024-05-15 09:20:25.899 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions: []
[2024-05-15 09:20:25.902 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Using LAN addresses: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
[2024-05-15 09:20:25.906 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Using bind addresses: []
[2024-05-15 09:20:25.914 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Remote IP filter is "Allowlist"
[2024-05-15 09:20:25.916 +02:00] [INF] [9] Jellyfin.Networking.Manager.NetworkManager: Filter list: []
[2024-05-15 09:20:28.969 +02:00] [WRN] [9] Jellyfin.Networking.Manager.NetworkManager: "127.0.0.1": Only loopback "127.0.0.1" returned, using that as bind address.
[2024-05-15 09:20:32.196 +02:00] [INF] [22] Emby.Server.Implementations.Session.SessionManager: Sending shutdown notifications
[2024-05-15 09:20:32.208 +02:00] [INF] [9] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "127.0.0.1" closed
[2024-05-15 09:20:32.225 +02:00] [INF] [17] Jellyfin.Networking.PortForwardingHost: Stopping NAT discovery

Code:
<?xml version="1.0" encoding="utf-8"?>
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <BaseUrl />
  <EnableHttps>false</EnableHttps>
  <RequireHttps>false</RequireHttps>
  <InternalHttpPort>8096</InternalHttpPort>
  <InternalHttpsPort>8920</InternalHttpsPort>
  <PublicHttpPort>8096</PublicHttpPort>
  <PublicHttpsPort>8920</PublicHttpsPort>
  <AutoDiscovery>true</AutoDiscovery>
  <EnableUPnP>false</EnableUPnP>
  <EnableIPv4>true</EnableIPv4>
  <EnableIPv6>false</EnableIPv6>
  <EnableRemoteAccess>true</EnableRemoteAccess>
  <LocalNetworkSubnets />
  <LocalNetworkAddresses />
  <KnownProxies />
  <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
  <VirtualInterfaceNames>
    <string>veth</string>
  </VirtualInterfaceNames>
  <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
  <PublishedServerUriBySubnet />
  <RemoteIPFilter />
  <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
</NetworkConfiguration>

Double check that the name of the HyperV NIC doesn't start with "veth" since Jellyfin ignores those by default.  Also double check that when you upgraded that the Windows Firewall rule is still there.