• 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 SOLVED: Fedora won't connect to server after update

     
    • 0 Vote(s) - 0 Average

    SOLVED: Fedora won't connect to server after update

    It borked
    VladtheImpaler
    Offline

    Junior Member

    Posts: 15
    Threads: 4
    Joined: 2023 Dec
    Reputation: 0
    Country:United States
    #1
    2024-05-20, 02:10 PM
    Updated my Windows 10 Jellyfin server to 10.9.2 and Fedora and Windows clients to JMP 1.10.1.

    Windows client connects fine, but Fedora won't.  I tried from Firefox, version from the copr repo, and flatpak.  Everything worked fine before the update.

    Log shows..  ( The IP is correct it's not a typo )

    2024-05-20 09:53:19.877 [info] unknown @ 0 - JS: begin connectToServer
    2024-05-20 09:53:19.877 [info] unknown @ 0 - JS: tryReconnect: http://192.168.99.100:8096
    2024-05-20 09:53:19.977 [info] unknown @ 0 - JS: getTryConnectPromise http://192.168.99.100:8096
    2024-05-20 09:53:19.977 [info] unknown @ 0 - JS: ConnectionManager requesting url: http://192.168.99.100:8096/system/info/public
    2024-05-20 09:53:19.977 [info] unknown @ 0 - JS: fetchWithTimeout: timeoutMs: 20000, url: http://192.168.99.100:8096/system/info/public
    2024-05-20 09:53:19.979 [info] unknown @ 0 - JS: fetchWithTimeout: succeeded connecting to url: http://192.168.99.100:8096/system/info/public
    2024-05-20 09:53:19.979 [info] unknown @ 0 - JS: ConnectionManager response status: 503, url: http://192.168.99.100:8096/system/info/public
    2024-05-20 09:53:19.979 [info] unknown @ 0 - JS: Reconnect failed to http://192.168.99.100:8096
    2024-05-20 09:53:19.979 [info] unknown @ 0 - JS: connectToAddress http://192.168.99.100:8096 failed

    Flatpak terminal output....

    [2:82:0520/095301.721060:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -107
    [2:82:0520/095301.721759:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -107
    [2:82:0520/095311.472547:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -107
    [2:82:0520/095311.473220:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -107
    [2:82:0520/095317.302439:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -107
    [2:82:0520/095317.303196:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -107
    [2:82:0520/095319.875982:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -107
    [2:82:0520/095319.876596:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -107
    2024-05-20 09:53:28.933 [info] unknown @ 0 - SDL is closing.


    I tried to add a firewall entry to open ports 8096 tcp, 1900 udp and 7359 udp but it didn't help.. (not using the https port)
    Go to solution
    Fate
    Offline

    Member

    Posts: 220
    Threads: 3
    Joined: 2023 Jun
    Reputation: 16
    #2
    2024-05-20, 03:12 PM
    Can you try deleting the server from the client and then readd it?
    VladtheImpaler
    Offline

    Junior Member

    Posts: 15
    Threads: 4
    Joined: 2023 Dec
    Reputation: 0
    Country:United States
    #3
    2024-05-20, 04:03 PM
    Doesn't help..  Says Connection Failure: "We're unable to connect to the selected server right now. Please ensure it is running and try again."
    VladtheImpaler
    Offline

    Junior Member

    Posts: 15
    Threads: 4
    Joined: 2023 Dec
    Reputation: 0
    Country:United States
    #4
    2024-05-20, 04:29 PM
    Fixed it... I guess Jelly isn't properly detecting the machine IP.

    I manually set "Bind to local network address" to the machines IP and now I can connect via IP and DNS.
    « 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