• 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 Can't connect to Jellyfin 10.9.2 with Jellyfin at f-droid

    Pages (2): 1 2 Next »

     
    • 0 Vote(s) - 0 Average

    Can't connect to Jellyfin 10.9.2 with Jellyfin at f-droid

    Others having this issue?
    34626
    Offline

    Member

    Posts: 172
    Threads: 36
    Joined: 2023 Jul
    Reputation: 0
    Country:Denmark
    #1
    2024-05-20, 09:15 AM
    I've recently started using a HTPC rather then Chromecast, why i also started to use Jellyfin from F-droid rather then Google Play, since i dont need the Chromecast function.

    But for some reason, i am not able to connect to my Jellyfin server running 10.9.2, my best guesss is that the f-droid release is out of date, its from december 2023.

    Can someone verify this or maby help me figure this out? Jellyfin just says its not able to connect to the server, i dont get an error that my client is out of date?
    Serv: N5105 - 32GB RAM, 1 WD Red SA500 2TB, 2 8TB, 2 4TB WD Red Plus, LC-35U3-C-HUB
    OS: Debian
    Clients: Pi4 with LibreELEC + JellyCon and Jellyfin Media Player
    Network: 2 TP-Link AX23, OpenWRT mesh 802.11s and 1 Gbit
    jellyfinvm
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 May
    Reputation: 0
    #2
    2024-05-20, 09:56 AM
    F-droid has the latest version (2.6.1) same as google play (from 2024).
    https://f-droid.org/packages/org.jellyfin.mobile/

    also, try clearing the jellyfin app cache and data and then connect.
    rfelix
    Offline

    Junior Member

    Posts: 8
    Threads: 4
    Joined: 2024 May
    Reputation: 0
    Country:Brazil
    #3
    2024-05-20, 11:24 AM
    I have the same problem here, I can't log in to any device it says "cannot connect to the server"
    34626
    Offline

    Member

    Posts: 172
    Threads: 36
    Joined: 2023 Jul
    Reputation: 0
    Country:Denmark
    #4
    2024-05-20, 12:02 PM
    I have tried to uninstall and install it from two Android devices, and tried to clear their cache + upgraded caddy + stopped and started my docker (official docker image) but it still has the connection issue.
    Serv: N5105 - 32GB RAM, 1 WD Red SA500 2TB, 2 8TB, 2 4TB WD Red Plus, LC-35U3-C-HUB
    OS: Debian
    Clients: Pi4 with LibreELEC + JellyCon and Jellyfin Media Player
    Network: 2 TP-Link AX23, OpenWRT mesh 802.11s and 1 Gbit
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #5
    2024-05-20, 12:43 PM
    In your caddy logs do you see the connection attempts?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    rfelix
    Offline

    Junior Member

    Posts: 8
    Threads: 4
    Joined: 2024 May
    Reputation: 0
    Country:Brazil
    #6
    2024-05-20, 04:52 PM
    how many people can simultaneously watch on jellyfin at the same time?
    34626
    Offline

    Member

    Posts: 172
    Threads: 36
    Joined: 2023 Jul
    Reputation: 0
    Country:Denmark
    #7
    2024-05-22, 07:09 PM
    (2024-05-20, 12:43 PM)TheDreadPirate Wrote: In your caddy logs do you see the connection attempts?

    Caddy dosent make logs (As far as i know). But i removed Jellyfin and reinstalled, but it already had the host information, so i clear storage data of Jellyfin and then it was cleared, i uninstalled Jellyfin, restarted and installed Jellyfin.
    But now, it will crash instantly when i click connect.

    I have done the same procedure on my smartphone, but here it worked and i do now have access, but on the Lenovo tab p11 2nd edition it fails - i havent tried with jellyfin from google play, but that was what i used earlier, but now i only try the f-droid version.
    Serv: N5105 - 32GB RAM, 1 WD Red SA500 2TB, 2 8TB, 2 4TB WD Red Plus, LC-35U3-C-HUB
    OS: Debian
    Clients: Pi4 with LibreELEC + JellyCon and Jellyfin Media Player
    Network: 2 TP-Link AX23, OpenWRT mesh 802.11s and 1 Gbit
    34626
    Offline

    Member

    Posts: 172
    Threads: 36
    Joined: 2023 Jul
    Reputation: 0
    Country:Denmark
    #8
    2024-05-22, 07:20 PM
    I uninstalled Jellyfin from f-droid and installed from google play and it worked like a charm. I then removed Jellyfin and tried to install from f-droid and now again it knew the host information - I did remove the used storage and cache from Jellyfin, but the one from f-droid for my tablet seems to have a bug on it.. This makes no sense..
    Serv: N5105 - 32GB RAM, 1 WD Red SA500 2TB, 2 8TB, 2 4TB WD Red Plus, LC-35U3-C-HUB
    OS: Debian
    Clients: Pi4 with LibreELEC + JellyCon and Jellyfin Media Player
    Network: 2 TP-Link AX23, OpenWRT mesh 802.11s and 1 Gbit
    34626
    Offline

    Member

    Posts: 172
    Threads: 36
    Joined: 2023 Jul
    Reputation: 0
    Country:Denmark
    #9
    2024-05-25, 12:45 PM
    Now my Android smartphone wont connect, i get this error in the logs:

    [2024-05-25 11:13:44.103 +00:00] [INF] [88] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:17:08.106 +00:00] [INF] [71] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:19:56.104 +00:00] [INF] [79] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:22:44.103 +00:00] [INF] [102] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:26:08.104 +00:00] [INF] [36] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:28:56.101 +00:00] [INF] [93] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:31:44.104 +00:00] [INF] [79] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:35:08.102 +00:00] [INF] [79] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:37:56.107 +00:00] [INF] [84] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:40:44.104 +00:00] [INF] [43] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:44:08.102 +00:00] [INF] [84] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:46:56.102 +00:00] [INF] [65] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:49:44.101 +00:00] [INF] [65] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:53:08.103 +00:00] [INF] [79] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:55:56.101 +00:00] [INF] [24] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 11:58:44.105 +00:00] [INF] [25] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:02:08.107 +00:00] [INF] [109] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:04:56.107 +00:00] [INF] [106] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:07:44.107 +00:00] [INF] [88] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:11:08.108 +00:00] [INF] [22] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:13:56.103 +00:00] [INF] [33] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:16:44.104 +00:00] [INF] [88] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:20:08.104 +00:00] [INF] [78] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:22:56.105 +00:00] [INF] [78] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:25:44.103 +00:00] [INF] [28] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:29:08.103 +00:00] [INF] [23] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:30:29.440 +00:00] [INF] [23] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" request
    [2024-05-25 12:30:35.329 +00:00] [INF] [23] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" request
    [2024-05-25 12:30:38.737 +00:00] [INF] [23] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" closed
    [2024-05-25 12:30:38.758 +00:00] [INF] [23] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" closed
    [2024-05-25 12:31:56.103 +00:00] [INF] [25] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:32:13.751 +00:00] [INF] [102] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" request
    [2024-05-25 12:32:18.906 +00:00] [INF] [85] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" request
    [2024-05-25 12:32:20.205 +00:00] [INF] [25] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" closed
    [2024-05-25 12:32:20.330 +00:00] [INF] [85] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" closed
    [2024-05-25 12:32:34.605 +00:00] [INF] [108] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" request
    [2024-05-25 12:32:41.376 +00:00] [INF] [67] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" request
    [2024-05-25 12:32:44.141 +00:00] [INF] [85] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" request
    [2024-05-25 12:32:46.753 +00:00] [INF] [24] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" closed
    [2024-05-25 12:32:46.758 +00:00] [INF] [24] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" closed
    [2024-05-25 12:32:46.787 +00:00] [INF] [24] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.1" closed
    [2024-05-25 12:34:44.105 +00:00] [INF] [21] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2024-05-25 12:38:08.106 +00:00] [INF] [46] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
    Serv: N5105 - 32GB RAM, 1 WD Red SA500 2TB, 2 8TB, 2 4TB WD Red Plus, LC-35U3-C-HUB
    OS: Debian
    Clients: Pi4 with LibreELEC + JellyCon and Jellyfin Media Player
    Network: 2 TP-Link AX23, OpenWRT mesh 802.11s and 1 Gbit
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #10
    2024-05-25, 05:39 PM
    Are you using a reverse proxy?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Pages (2): 1 2 Next »

    « 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