Login issue - Authentication failing

Issue description:

When resuming a session from yesterday, I got errors that my media was unavailable.

Trying to remove and read the server I get an authentication failure. I am able to log in through the web and the jellyfin app with the same connection URL and credentials.

Jellyfin server does not log that there was any log in attempt, invalid or otherwise.

Logs:

Upload description: bslavergne

Additional information:

 

 

Reproduction steps:

 
Add new server
http://bslavergne.com:32500/
Enter credentials
 

Media provider:

Jellyfin

Screenshots:

     

Well AuthenticateByName is called and returns error 400. Check your proxy, probably some “security” settings blocking the call.

I don’t have any proxy set up. Unsure what security setting could be blocking it, could you give me an idea of where to look? Default jellyfin app and web logins are working just fine locally and through external IP.

When on the local network, I have the same problem trying to connect using direct local IP. If that helps eliminate some of the potential problems.

I have no way to know, something answer error 400.
It should be present in the server logs and show why.

[2025-12-27 07:50:18.544 -06:00] [ERR] Error processing request. URL “POST” “/Users /AuthenticateByName”. System. ArgumentNullException: Value cannot be null.

[2025-12-27 07:50:19.479 -06: 00] [ERR] Error processing request: “Token is required” . URL “GET” "/socket ".

[2025-12-27 07:50:20.868 -06:00] [INF] “CustomAuthentication” was not authenticated. Failure message: “Invalid token.”

Here’s what I’m seeing in the logs, is this helpful at all?

Not really the app can’t send null data, do you have enabled some plugins or SSO or anything ?

No plugins related to logins, no SSO.

There’s more in the log, if you don’t mind taking a look. Did a restart, log starts with the shutdown command and goes for about 300 lines. Tons of repeated auth errors, but 232 has the 400 error you pointed out.

Cleared up the repeating auth errors, I think I had a tab open that was continually trying to hit the server.

The symfonium specific login issue persist, same exception is being thrown as in the log from my last reply.

Any insight would help greatly. I’ve really loved using the app compared to the base jellyfin music player experience.

There’s not much more I can do here, Jellyfin returns an error without more details, I can’t guess why your specific server does that.

Finally got back home from being out of town and could dig into it.

/etc/jellyfin/system.xml

EnableLegacyAuthorization needs to be set to true. Upgrading to 10.12 sets that to false and breaks Symfonium.

10.11 is broken as hell and you play with 10.12 :slight_smile:

Will add support for the new auth in next release.

1 Like

Thanks for the help :slightly_smiling_face:

Feeling great about buying your app :slightly_smiling_face: