• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0

     
    • 0 Vote(s) - 0 Average

    Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0

    Jellyfin is inaccessible after upgrade from Jellyfin.Server 10.8.13.0 to 10.9.11.0
    Riesling
    Offline

    Junior Member

    Posts: 19
    Threads: 1
    Joined: 2024 Jun
    Reputation: 0
    #7
    2024-10-09, 05:41 PM (This post was last modified: 2024-10-09, 06:32 PM by TheDreadPirate. Edited 6 times in total.)
    Yes, Pirate, network is o.k.:

    Code:
    root@jellyfin:/# ping google.com
    PING google.com(fra24s02-in-x0e.1e100.net (2a00:1450:4001:803::200e)) 56 data bytes
    64 bytes from fra24s02-in-x0e.1e100.net (2a00:1450:4001:803::200e): icmp_seq=1 ttl=57 time=21.8 ms
    64 bytes from fra24s02-in-x0e.1e100.net (2a00:1450:4001:803::200e): icmp_seq=2 ttl=57 time=9.95 ms
    64 bytes from fra24s02-in-x0e.1e100.net (2a00:1450:4001:803::200e): icmp_seq=3 ttl=57 time=11.6 ms
    64 bytes from fra24s02-in-x0e.1e100.net (2a00:1450:4001:803::200e): icmp_seq=4 ttl=57 time=12.4 ms
    ^C
    --- google.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3002ms
    rtt min/avg/max/mdev = 9.950/13.924/21.803/4.632 ms

    The network.xml seems to have been generated by the server?

    Code:
    root@jellyfin:/# cat /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>true</EnableIPv6>
      <EnableRemoteAccess>false</EnableRemoteAccess>
      <LocalNetworkSubnets />
      <LocalNetworkAddresses />
      <KnownProxies />
      <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
      <VirtualInterfaceNames>
        <string>veth</string>
      </VirtualInterfaceNames>
      <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest>
      <PublishedServerUriBySubnet />
      <RemoteIPFilter />
      <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
    </NetworkConfiguration>

    could it be the name of the interface?

    Code:
    root@jellyfin:/# ifconfig
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 10.3.3.3  netmask 255.255.255.0  broadcast 10.3.3.255
            inet6 2a02:[public IPv6 address]  prefixlen 64  scopeid 0x0<global>
            inet6 fe80::87b:60ff:fe3a:74e8  prefixlen 64  scopeid 0x20<link>
            ether 0a:7b:60:3a:74:e8  txqueuelen 1000  (Ethernet)
            RX packets 290536  bytes 43602281 (41.5 MiB)
            RX errors 0  dropped 91317  overruns 0  frame 0
            TX packets 4355  bytes 6326000 (6.0 MiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 1000  (Local Loopback)
            RX packets 16  bytes 3091 (3.0 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 16  bytes 3091 (3.0 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    ...apparently not - if I change

     
      <VirtualInterfaceNames>
        <string>veth</string>
      </VirtualInterfaceNames>


    to the name of the interface:

      <VirtualInterfaceNames>
        <string>eth0</string>
      </VirtualInterfaceNames>

    I cannot connect via http at all...

    ~R.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    Messages In This Thread
    Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-09, 10:03 AM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-09, 01:20 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-09, 01:28 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-09, 02:01 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-09, 04:22 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-09, 05:00 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-09, 05:41 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-09, 05:55 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-09, 06:19 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-09, 06:37 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-09, 07:05 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-09, 07:17 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-09, 07:31 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-09, 07:53 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-10, 07:20 AM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-10, 11:58 AM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-11, 08:06 AM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-14, 05:37 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-14, 05:41 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-14, 05:59 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-14, 06:16 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-14, 06:46 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-14, 07:15 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-14, 07:25 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by TheDreadPirate - 2024-10-14, 07:56 PM
    RE: Inaccessible after upgrade from 10.8.13.0 to 10.9.11.0 - by Riesling - 2024-10-15, 08:14 AM

    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode