I have Infuse Pro 8.3.1 (5414) and Jellyfin 10.11.2 with a library mode share, I can’t complete the synchronization in any way.
i had this problem and it was my infuse sync jellyfin plugin wasn’t updating. Apologies if that’s not helpful but just figured I would put that out there.
I still have this issue. Can anyone help me?
I’m a paying user, and after almost 11 days I still haven’t received support.
I just updated to Infuse Pro 8.3.2 (5433), and nothing has changed by the way.
Can you check the version of InfuseSync that is installed on your server?
The latest version is 1.5.2 and details on installing and updating InfuseSync can be found in this guide.
I have version 1.5.2.0
If you’re able to send in a quick report from your device we can look further into what may be going on here.
Note: You may also try updating to Jellyfin 10.11.3 if you haven’t already.
I have Infuse Pro 8.3.2 (5433)
I have InfuseSync 1.5.2.0
I have Jellyfin 10.11.3
Everything is updated to the latest version.
My log code is Y4MPD
1 Like
Any update?
I pay a subscription, but the app hasn’t been working for almost 20 days and I can’t use it…
Still, after 20 days, I am unable to use my Infuse…
I updated to Infuse Pro 8.3.3 (5449), I still have the same issue.
@james Months later, this issues still hasn’t been fixed. I haven’t been able to use my paid subscription for months. My subscription will expire in February. I won’t be renewing it 
Sorry for the trouble, we have been working to investigate a few of the more rare conneciton issues like this.
There were a number of improvements for the Jellyfin login flow added in the recently released 8.3.6 update, so if you haven’t yet updated you may give that a try.
There are also a few more improvements coming in the next update (8.3.7) which could help resolve a few issues in this area as well.
I’m having similar issue. I’ve had a flat file share working for years and have been trying Jellyfin the last month. Just tried the Mac version and it grabbed all the file share data, but got “Indexing failed for Jellyfin”
Currently running:
- Jellyfin 10.11.6
- InfuseSync 1.5.2.0
- Infuse 8.3.6 on Mac OS 15.7.3 (24G419)
EDIT: Should have mentioned that the Jellyfin content loads perfectly on my AppleTV. All data is coming from a Synology box offsite.
A few more improvements for connecting to Emby and Jellyfin servers are available in today’s 8.3.7 update.
Please let us know if you continue to see any issues here.
@james I am having the indexing failed error on Infuse 8.3.9 using a newly rebuilt from ground up jellyfin server 10.11.6 and infuse sync 1.5.2.
I had a hard drive failure in my desktop followed by time machine corruption on my backup so did an entire reinstall of mac os and all applications, etc. I figured it was a good time to upgrade from jellyfin 10.9 and infuse sync 1.5.0.
I got the new jellyfin server all set up and reorganized and added it to infuse on my appletv. It has had the index failed error multiple times now and I have deleted and re-added it multiple times.
I just re-added it a fourth time and the indexing worked fine for a while before failing after around 10 minutes.
It fetched content for all the films and a good portion (maybe 2/3)of the television before failure around halfway though a folder of 11,000 episodes. My library now shows zero movies, zero tv episodes and zero other.
Error Reporting Code: J610R
Figured I would try on an old iPad and getting same error but much sooner. AQFQR
Both sets of logs seem to indicate Infuse is timing out when attempting to connect to the local server located at: xxx.xxx.xxx.14
This may indicate an issue with the network, a change in the server address, or perhaps some other configuration issue with the server itself.
The first thing I would check is to see if the current server address matches the address which has been saved in Infuse. If it has changed, you can remove the currently saved Jellyfin share from Infuse and re-add it with the updated details.
@james Okay thanks perhaps it is something to do with my PIA VPN settings that I had on to set up again, though the fact that it is connecting and getting so far into the indexing before failing makes me question whether it is a network issue. Perhaps the mac mini is just hanging with some other process causing jelkyfin to become non-responsive. If that is the case, it may be time for an upgrade; it is an early 2018 mac mini.
If there is a VPN active on the Mac you may need to look for an option that allows local network traffic to bypass the VPN.
This is what the setting looks like in NordVPN and I presume other VPN services have something similar.
Thanks yes I have split tunneling set up so the IP address for the AppleTV and iPad both bypass the vpn.
Looks like it just needed time overnight, as by time I got home today my library was full and everything was working as expected again. Appreciate your swift input as always!
1 Like