+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Logs filling up with same error (/t-logs-filling-up-with-same-error)
Logs filling up with same error - dazzleduds20 - 2024-02-29
Hi all, when setting up jellyfin through docker on unraid my logs get filled with these log entries -
[02:14:17] [INF] [30] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[02:14:17] [INF] [30] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[02:14:17] [INF] [30] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
I have tried multiple Jellyfin containers and they all give me these same errors.
Does anyone know what these are related to and how I can stop them?
These happen before setting anything up inside jellyfin and once its all setup aswell.
Thanks in advanvce, Darren
RE: Logs filling up with same error - dazzleduds20 - 2024-02-29
Here is some of the recent logs, just so you can see how often they are incase that would point to something-
[2024-02-29 02:49:21.810 +00:00] [INF] [44] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:49:21.810 +00:00] [INF] [44] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:49:21.810 +00:00] [INF] [44] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:49:51.862 +00:00] [INF] [14] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:49:51.862 +00:00] [INF] [14] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:49:51.863 +00:00] [INF] [14] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:50:21.956 +00:00] [INF] [54] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:50:21.956 +00:00] [INF] [54] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:50:21.956 +00:00] [INF] [54] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:50:52.012 +00:00] [INF] [53] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:50:52.012 +00:00] [INF] [53] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:50:52.012 +00:00] [INF] [53] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:51:22.045 +00:00] [INF] [14] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:51:22.045 +00:00] [INF] [14] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:51:22.045 +00:00] [INF] [14] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:51:52.091 +00:00] [INF] [54] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:51:52.091 +00:00] [INF] [54] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:51:52.091 +00:00] [INF] [54] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:52:22.142 +00:00] [INF] [44] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:52:22.142 +00:00] [INF] [44] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:52:22.142 +00:00] [INF] [44] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:52:52.182 +00:00] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:52:52.182 +00:00] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:52:52.182 +00:00] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:53:22.233 +00:00] [INF] [59] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:53:22.233 +00:00] [INF] [59] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:53:22.233 +00:00] [INF] [59] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:53:52.284 +00:00] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:53:52.284 +00:00] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:53:52.284 +00:00] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:54:22.327 +00:00] [INF] [51] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:54:22.327 +00:00] [INF] [51] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:54:22.327 +00:00] [INF] [51] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
[2024-02-29 02:54:52.400 +00:00] [INF] [55] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:54:52.400 +00:00] [INF] [55] Jellyfin.Api.Auth.CustomAuthenticationHandler: "CustomAuthentication" was not authenticated. Failure message: "Invalid token."
[2024-02-29 02:54:52.400 +00:00] [INF] [55] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: "CustomAuthentication" was challenged.
RE: Logs filling up with same error - TheDreadPirate - 2024-02-29
Did you recently change passwords?
RE: Logs filling up with same error - dazzleduds20 - 2024-02-29
No, this happens on a new docker container before I set anything up. I tried multiple containers including the official one.
Why does that message usually show up for a device trying to login?
RE: Logs filling up with same error - TheDreadPirate - 2024-02-29
If you have a new server, but you have clients that were previously connect to Jellyfin at the same IP, could they be attempting to log back in with the previously used credentials? Like a phone or Android TV?
RE: Logs filling up with same error - dazzleduds20 - 2024-02-29
It was only me on the last server, could plugins cause this? maybe jellyseer? Or is that error only for a device trying to login?
RE: Logs filling up with same error - dazzleduds20 - 2024-02-29
I think I may have found it, the kid's bedroom firestick. I added the quick connect, and so far, the messages seem to have stopped. Thanks for pointing me in the right direction
