no IP in Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token. #7049

Open
opened 2026-02-07 04:26:38 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @prahal on GitHub (May 31, 2025).

Description of the bug

Please log IP of the offender, or anything to identify it, I get this error every 10 seconds and I cannot find which device cause it:
[10:24:03] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[10:24:03] [ERR] [3] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: Invalid token. URL GET /socket.

Reproduction steps

I have no idea which device cause the error in the log. That is the point of this bug report.

What is the current bug behavior?

Logs error about device without telling which device
[10:24:03] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[10:24:03] [ERR] [3] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: Invalid token. URL GET /socket.

What is the expected correct behavior?

Log an IP with the error or anything identifying the device with the invalid token error.

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

10.10.7

Specify the build version

10.10.7

Environment

- OS: Debian 12
- Linux Kernel: 6.12.22 armbian rockchip64
- Virtualization: docker
- Clients: Debian 13, Android 
- Browser: Firefox
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration:
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

[10:24:03] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[10:24:03] [ERR] [3] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: Invalid token. URL GET /socket.

FFmpeg logs


Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @prahal on GitHub (May 31, 2025). ### Description of the bug Please log IP of the offender, or anything to identify it, I get this error every 10 seconds and I cannot find which device cause it: [10:24:03] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token. [10:24:03] [ERR] [3] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: Invalid token. URL GET /socket. ### Reproduction steps I have no idea which device cause the error in the log. That is the point of this bug report. ### What is the current _bug_ behavior? Logs error about device without telling which device [10:24:03] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token. [10:24:03] [ERR] [3] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: Invalid token. URL GET /socket. ### What is the expected _correct_ behavior? Log an IP with the error or anything identifying the device with the invalid token error. ### Jellyfin Server version 10.10.0+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number 10.10.7 ### Specify the build version 10.10.7 ### Environment ```markdown - OS: Debian 12 - Linux Kernel: 6.12.22 armbian rockchip64 - Virtualization: docker - Clients: Debian 13, Android - Browser: Firefox - FFmpeg Version: - Playback Method: - Hardware Acceleration: - GPU Model: - Plugins: - Reverse Proxy: - Base URL: - Networking: - Storage: ``` ### Jellyfin logs ```shell [10:24:03] [INF] [3] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token. [10:24:03] [ERR] [3] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: Invalid token. URL GET /socket. ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
OVERLORD added the enhancementsecurity labels 2026-02-07 04:26:38 +03:00
Author
Owner
@prahal commented on GitHub (May 31, 2025): Issue mentioned in https://forum.jellyfin.org/t-authenticationscheme-customauthentication-was-challenged-customauthentication
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#7049