[Issue]: After upgrading to 10.9.1, the Android client cannot connect to the server（Fixed in version 10.9.3）

[as4134]

Please describe your bug

Upgrade Jellfyin to version 10.9.1 (including 10.9.0). The Android Jellyfin client can no longer connect to the server, but it can be accessed normally in the browser. I guarantee that my URL is correct and there are no firewall interception issues involved;
The Jellyfin server works through HTTPS, certificates are issued by trusted institutions, and the intermediate certificate chain is complete. Now, there is only one way to use the Jellyfin Android client to connect to the server:
Clear all application data and reopen it, fill in the server URL, in order to access it normally. However, once the client is closed and opened again, the problem will reappear, making it impossible to connect to the server.
The server only has one network card, and Jellyifn works in Windows, not in a Docker or virtual machine environment. The routing port mapping settings are correct.
I have also seen feedback from users on the forum regarding this issue, and the situation is consistent

Reproduction Steps

1. Open the Android client, client version v2.6.1
2. Enter server URL (HTTPS)
3. Connect to the server

Jellyfin Version

10.9.0

if other:

android client 2.6.1

Environment

- OS:
- Linux Kernel:
- Virtualization:
- Clients:
- Browser:
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration:
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

Log service prompt error, unable to provide at the moment

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

Code of Conduct

• I agree to follow this project's Code of Conduct

[jellyfin-bot]

Hi, it seems like your issue report has the following item(s) that need to be addressed:

• You have not filled in the environment completely.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

[voronind-com]

I have the same issue on one Android device out of three. Tried all old versions from fdroid, it persists even on old versions.

It connects for the first time, then after restart it is broken untill reinstalled.

[cohortcw179]

I too have similar issues. Both Android and Jellyfin Media Player (Windows) works well on first login. However, if I logged out of those apps, I can no longer log back in until I clear the apps data or reinstall. Tried the below or set server to bind to my local address. Even then nothing works.

<IgnoreVirtualInterfaces>false</IgnoreVirtualInterfaces>

[VigibotDev]

Yes all my device can't connect, all browsers need a data clean, and all android require uninstall/resintall to work only once :(

[VigibotDev]

For Jellyfin Windows Client app delete "C:\Users\Your Username\AppData\Local\Jellyfin Media Player" and re connect to get nominal working

[tumbly]

Same issue for me on android (server is running
10.9.1 on linux).

A temporary solution I found is force stopping the android app and deleting its storage.
This way I can login once and use the app normally, until I stop force it and try to start it again, this time I get a "Connection cannot be established" error.

[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[ERR] Error processing request: "Invalid token". URL "GET" "/socket".
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."

This issue looks like it's a duplicate of #11620

[wolonggl]

This bug is so bad that my jellyfin has stopped logging in

[fengzhengxaiowanzi]

10.9.2 also has this problem. I had this problem on both my Android devices, the first time I logged in fine, then I had to clear the data to get it to work, and the console logs showed everything was fine, so I had to roll back to 10.8.13

[Alliyance]

The new update is a outta mess :(:(:(:(

[as4134]

新的更新是一个混乱的:(:(:(:(

Yes, 10.9.2 didn't fix this

[voronind-com]

Same issue for me even on 10.9.2 and android app built from master.
This is the link for android app issue: jellyfin/jellyfin-android#1382

[svenlindekugel]

Can confirm as well starting with 10.9.1, running genuine docker image, the Jellyfin app needs clear data after app restart.

[CatSamaDD]

The issue is still found in version 10.9.2. I believe the problem lies in the token verification mechanism added in the updates after version 10.9 to address the longstanding security concerns. However, the Android version 2.6.1 has not been updated simultaneously to adapt to this change.

[voronind-com]

Seems to be closed by jellyfin/jellyfin-android#1382 (comment)

We'll need to update the server once 10.9.3 releases (not yet).

[wolonggl]

Version 10.9.3 still has the same issue

[as4134]

版本 10.9.3 仍然存在同样的问题

I tested it and this has been fixed in 10.9.3, you can reinstall it after partial server data.

[VigibotDev]

Jellyfin Server 10.9.3 solve the Android Mobile App login problem for me ! Thanks for the work