• 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 CLOSED — Yet Another Connection Problem

     
    • 0 Vote(s) - 0 Average

    CLOSED — Yet Another Connection Problem

    b-riched
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2025 May
    Reputation: 0
    Country:Germany
    #1
    2025-05-07, 06:47 PM (This post was last modified: 5 hours ago by b-riched. Edited 12 times in total.)
    Hi there, 

    Yes, me too, i.e. Clients won‘t Connect to Jellyfin Server. 
    Web-Clients do connect, but Client Apps do not. 

    [edit]
    Specifically
      IOS Safari or Win11 Edge browser will connect via 192.x.z.149:8096 with defined users 
    But… 
      Tried iOS Jellyfin Mobile App which tells me ‘unable to connect’
      Trier iOS SwiftFin App which tells me that either there is no Internet Connection (external) or
          cannot detect any local server in the first place.
      Tried iTV Box JF client which will find the server at 192.x.z.149 but does not connect (no error message displayed)

    [edit]
    Ideas so far (with no success)
      - 0.0.0.0 Trick, incl. Trying to connect to one of the listed addresses the JF server is listening (e.g. 172.17.01.1:<ports>)
      - switching IPv6 off/on
      - naming different IP addresses
      - allowing external JF server access
      - updating JF apps
      - broadcasting to 192..x.y.255 and to 0.0.0.0
      - adding one of the 4 ports to the address (192.x.y.149:7359, etc.)
      - adding the /jellyfin suffix (and combinations to the above)
      - trying other IP addresses such as 192.x.y.3 will be detected by iTV JF App but will cot connect.
      - adding protocol prefix to the address, i.e. ‘http://192.x.y.149:7359’ or ‘…:8096’ will not help and IMHO should not,
        as the client app does not open a http connection.
          I believe that the corresponding ‘http bug’ has already been fixed anyway.


    Any other further idea? 
    Many thanks in advance

    LAN:
      AVM 6690 cable Router
      IPv4 / IPv6
      No Open Ports
      Net: 192.x.y.1 / 255.255.255.0 (no further Subnets)

    Homeserver:
      OS: UnRaid 7 
      UnRaid Server: 192.x.y.149 (Static IP defined by Router)
      AdGuard Running on 192.x.y.2 (Static IP defined by Router) 
     Jellyfin docker V. 10.10.7 up and running fine, users defined, PWs set 

    Jellyfin Installation:
      JELLYFIN_PublishedServerUrl: 192.x.y.149 for both, container and LAN IP
      Ports (default): 8096 / 8920 / 7359 / 1900
      HTTPS: disabled / Not forced 
      Remote Access: disabled
      IPv4, IPv6 enabled
      JF Server Not Published (outside local NW)

    [edit]
    JF Log File:
      - does show successful connections to web-clients.
      - does NOT show any unsuccessful connections attempts issued by the JF apps
      - does show that networking manager filters for 192.x.y.149 (which is what I would expect it to do)
    b-riched
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2025 May
    Reputation: 0
    Country:Germany
    #2
    5 hours ago
    UPDATE

    After reading through some more of the older cases in this channel I got inspired to de- and reinstall the SwiftFin App on my iTV Box.
    After that the app did connect to the JF server via “http://192.x.y.149:8096”.
    Important seems to be that one leaves the automatically detected server aside and types in the address manually at the first connection attempt. So it is a matter of “not doing the obvious” combined with “doing it right the first time”. Strange!

    Why the app does connect via http and port 8096 instead of 7359 still is a miracle to me but it works now.
    Why the app can only handle movies and tv-shows and cannot cope with other media type such as music, pictures, ebooks, audio books which are not even displayed (let alone played) is another miracle. But that is not subject to this channel anymore…

    Remaining issue is the iOS apps not working. But anticipating their functionality being at the same (disappointing) level I will gladly stay with the browser-based approach which at the first glance is working fine.

    Given this approach I declare the case closed but only partially resolved.
    « 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