SOLVED: Upgrade killed server connection? :(

[TheDreadPirate]

WTF is going on with your network config? Jellyfin is only binding to localhost. Looks like a bunch of Tailscale IPs are in configs they shouldn't be in.

What are the contents of /etc/jellyfin/network.xml?

[ExistentialJazz]

/etc/jellyfin/network.xml

------

<?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>
  <CertificatePath />
  <CertificatePassword />
  <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>false</EnableRemoteAccess>
  <LocalNetworkSubnets>
    <string>100.109.49.40</string>
    <string>100.89.59.33</string>
    <string>100.70.79.66</string>
    <string>100.87.144.45</string>
    <string>100.111.96.31</string>
    <string>100.70.16.66</string>
  </LocalNetworkSubnets>
  <LocalNetworkAddresses />
  <KnownProxies />
  <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
  <VirtualInterfaceNames>
    <string>veth</string>
  </VirtualInterfaceNames>
  <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
  <PublishedServerUriBySubnet />
  <RemoteIPFilter />
  <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>

[TheDreadPirate]

Replace with the following then restart the jellyfin service.

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>
  <CertificatePath />
  <CertificatePassword />
  <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>false</EnableRemoteAccess>
  <LocalNetworkSubnets>
    <string>100.64.0.0/10</string>
    <string>192.168.0.0/24</string>
  <LocalNetworkAddresses>
  <KnownProxies />
  <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
  <VirtualInterfaceNames>
    <string>veth</string>
  </VirtualInterfaceNames>
  <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
  <PublishedServerUriBySubnet />
  <RemoteIPFilter />
  <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>

[ExistentialJazz]

That did it,

Thanks so much!

----

As you surmised I was connecting IPs directly through tailscale for my devices to have access outside of my home network - this was the only way I could figure out access that seemed safe with my novice network skills - what is the proper way to do this so that I don't screw up the XML file in the future? Thanks!

[TheDreadPirate]

The XML parameters I provided does that already. Remote connections are still disabled, but the Tailscale IP space is part of the "LAN subnets" config.

Code:

<string>100.64.0.0/10</string>

That allows Tailscale IPs so you don't have to add each individual IP. What you DIDN'T have before was your actual LAN IP address space.

Code:

<string>192.168.0.0/24</string>

And since you didn't allow remote connections your local IPs were considered remote since they were not present in the LAN subnets config.