Open tarumes opened 1 month ago
jellyfin-bot
commented
1 month ago Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems.
tarumes
commented
1 month ago duplicate https://github.com/jellyfin/jellyfin/issues/11597 after some tests something is aggressively saved in the browser cache
edit 2:
mirolm
commented
1 month ago Same happens to me. Ocurrs in both jellyfin-web and jellyfin-media-payer.
Also happens in both scenarions - with or without reverse proxy.
To reproduce:
When this happens i see in jellyfin log:
[2024-05-13 16:32:36.374 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.384 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.414 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.415 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.417 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.419 +00:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-05-13 16:32:36.422 +00:00] [ERR] Error processing request: "Invalid token". URL "GET" "/socket".
[2024-05-13 16:32:36.425 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.426 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.427 +00:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-05-13 16:32:36.509 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.510 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.534 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.534 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.537 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.538 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.538 +00:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-05-13 16:32:36.538 +00:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-05-13 16:32:36.574 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:36.576 +00:00] [ERR] Error processing request: "Invalid token". URL "GET" "/socket".
[2024-05-13 16:32:37.925 +00:00] [INF] "Clean up collections and playlists" Completed after 0 minute(s) and 0 seconds
[2024-05-13 16:32:39.252 +00:00] [INF] "Update Plugins" Completed after 0 minute(s) and 1 seconds
[2024-05-13 16:32:43.120 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:43.120 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:43.120 +00:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-05-13 16:32:43.126 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:43.128 +00:00] [INF] "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-05-13 16:32:43.128 +00:00] [INF] AuthenticationScheme: "CustomAuthentication" was challenged.In the chromium log we have:
Easiest workaround is to delete site data in the browser. To get out of this in jellyfin media player you need to stop jellyfin as a service in order to get to add/delete server screen.
Ozwel
commented
1 month ago Having that issue too.
Accessing the web interface from localhost or using the server's IP works every time. Seems to fail only when using the domain name.
Private/Incognito browsing session doesn't help.
I've had no issue with 10.8.13 for months.
will-molloy
commented
1 month ago Clearing cache doesn't help.
Ozwel
commented
1 month ago Clearing cache doesn't help.
Isn’t it resolved with 10.9.2?
tarumes
commented
1 month ago Clearing cache doesn't help.
might be good to have some more data @will-molloy
clientside:
did you tried to delete all of the website data not just cache?
serverside:
XeClutch
commented
1 month ago Ran into this myself, here's a workaround:
<ip>:<port>/web/index.html<ip>:<port>
At that point you should be prompted to log back in. Something is going on with the authentication, not sure what. Note: Some of those steps may be unnecessary but that's what I did to get back into my library.
hughwilliams94
commented
2 weeks ago Even using the above workaround doesn't work for me. I've noticed that the issue only occurs if I'm disconnected from the internet. I'm running jellyfin locally on my laptop using the jellyfin and jellyfin-web packages from Alpine Linux. It shouldn't be making requests to the internet presumably but it seems to hang as if it is waiting for a connection. Checking the browser network logs when it is connected to the internet doesn't show any reqeusts to addresses other than localhost
Please describe your bug
as i updated from 10.8.13 to 10.9.0 the WebUI does nothing
since i dont get browser log i dont know if its related to https://github.com/jellyfin/jellyfin/issues/11597
Reproduction Steps
as i updated from 10.8.13 to 10.9.1
Jellyfin Version
10.9.0
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
no logs in browser
Please attach any screenshots here
Code of Conduct