I’m using infuse on an ipad connecting to a jellyfin server
Immediately after upgrading, my pre-existing jellyfin location stopped working, with me getting a not found error
I tried deleting and readding but to no avail
I’ve used it without issue for quite a while. Could something have changed in the latest update with respect to how I need to configure the connection?
note that i just checked by using swiftfin and it connected without issue
A post was merged into an existing topic: .strm files managed by Jellyfin not playing in Infuse
Would you be able to send in a quick report from your device and post the 5 digit code it gives you here?
from iphone: J8QBD
seeing anecdotal reports of the issue on apple tv as well (but i myself dont have one). will share ipad in a little
iphone is above
ipad: RCJQE
What version of Jellyfin are you using?
Also, can you check to ensure Infuse has access to the Local Network? More info on this can be found in this guide.
jellyfin version 10.8.13
just checked, app already has local access
fwiw on the infuse reddit others are starting to share their issues too. i told them to post diagnostics here if they can
Thanks for that.
It may be a compatibility issue with Jellyfin 10.8 and some of the newer APIs which Infuse now uses.
We will certainly look into this, but have you thought about updating to Jellyfin 10.10?
My Jellyfin is 10.7.7, and it still can’t connect after the upgrade.
per above
Have you abandoned support for versions prior to 10.10?
I’m using jellyfin on a server from ultra.cc. They provide a turnkey jellyfin solution which looks like it is currently 10.8. I am going to ask about what their plans are for upgrading it etc, though I wonder if it might be too early to drop support for previous releases
We test against the 2 most recent versions of Jellyfin which would be 10.9 and 10.10.
Jellyfin 10.7 was released in 2021 and 10.8 was released in 2022. Jellyfin has stopped updating both with the last release being 10.8.13 which was released in 2023.
For efficiency it makes sense to draw the line somewhere, but I am curious if there are specific reasons to run these older versions. AFAIK, newer versions do not have any new hardware requirements and since Jellyfin is free there certainly is not a cost component.
Thanks for sharing this. It’s interesting they are staying with an older version and I would be curious to know if there is a specific reason or if an upgrade is planned.
i checked today and it is now 10.10! i wonder if this wqs the reason…
infuse does indeed work fine with 10.10. that said, i suppose it’s worth considering how many years of backwards compatibility make sense (2 seems quick for a tool like infuse, but i suppose it depends), and ideally in the future if backwards compatibility is broken that can be communicated, but I realize this is just one small part of the total infuse offering (and i mean, i am a huge fan of infuse, little complaints here and there aside!)
Oh nice, that’s great to hear! 
There wasn’t a direct intention to drop support for older versions here, but the API changes in this update will presumably be required by an upcoming Jellyfin version (maybe 10.11?). Supporting both old and new would present a number of challenges with somewhat diminishing returns since most people are running newer Jellyfin versions.
There are of course a number of benefits to running the current version of Jellyfin (security or otherwise) so it’s probably not a terrible idea to update.
Unfortunately some of us can’t update to later Jellyfin versions easily on the older devices we use as a video server (my old MacOS laptop that I’ve just setup to run Jellyfin on, then bought an Apple TV and just subscribed for Infuse Pro only for it to cut out in 2 weeks with an automatic update doesn’t support beyond Jellyfin 10.8 due to MacOS incompatibilities)
Thanks for sharing this info.
We’re looking into a few options here.
Everything worked fine yesterday (05/28), and I have made no changes to any configuration – neither jellyfin’s, nor InFuses. However, today (05/29) when I tried to load my content using InFuse on my AppleTV, it was unable to access my jellyfin content.
It gave me “Error”. Like any good troubleshooter would do, I removed the jellyfin server configuration and attempted to re-add it. InFuse recognized my server in the Shares > Add Media Server > Available Servers. I clicked on that, and entered in my username/password. When I click add it says Checking Connection, and almost immediately comes back with an alert saying “An error occurred”. I have also uninstalled and reinstalled the Infuse plugin for jellyfin, without success. I have also uninstalled and reinstalled the AppleTV app.
When I go to my jellyfin server via Chrome, and I check the logs, it says authentication succeeded and reissuing access token. See log below.
[2025-05-29 21:22:47.338 -04:00] [INF] Startup complete 0:00:28.4479103
[2025-05-29 21:22:48.884 -04:00] [INF] Authentication request for "jellyfin" has succeeded.
[2025-05-29 21:22:48.887 -04:00] [INF] Current/Max sessions for user "jellyfin": 1/0
[2025-05-29 21:22:48.943 -04:00] [INF] Reissuing access token: "xxxx"
[2025-05-29 21:22:49.033 -04:00] [WRN] Slow HTTP Response from "http://mediacenter.local/Users/AuthenticateByName" to "192.168.x.x" in 0:00:01.1641388 with Status Code 200
[2025-05-29 21:22:50.063 -04:00] [INF] Watching directory "/media/shows"
[2025-05-29 21:22:51.636 -04:00] [INF] Watching directory "/media/movies"
[2025-05-29 21:24:29.742 -04:00] [INF] Authentication request for "jellyfin" has succeeded.
[2025-05-29 21:24:29.743 -04:00] [INF] Current/Max sessions for user "jellyfin": 2/0
[2025-05-29 21:24:29.750 -04:00] [INF] Reissuing access token: "xxxx"
[2025-05-29 21:24:29.804 -04:00] [WRN] Slow HTTP Response from "http://192.168.x.x:80/Users/AuthenticateByName" to "192.168.x.x" in 0:00:01.0295062 with Status Code 200
[2025-05-29 21:27:06.922 -04:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets.
[2025-05-29 21:28:06.946 -04:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets.
[2025-05-29 21:29:06.968 -04:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets.
[2025-05-29 21:30:06.980 -04:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets.
[2025-05-29 21:31:06.997 -04:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets.
[2025-05-29 21:32:07.009 -04:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets.
[2025-05-29 21:32:09.321 -04:00] [INF] Authentication request for "jellyfin" has succeeded.
[2025-05-29 21:32:09.322 -04:00] [INF] Current/Max sessions for user "jellyfin": 2/0
[2025-05-29 21:32:09.329 -04:00] [INF] Reissuing access token: "xxxx"
[2025-05-29 21:32:09.331 -04:00] [WRN] Slow HTTP Response from "http://192.168.x.x:80/Users/AuthenticateByName" to "192.168.x.x" in 0:00:00.981574 with Status Code 200
I have submitted diagnostics and the code is TMCQ8. Thank you in advance!
I moved your post to an already running thread discussing this issue. It appears that if you can, upgrading your Jellyfin to 10.10 that should solve your problem. The dev is researching this issue so you may want to read through this thread to see what’s been discussed. 