• 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 Networking & Access LAN DIscovery can't find server

     
    • 0 Vote(s) - 0 Average

    LAN DIscovery can't find server

    UnderEu
    Offline

    Junior Member

    Posts: 5
    Threads: 2
    Joined: 2026 Jul
    Reputation: 0
    Country:Brazil
    #1
    2026-07-10, 01:05 PM
    Hi.

    I have my own local server for a while and experience has been great, however I can't make client apps on my local network find my local server via LAN Discovery feature.
    Server-side configuration is done, both the app and firewall; all clients are setup to connect manually, which is not a massive deal but it gets annoying to setup a "smart TV" by using the D-Pad to type, that's why I was trying to put LAN Discovery to work in the 1st place.

    All apps hosted on my LAN are IPv6-only and I presume the server app is not doing its discovery magic via this protocol.


    Application version: 0.19.9 Release

    Where did you install the app from? Amazon Appstore

    Device information: Amazon Fire TV Cube (3rd Generation)

    Android version: Fire OS 7.7.1.4 (PS7714/5507)

    Jellyfin server version: 10.11.11
    TheDreadPirate
    Online

    Community Moderator

    Posts: 15,880
    Threads: 11
    Joined: 2023 Jun
    Reputation: 478
    Country:United States
    #2
    2026-07-10, 02:00 PM (This post was last modified: 2026-07-10, 02:07 PM by TheDreadPirate. Edited 2 times in total.)
    Jellyfin's service discovery is a "broadcast" on port 7359. The problem is that IPv6 does not support broadcasting and, therefore, service discovery does not work in an IPv6 only environment. Broadcasting, explicitly, only uses IPv4.
    Jellyfin 10.11.11 (Docker)
    Debian 13 w/Xanmod amd64v3 LTS kernel
    AMD Ryzen 5500 w/32GB DDR4
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    ZFS Storage pool
        vdev1 - 6x WD Red Pro 6TB CMR in RAIDZ1
        vdev2 - 3x WD Red Pro 18TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    UnderEu
    Offline

    Junior Member

    Posts: 5
    Threads: 2
    Joined: 2026 Jul
    Reputation: 0
    Country:Brazil
    #3
    2026-07-10, 05:27 PM
    (2026-07-10, 02:00 PM)TheDreadPirate Wrote: Jellyfin's service discovery is a "broadcast" on port 7359.  The problem is that IPv6 does not support broadcasting and, therefore, service discovery does not work in an IPv6 only environment.  Broadcasting, explicitly, only uses IPv4.

    OK, makes sense.

    Tks. for clarification.
    jrgrant
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2026 Aug
    Reputation: 0
    Country:United States
    #4
    2026-08-03, 11:49 PM
    (2026-07-10, 02:00 PM)TheDreadPirate Wrote: Jellyfin's service discovery is a "broadcast" on port 7359.  The problem is that IPv6 does not support broadcasting and, therefore, service discovery does not work in an IPv6 only environment.  Broadcasting, explicitly, only uses IPv4.

    Right, IPv6 has no "broadcast" address per se, but the functionality of the "all one's after the netmask" broadcast from IPv4 is replaced with a link local all nodes multicast address. That address is FE02::1
    Seems like this might be a significant enhancement to the discovery algorithm. I know it's dangerous to suggest an enhancement without volunteering to provide the solution, but I'm not equipped Smiling-face
    TheDreadPirate
    Online

    Community Moderator

    Posts: 15,880
    Threads: 11
    Joined: 2023 Jun
    Reputation: 478
    Country:United States
    #5
    2026-08-04, 12:53 AM
    When I say it is IPv4 only, I am not mincing words. Jellyfin only "broadcasts", which is an IPv4 only function. It just will not work in any way, shape, or form with IPv6.

    And there are currently no plans to implement a multicast equivalent, which would work in IPv6.
    Jellyfin 10.11.11 (Docker)
    Debian 13 w/Xanmod amd64v3 LTS kernel
    AMD Ryzen 5500 w/32GB DDR4
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    ZFS Storage pool
        vdev1 - 6x WD Red Pro 6TB CMR in RAIDZ1
        vdev2 - 3x WD Red Pro 18TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • 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