Infuse cannot connect to Jellyfin

I’m pulling my hair out a bit here :sweat_smile: Infuse suddenly refuses to connect to my Jellyfin server, while literally every other Jellyfin client (web, official app, etc.) works perfectly. It’s definitely something on the Infuse side.

Quick rundown:

• Jellyfin: 10.11.5 (latest stable) and 10.12.0 (unstable version)

• Infuse: Latest stable version

• Trying to connect directly with server address + username/password over local network (no reverse proxy or anything fancy)

• Infuse just says “Unable to connect to the server”

When I look at the Jellyfin logs, I see this every time Infuse tries to log in:

System.ArgumentNullException: Value cannot be null. (Parameter ‘request.App’)

at Emby.Server.Implementations.Session.SessionManager.AuthenticateNewSessionInternal(AuthenticationRequest request, Boolean enforcePassword)
at Jellyfin.Api.Controllers.UserController.AuthenticateUserByName(AuthenticateUserByName request)

Infuse isn’t sending the “App” name in the login request, so Jellyfin rejects it.
I’ve already tried pretty much everything:
• Deleted the server in Infuse, cleared metadata cache, force-quit the app, restarted my Apple TV/iPhone/iPad, re-added the server from scratch, deleted Infuse data in the iCloud.
• Fully uninstalled and reinstalled Infuse
• Restarted the Jellyfin server (clears all sessions)
• Changed the user password
• Tried different accounts
Nothing works. This feels a lot like those compatibility hiccups we had earlier in 2025 when an Infuse update temporarily broke Jellyfin connections.
Anyone else running into this right now? Or any tips from the Firecore team? I’d really appreciate any help
Thanks!

I am also having bad connections to Jellyfin. It works temporarily - for about a day or so - until it fails to connect or index and I need to completely re-add the server. Very frustrating.

I’m having a similar issue where I can’t connect to my remote server via infuse but literally every other app works. Also of note if I was already connected to the server it works. I just can’t add it as a new server on any of my infuse devices that didn’t already have it.

The upcoming 8.3.6 version of Infuse will add support for logging into Jellyin 10.12 (unstable).

If at some point you have installed 10.12 and then rolled back to 10.11.x there will be a change to a settings file that remains in place and will continue to affect your 10.11.x installation. More info on rolling back this change can be found in this guide.

Thank you!

Today’s 8.3.6 update adds initial support for Jellyfin 10.12 (unstable).

Note: Running unstable Jellyfin builds is always a little risky and there will likely more improvements coming as development of the 10.12 version progresses.

Didn’t fix my issue. Still unable to connect.

Also still having issues on latest Infuse build and Jellyfin 10.11.6

Having the same issue as other users here, server version 10.11.6 and latest Infuse build, still getting ‘can’t connect to server’ while it’s fine in other apps.

I wasn’t having issue with jellyfin 10.11.5 but suddenly today it stopped connecting. Removing and re-adding the server does not help and other devices have no issue connecting to Jellyfin. Looks like something changed in infuse, breaking connectivity.

I tried repeatedly over the last few days with no luck, haven’t changed anything on server or client end and then suddenly when I tried to re-add the server a few moments ago it randomly worked…. Not a massive help to your issue I know but keep giving it a go until there’s a response from devs, you may get lucky like I did.

So I noticed that with the jellyfin username of “infuse” I would get a connection error, but if I entered in an invalid username, I would get a bad password response. So I tried connecting with my infuse admin account and it worked without issue.

My guess is there is a bug in the infuse codebase where it fails if the username is “infuse”. Can anyone else replicate this behavior?

If you are seeing any issues with the current 8.3.7 version of Infuse it may be best to submit a report from your device so we can look further into what may be going on.

Thanks James. I’ve done that now.

For everyone in this thread, I also created a new user “jelly-infuse” with the same permissions as “infuse” and the failed connection issue went away.

Thanks for sending that in.

The logs seem to point to server-side issues. The last successful login with the ‘infuse’ user was on 2026-02-06 at 13:10:25. Later that same day, all connection attempts started failing with a 500 Internal Server Error. I am not sure if any server changes were made around that time. I suppose it’s possible the account itself may have gotten corrupted somehow, but it’s hard to speculate on what may have caused this.

We’ve double-checked things here and there isn’t any logic in place that would block certain Jellyfin usernames, so as a quick test you could look at deleting the original ‘infuse’ user and recreating it. Presumably this should work in the same way the new ‘jelly-infuse’ user is working now.

Thanks James. The server didn’t update, but when I went to delete the “infuse” user the Jellyfin just spun. This indicated to me that there was a server side issue. Rebooting the Jellyfin service resolved the issue.

What remains odd is that CoreEelec (kodi) and the native Jellyfin client on iOS had no issues with the same user account.

It does seem strange, but I can’t really provide much more of an explanation. It’s definitely something we haven’t seen before, but we can do more digging if we see any additional reports come in.

Suddenly working again for me. I changed nothing. Just happened to try this morning and it worked.

Made an account on this forum because Infuse is literally the only broken client I have for my jellyfin (10.11.5) out of all of them. The others work perfectly fine for years. I just bought infuse and I’m wondering if there’s a return policy or something on the lifetime. I really didn’t think it’d be this buggy.

Sorry to hear that. If you can submit a report from your device and post the 5 digit code here we can look further into your specific case.