• 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 General Questions AuthenticationScheme: CustomAuthentication was challenged. CustomAuthentication ...

     
    • 0 Vote(s) - 0 Average

    AuthenticationScheme: CustomAuthentication was challenged. CustomAuthentication ...

    RelatableQuery
    Offline

    Junior Member

    Posts: 8
    Threads: 4
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #1
    2024-10-31, 09:21 PM (This post was last modified: 2024-10-31, 09:21 PM by RelatableQuery.)
    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.
    TheDreadPirate
    Online

    Community Moderator

    Posts: 11,857
    Threads: 10
    Joined: 2023 Jun
    Reputation: 347
    Country:United States
    #2
    2024-11-01, 12:40 AM
    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.
    Jellyfin 10.10.3 (Docker)
    Ubuntu 24.04 LTS 
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
    [Image: GitHub%20Sponsors-grey?logo=github]
    jinsokage
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #3
    2024-11-19, 09:26 AM (This post was last modified: 2024-11-19, 10:17 AM by jinsokage. Edited 3 times in total.)
    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
    TheDreadPirate
    Online

    Community Moderator

    Posts: 11,857
    Threads: 10
    Joined: 2023 Jun
    Reputation: 347
    Country:United States
    #4
    2024-11-19, 01:43 PM
    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.
    Jellyfin 10.10.3 (Docker)
    Ubuntu 24.04 LTS 
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
    [Image: GitHub%20Sponsors-grey?logo=github]
    1
    jinsokage
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Feb
    Reputation: 0
    Country:United States
    #5
    2024-11-19, 06:59 PM
    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
    « 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