I submitted a support request but I can’t seem to see it via the Zendesk link so made a topic here (my diagnostics are TB2JH) so decided to also make a topic here in case anyone has had the same issues as me.
This behaviour happens on both tvOS and ipadOS.
Using latest stable jellyfin, and infusesync plugin.
I recently had to rebuild my JF install due to a hardware issue, and while I’m mostly back up and running (Everything looks fine on the Jellyfin end and all my media plays fine there), when I add my JF share in Infuse, I get an “Indexing failed” error after “Fetching content” runs for a few seconds.
This only happens for one specific folder, my Anime folder, which uses Shoko Anime as a metadata provider within JF. If I uncheck that Library and Scan for Changes everything not in that Library fetches just fine. Unfortunately, there’s no useful error output that I can pin this down any further as to what is actually going wrong so hopefully can get some insight into it here.
Also noticing this in swiftfin so I suspect it’s a problem with the library but I currently have no way to view logs for either so hoping I can find out the actual error with my library
Just as additional info if anyone else runs into this - I managed to get it to index by restarting my server and hitting scan for changes in infuse just as the jellyfin server comes back up (behaviour which I can replicate with backups etc) so I’ve got a working Infuse now across both beta and non beta versions but this issue still reoccurs if I have ever to “freshly” index my jellyfin server again (say on a new device with no iCloud sync).
Just ran into this again with no changes to my library except the addition of some new files to my jellyfin server, pretty frustrating as “indexing failed” isn’t very descriptive.
I’m fully on non beta versions (latest stable jellyfin and latest version of infuse) now as well with the same issue happening if @NC_Bullseye could possibly move this thread out of beta forum purgatory?
Submitted more diagnostics at ZJK0A - also tagging @james (sorry for the notification but this is a pretty frustrating one to run into sitting down on a Friday after work to relax with a show and having the bug retrigger)
Swiftfin is working totally fine throughout this time as well so looks to be on the infuse end only from what I can see.
Looks like this time my “fix” with restarting the server isn’t doing anything unfortunately.
Spent some more time resting with a totally fresh jellyfin install run on a vm with a restored backup and discovered the following:
Native jellyfin clients on various works fine, swiftfin works fine and so does the web interface.
I can play content through infuse browsing to the jellyfin share even as indexing fails (and seeing all the correct files etc)
I’m fairly confident the server itself is fine and something is going wrong with the indexing process on the infuse side. Any insights into a solution would be very welcome before I start setting up wireshark to see if I can pick out any further info.
More digging - it’s only certain shows in the library - if I navigate to them directly I get “unexpected server response” in infuse but fine everywhere else. Can’t see any difference in the files there vs any of the other shows though, they’re all just mkvs with standard file names and nothing weird going on.
Managed to fix my setup once more - for every show I observed an “unexpected server error” for when I tried to browse to the folder directly or do a speed test against from the Shares menu I moved them all out of my Library, rescanned and force recreated the jellyfin docker container which allowed infuse to finally index successfully.
Then I added those shows back in and rescanned, force recreated etc (regular restart wasn’t enough) which also allowed them to sync. Still no idea what caused infuse to dislike the shows but at least we’re back in business for now.
Hopefully this will help some other folks fix similar issues until we can find a permanent resolution.
Still experiencing this on and off, I have a workaround as mentioned above but even improvements to error reporting on the indexing (skipping a show/folder if it has problems and giving me a list of problem shows/folders while indexing the rest of the shows) would save a huge amount of time even if there’s no easy underlying fix to be done.
I’m guessing jellyfin support is a niche case and smaller amount of users vs plex or similar so I do understand it’s not a super high priority but it is still fairly frustrating to deal with. Even just some better error logging so I can solve the problem on the jellyfin side if possible would be appreciated as right now I’m still working with a black box on the infuse side.