AuthenticationScheme: CustomAuthentication was challenged. CustomAuthentication ... - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions) +--- Thread: AuthenticationScheme: CustomAuthentication was challenged. CustomAuthentication ... (/t-authenticationscheme-customauthentication-was-challenged-customauthentication) |
AuthenticationScheme: CustomAuthentication was challenged. CustomAuthentication ... - RelatableQuery - 2024-10-31 I am watching my docker container logs, and I am seeing the following messages get repeated every few seconds. How can I find out where this is coming from? jellyfin | [21:18:45] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged. jellyfin | [21:18:50] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token. jellyfin | [21:18:50] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token. jellyfin | [21:18:50] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged. jellyfin | [21:18:55] [INF] [36] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token. jellyfin | [21:18:55] [INF] [36] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token. jellyfin | [21:18:55] [INF] [36] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged. RE: AuthenticationScheme: CustomAuthentication was challenged. CustomAuthentication ... - TheDreadPirate - 2024-11-01 Unfortunately you can't. I've seen this before, tried enabling debug logging, but the debug logs didn't say which device was the culprit. This happens when a device's token was expired and you haven't re-logged in on that device. RE: AuthenticationScheme: CustomAuthentication was challenged. CustomAuthentication ... - jinsokage - 2024-11-19 how does one fix this? randomly started getting this and I can no longer get into Jellyfin. I've even blown it up and tried multiple images/versions and it keeps giving me the same error. Do I have to move this container onto a totally different host or something? Even after nuking the container and trying to start fresh, I get the login screen but it's the regular one and not the one to create the admin user. *EDIT* so yeah, I created a new stack on a new host and I get the creation wizard. Very odd, any ideas on how I can completely purge Jellyfin from the other server that's throwing that Authentication error? https://github.com/jellyfin/jellyfin/issues/11620 this is about something hitting my instance. Not sure what, since every connection was either deleted or is offline. Once I changed the external port the errors stopped RE: AuthenticationScheme: CustomAuthentication was challenged. CustomAuthentication ... - TheDreadPirate - 2024-11-19 On the original host you can also re-enable the setup wizard. Stop Jellyfin then open the following file. Windows: C:\ProgramData\Jellyfin\Server\config\system.xml Linux: /etc/jellyfin/system.xml Docker: /config/config/system.xml (within where you mounted the /config volume) Set IsStartupWizardComplete to false. Start Jellyfin, go through the setup wizard. You only need to set your credentials, skip the rest. RE: AuthenticationScheme: CustomAuthentication was challenged. CustomAuthentication ... - jinsokage - 2024-11-19 thanks. that's good to know if this happens again. after switching my port and creating the admin account, I was able to switch the port back. No idea what glitched out my instance, but I get to redo all my settings now. Joy |