IOS and AppleTV apps not working correctly

Server Version#: 1.30.2.6563-3d4dc0cce
Player Version#: 8.14

IOS app outside of firewall saying not enough data for transfer, keeps saying need XYZ Kbs and only ABC avaialble.

This would be fine, but form the same network I am able to play the same exact video using a computer and the plex app on Mac. Also able to play the same video on iPad via the Safari, Chrome, Firefox browsers from the same external network (was in hotel).

So this to me looks like not an issue with the server or the data but an issue with the IOS app handling the data. This was tried on iPad Pro with app, and on phone with the same exact results.

Also on Apple TV inside the house, the same problem is exhibited over a wireless network where I know there is enough data to handle the connection. Turning on VLC on apple TV was able to stream the same exact movie just fine.

Can you verify if Plex considers those streams to be local or remote? You should be able to see that in the server dashboard (now playing).

If your stream is treated as remote, the server might apply additional bandwidth limitations

Unfortunate was not able to be remote until now where I know bandwidth and can check.

Remote location 50 mbps , home location 1 Gbps (around 700 mbs checked bandwidth by directional).

Since I am getting this message nothing is playing in dashboard.

But through browser I am getting everything playing just fine. Remote @. 6 mbps with direct play.

Both are from same location, same file at exactly the same time.

The server version has changed of course.
Now on Version 1.31.1.6782 , and will hold off bumping to troubleshoot.
Server is running in docker.

Any restrictions set in the client app (e.g. quality > remote streaming) or the server (e.g. settings > remote access > internet upload bandwidth or per-stream restriction)? Though if it’s working fine using the browser there’s a chance this is a client option.

Thank you.

Looks like restrictions on the sound end in client. Will do some more testing later on. But looks like it works.