Hi, I’m having a weird issue, I’m connecting infuse to my plex server in library mode. One of my libraries (the TV one) is a large library. If I’m connected to WI-FI I get indexing failed issue. But if I connect my Apple TV to my iPhone phone hotspot it instantly indexes and all goes well. - tested this with infuse on 2 Apple TVs iPad and iPhone all the same, if I’m connected to the WiFi(same network as plex server), won’t index, if I’m connected to 5G, will easily work.
I’m on all devices with the version 8.2.3 version, I’m a Pro user, and I would not like to use the direct mode as I lose the nice categories I enjoy from infuse.
I previously added this as a reply to the new update, I’m moving my question here as I think is the correct place for it.
I’ve tried changing many of the network settings from plex to no avail, the only thing that seems to make it work is to not be on the same network (which is crazy, as I think would actually make things easier) anyone has any suggestion?
One more info I forgot, indexing works on same network for a smaller library, so I’m assuming is not an issue of reaching plex, but maybe a timeout situation. Also no issues streaming.
Now that I have all episodes already accounted for, I don’t see difference as nothing new was added, but still, on same network gives the same error as before where episodes wouldn’t be listed, and on 5g no error, same as when I managed to actually index things
192.168.68.102 is the correct ip address of the server, and is a reserved ip
Local Network access is enabled on the phone, also when I play a video on plex dashboard I see it going through local network, and if it’s only the movie library enabled it does index
I’ve already attempted restarting the server, removing and trying adding plex connection again on infuse, to no avail.
And this is happening on multiple devices 2 Apple TV, iPad and iPhone (was just easier to test from iPhone)
We’ve seen a few cases where some dual-band routers will have connection issues on certain bands. EG Connections work over 2.4 GHz but not 5 GHz (or vice versa).
Are you able to test with Ethernet or possibly look at creating separate networks for each network band to see if one works over the other?
Also, if this happens to be a guest Wi-Fi network then many routers will prevent communication to certain devices.
@james one thing it happens in plex logs when it fails is CERT: incomplete TLS handshake from [::ffff:192.168.68.87]:53654: stream truncated - again this only happens on local network, I’ve tried a bunch of changes on my network, router, nas and plex nothings seems to fix this
IPv6 doesn’t seem to be the issue, disabled both on NAS & Plex, get the same error for the IPv4 - I’ve also cleaned up the authenticated (again as had it done due to plex security issue), and re-auth infuse +_+
CERT: incomplete TLS handshake from 192.168.68.87:54053: stream truncated
@james bringing more information, I’ve activated my guest network, that doesn’t change the submask, mainly SSID - indexing worked for like once in each device, then stopped working again with same error. - any possibility plex blocks it in some way after large requests? - which wouldn’t happen on mobile network as is always a different identifier?