+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic (/t-jellyfin-api-auth-customauthenticationhandler-customauthentication-was-not-authentic)
Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic - miek - 2025-02-13
So, when I look at my logs, I see the following messages just "spamming" over and over and over non stop. I am able to scan in new media no issues. Playback isn't an issue. Everything appears to be working, I just can't seem to figure out why this error is spamming like it is
[01:12:02] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:02] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:02] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:03] [INF] [68] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:03] [INF] [68] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:03] [INF] [68] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:04] [INF] [43] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:04] [INF] [43] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:04] [INF] [43] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:05] [INF] [43] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:05] [INF] [43] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:05] [INF] [43] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:06] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:06] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:06] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:07] [INF] [68] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:07] [INF] [68] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:07] [INF] [68] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:08] [INF] [34] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:08] [INF] [34] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:08] [INF] [34] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:09] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:09] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:09] [INF] [46] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:10] [INF] [68] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:10] [INF] [68] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:10] [INF] [68] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:11] [INF] [34] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:11] [INF] [34] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:11] [INF] [34] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:12] [INF] [43] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:12] [INF] [43] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:12] [INF] [43] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
[01:12:13] [INF] [34] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:13] [INF] [34] Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authenticated. Failure message: Invalid token.
[01:12:13] [INF] [34] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged.
I don't have any plugins installed except for the default few. So no clue what the problem is.
RE: Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic - TheDreadPirate - 2025-02-13
9 times out of 10 this is a TV client (Android TV or Roku) whose token has expired or was revoked and you never re-logged in on it. So it is continuously trying to log in with an invalid token until you go to that TV and provide new credentials.
RE: Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic - miek - 2025-02-13
Ah so it's most likely one of my friends who just needs to "relog". Cool. That makes me feel a lot better. Sucks it's spamming the logs though, but at least it's "Hopefully" a nothing issue.
RE: Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic - TheDreadPirate - 2025-02-13
If this was a bad actor trying to log in, it would log a different message. It would explicitly say that an invalid username/password was provided.
RE: Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic - m3z - 2025-03-28
Hello
I meet the same problem (lot of invalid token) after a fresh install of jellyfin using swizzin box.
I already install Jellyfin on the same swizzin box and i was ok. I uninstall for some test and now it doesn't works.
I restored container backup to recover state before first Jellyfin installation.
But it doesn't help i still have same problem.
Now I can connect to jellyfin web but from here i am unable to connect to Jellyfin server.
I can see my server. If i click to connect i get message: "We are unable to connect to the selected server. Please check that it is operational and try again."
Please find below the conf:
Server is a privileged lxc container manage by proxmox 8.2.4 (2 cpu/4 gb ram/16 gb disk, nestling enable).
Os : Ubuntu 22.04.5 LTS (Jammy Jellyfish)
Jellyfin.Server 10.10.6.0 is installed using swizzin script.
root@xxxxxx:~# box install jellyfin
INFO Installing jellyfin
DOCS Further reference: https://swizzin.ltd/applications/jellyfin
Warning: output encryption option -nodes ignored with -export
... Performing apt update
\u2714 Done
... Performing installation of 1 apt packages
(jellyfin)
\u2714 Apt install complete
Failed to restart jellyfin.service: Unit jellyfin.service is masked.
SUCCESS Jellyfin installedq
root@ xxxxxx :~# systemctl unmask jellyfin.service
root@ xxxxxx :~# systemctl start jellyfin.service
systemctl status jellyfin.service
* jellyfin.service - Jellyfin Media Server
Loaded: loaded (/lib/systemd/system/jellyfin.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/jellyfin.service.d
-jellyfin.service.conf
Active: active (running) since Fri 2025-03-28 11:00:13 CET; 11s ago
Main PID: 19987 (jellyfin)
Tasks: 29 (limit: 18897)
Memory: 134.3M
CPU: 15.428s
CGroup: /system.slice/jellyfin.service
|-19987 /usr/bin/jellyfin --webdir=/usr/share/jellyfin/web --ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg
-20018 /usr/lib/jellyfin-ffmpeg/ffmpeg -hide_banner -f lavfi -i nullsrc=s=1x1:d=10000 -f null -Mar 28 11:00:19 hesperide jellyfin[19987]: [11:00:19] [INF] Available decoders: ["libdav1d", "av1", "av1_cuvid", "av1_qsv", "h264", "h264_qsv", "h264_cuvid", "hevc", "hev>
Mar 28 11:00:19 hesperide jellyfin[19987]: [11:00:19] [INF] Available encoders: ["libsvtav1", "av1_nvenc", "av1_qsv", "av1_amf", "av1_vaapi", "libx264", "h264_amf", "h264>
Mar 28 11:00:19 hesperide jellyfin[19987]: [11:00:19] [INF] Available filters: ["bwdif_cuda", "deinterlace_qsv", "deinterlace_vaapi", "flip_vulkan", "hwupload_cuda", "hwu>
Mar 28 11:00:20 hesperide jellyfin[19987]: [11:00:20] [INF] Available hwaccel types: ["cuda", "vaapi", "qsv", "drm", "opencl", "vulkan"]
Mar 28 11:00:22 hesperide jellyfin[19987]: [11:00:21] [INF] CustomAuthentication was not authenticated. Failure message: Invalid token.
Mar 28 11:00:22 hesperide jellyfin[19987]: [11:00:22] [INF] CustomAuthentication was not authenticated. Failure message: Invalid token.
Mar 28 11:00:22 hesperide jellyfin[19987]: [11:00:22] [INF] AuthenticationScheme: CustomAuthentication was challenged.
Mar 28 11:00:22 hesperide jellyfin[19987]: [11:00:22] [INF] Clean Transcode Directory Completed after 0 minute(s) and 0 seconds
Mar 28 11:00:22 hesperide jellyfin[19987]: [11:00:22] [INF] Clean up collections and playlists Completed after 0 minute(s) and 0 seconds
Mar 28 11:00:23 hesperide jellyfin[19987]: [11:00:23] [INF] Update Plugins Completed after 0 minute(s) and 0 seconds
logs:
https://paste-bin.xyz/8153696
Thanks for your help
RE: Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic - TheDreadPirate - 2025-03-28
Is there a reverse proxy handling connections? One thing I noticed is that Jellyfin only found the local loopback. If there isn't another app handling external connections, you'd only be able to reach Jellyfin from the host running Jellyfin in its current state.
RE: Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic - m3z - 2025-03-28
Hi TheDreadPirate
and thanks you for your help.
Yes your right, there is an nginx server featured with swizzin that works as reverse proxy.
Here is the setup for jellyfin
location /jellyfin {
proxy_pass https://127.0.0.1:8920;
#
proxy_pass_request_headers on;
#
proxy_set_header Host \$proxy_host;
#
proxy_http_version 1.1;
#
proxy_set_header X-Real-IP \$remote_addr;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto \$scheme;
proxy_set_header X-Forwarded-Protocol \$scheme;
proxy_set_header X-Forwarded-Host \$http_host;
#
proxy_set_header Upgrade \$http_upgrade;
proxy_set_header Connection \$http_connection;
#
proxy_set_header X-Forwarded-Ssl on;
#
proxy_redirect off;
proxy_buffering off;
auth_basic off;
}
RE: Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic - TheDreadPirate - 2025-03-28
Can you try clearing your browser cache or opening a private browser window?
RE: Jellyfin.Api.Auth.CustomAuthenticationHandler: CustomAuthentication was not authentic - m3z - 2025-03-29
Hi TheDreadPirate,
That's it. After the clearing cache it works again.
I'm sorry I didn't think of it and waste your time for that
Many thanks for your help.
I will take time to discover Jellyfin
Thanks again !