The Android app gets stuck at login after Jellyfin v10.9.0.

[maru801]

Describe the bug

Ever since v10.9.0, after a successful login into the app, I can't reopen the Jellyfin Android app on my local network. If I do, I'm greeted with this screen:

The screen doesn't say it can't find the server, but that the connection can't be established. If I tap on the "Connect" button, it just spams my logs with "Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.190" request". I pasted a snippet of my server logs of when this happens in the log section here. The only way to fix this is to clear out the cache and data stored for the app, and this only works once. I have to keep clearing out the data if I close the app.

I'm running the Jellyfin server as a custom app on a Truenas Scale system. I port forwarded the 8096 port to 9001.
Strangely enough, I'm able to enter and use the Android app if I disconnect from my local network and start my Tailscale VPN.

I've tried the community app of Jellyfin that Truenas offers to use Host Networking to see if this solved my issue.
Enabling Host Networking does solve my issue of local network access, but it now breaks my Tailscale access for when I'm away from my local network. When this happens, I get greeted with a loading circle that takes a while to bring me to a server select screen. The only way to get the app to work again is to delete the server at this screen, close the app, and reopen it. For some reason, this issue doesn't generate any logs. And just in case, I also ran into the same issue on a Synology nas while running Jellyfin v10.9.1 from a Docker container.

Logs

[INF] [26] Jellyfin.Server.Implementations.Users.UserManager: Authentication request for "max" has succeeded.
[INF] [26] Emby.Server.Implementations.Session.SessionManager: Current/Max sessions for user "max": 1/0
[INF] [26] Emby.Server.Implementations.Session.SessionManager: Creating new access token for user <redacted>
[INF] [16] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.190" request
[WRN] [28] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "192.168.1.190" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."
[INF] [28] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.190" closed
[INF] [23] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.190" request
[INF] [23] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.190" request
[INF] [26] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.190" request

Application version

2.6.1

Where did you install the app from?

Google Play

Device information

Samsung Galaxy Note 9

Android version

Android 10 (w/ Samsung's One UI v2.5)

Jellyfin server version

10.9.1

Which video player implementations does this bug apply to?

• Web player (default)
• Integrated player (ExoPlayer)
• External player (VLC, mpv, MX Player)

[KimPig]

same here. Can't reconnect via reverse proxy.

[EHRETic]

same here. Can't reconnect via reverse proxy.

Hi there,

Same for me, stuck on the JF logo and no way to get it past it ;-)

[taitsmith]

semi able to replicate- updated to 10.9.1, signed out of active sessions on pixel 6 pro and experienced the same issues with 2.6.1 and debug built from the latest master branch. signing out all devices on the server dashboard / clearing cache / data seems to have fixed the issue on both the debug and 2.6.1 release versions. accessing the server remotely through tailscale also works after clearing data.

tested on physical pixel 6 pro android 14 (play store release / current master) and emulator pixel 8 pro android 14 (current master). i have an old samsung somewhere i can test on, if i can find it.

[KimPig]

semi able to replicate- updated to 10.9.1, signed out of active sessions on pixel 6 pro and experienced the same issues with 2.6.1 and debug built from the latest master branch. signing out all devices on the server dashboard / clearing cache / data seems to have fixed the issue on both the debug and 2.6.1 release versions. accessing the server remotely through tailscale also works after clearing data.

tested on physical pixel 6 pro android 14 (play store release / current master) and emulator pixel 8 pro android 14 (current master). i have an old samsung somewhere i can test on, if i can find it.

That's strange. I've deleted all devices from the server dashboard after updating to 10.9.0 and reinstalled the app on my phone, but I'm still having the same problem.

[PrimeO7]

I have the same Issue, but only on one of my devices.

Both run Android 8.1
Both run Jellyfin Android 2.6.1
Server Version 10.9.1

Behavior of the Problem Device:

• Fresh reinstall
• First time connecting to server via local ip: 192.168.1.14:8096
• Login successful
• Close app
• Reopen app
• Connection to server can't be established.
• Close app and delete all app data
• Add Server ip
• Connecting to server works again until app is closed, than the cycle repeats.

[taitsmith]

I have the same Issue, but only on one of my devices.

Both run Android 8.1 Both run Jellyfin Android 2.6.1 Server Version 10.9.1

interesting. can you post a bit of the server logs from when you (attempt) to connect with both devices? i’m still unable to reliably reproduce this with the 2.6.1 release, but building from the current master branch doesn’t seem to have any issues.

i do have a separate / potentially related issue on both android and ios but need to look into it more.

[maru801]

I think being able to reliably reproduce this issue depends on what and how the Jellyfin server is installed.

I have a Truenas Scale NAS & a Synology NAS.

Using the Jellyfin server on my Truenas Scale system, I get this Android error while on my local network. Using a VPN to use an external network makes everything work fine on it however. If I enable host mode network, local network works and the Android app doesn't run into this issue, but then fails to connect at times while on the VPN.

On the Synology with Jellyfin running in a Docker container, local network also works fine but my VPN stops working.

I have both servers using pretty much the same settings to run Jellyfin, so I don't know why it behaves differently on both.

[PrimeO7]

Okay, I no longer think the issue is caused by the android app.
I was actually able to cause this on the Linux jellyfin media player 1.10.0 and 1.9.1 as well.
I tried testing with android apk 2.6.0 and 2.6.1 the issue would persist with both.

I've decided to rollback my server to 10.8.13(docker linuxserver/jellyfin) and load the config files from a backup.
Ofc, no more issue now.

I guess server version 10.9.0+ has introduced some bugs in Networking.

[taitsmith]

I guess server version 10.9.0+ has introduced some bugs in Networking.

i was leaning towards this as well since i’ve had issues with android and ios (but not android tv or web). the most common issue on 2.6.1 on android results from the webview throwing a 404 and displaying an empty screen, but i havent found anything specific to the servers not showing up.

[DisloyalSnow911]

I have the same problem, just like the author.

[maru801]

I would also like to point out that if I wait a few hours at random, the app usually enters my server just fine again, then breaks if I close it afterwards.

[rusticrooster]

I have the same problem. This is happening on my LAN and WAN for two android phones, but not my Android TV. My devices are both Android Galaxy S23. Accessing Jellyfin via web browser on the devices works fine. For the server configuration I am not using a reverse proxy or HTTPS. I am using Tailscale VPN. Let me know if you'd like more details.