Hi, same big issue on TV Apps with nVidia SHield TV Pro
I am using since years the Plex Apps on two TVs LG & Samsung , with PMS on Nvidia Shield TV Pro.
Since 1 week I’m getting error message “Http request failed: bla bla plex.direct:32400/library/metadata bla bla” “status: Network Error”
After error appeared, I upgraded NVidia Shield to latest version today (it upgraded the PMS also version 1.41.7.9823smb). No change, same errors.
Connection is wired.
When using locally Shield Plex App or Windows Plew app.plex.tv, runs perfect.
But is crashing systematically with TV Plex App, errors mentioned above.
Additionally, Nvidia Shield stops completely.
Settings on the TV App:
forced direct read is disabled (when enabled, I get same error messages with recommendation “disable forced direct read”)
I never use the plex.direct part when accessing a server. It is unreliable.
It is dynamic by design.
It will change EVERY time your certificate updates
( That long number sequence in the name is the certificate Id – which changes every 30 days )
If you want a FQDN to access the server then get one from the internet and ATTACH it to your PMS server. ( that’s what I do – as do the rest of us with FQDNs)
For me I did not configure the app/server to be accessed in this way - this is how it was working out of the box with Plex Pass + (unintentional) remote access.
I’m having the same issue on my iPad. Client Version 2025.17.0 (1082). Server Version 1.41.8.9834 in Docker on Unraid. I was initially dealing with Inflate-gate and ran ChuckPA’s script to deal with that. Was afraid this may have been a consequence in some way but perhaps not… I haven’t heard complaints from other family, not too many use iOS.
Digging more around in my logs I see this: 06/09/2025 19:40:40:095 [Praeceps5iy3qsab9bp3l9ej1mqx7cvr] DEBUG [QueryClientProvider] network state changed to OFFLINE
Shortly before
ERROR [MediaDecisionEngine] Error refreshing decision. {
"type": "[object Error]",
"stack": "Error: Http request failed: https://192-168-0-3.fef14e1511c84ce18dd67229c7fd430f.plex.direct:32400/library/metadata/2855?checkFiles=1&includeChapters=1&includeMarkers=1, status: Network Error\n at construct (native)\n at apply (native)\n at _construct (address at /private/var/containers/Bundle/Application/4DF83FA3-FD1C-43C3-A57A-F5D2B2563D61/Plex.app/main.jsbundle:1:429686)\n at Wrapper (address at /private/var/containers/Bundle/Application/4DF83FA3-FD1C-43C3-A57A-F5D2B2563D61/Plex.app/main.jsbundle:1:429330)\n at construct (native)\n at _callSuper (address at /private/var/containers/Bundle/Application/4DF83FA3-FD1C-43C3-A57A-F5D2B2563D61/Plex.app/main.jsbundle:1:4472066)\n at HttpError (address at /private/var/containers/Bundle/Application/4DF83FA3-FD1C-43C3-A57A-F5D2B2563D61/Plex.app/main.jsbundle:1:4474500)\n at _reportResult (address at /private/var/containers/Bundle/Application/4DF83FA3-FD1C-43C3-A57A-F5D2B2563D61/Plex.app/main.jsbundle:1:4477035)\n at ?anon_0...",
"name": "Error",
"message": "Http request failed: https://192-168-0-3.fef14e1511c84ce18dd67229c7fd430f.plex.direct:32400/library/metadata/2855?checkFiles=1&includeChapters=1&includeMarkers=1, status: Network Error"
}
Which triggers the on screen error. I have Ubiquti networking system which doesn’t report any network drops at that time.
Do you have multiple access points? I just did a test while at work today and I experienced the no base uri timeout whenever my device associated to a new access point while walking from one section the office to another. Have the latest plex update(2025.18.0) that has some network related fixes but this issue still persists.
With the disconnection from my home network to cellular or wireless roaming while at the office I have two repeatable methods of recreating this issue.
Am I correct in assuming that the described error occurs exclusively on the new mobile apps?
If so, then it’s very likely that this is neither a server nor a remote access issue and the topic should be moved and re-tagged.
I’m still having this error periodically, and yes, it only happens with the mobile app. Could we move/re-tag and continue diagnosing the issue so the app big can be fixed?
I was able to recreate this issue today at my office. Created a Linux machine(Ubuntu) with Plex running in Docker (plexinc/pms-docker) directly connected to the internet with one of our static IPs through our secondary internet provider. Ran ufw allow 32400 and set up remote access. Began playback through our primary internet provider over wireless, and walked out of the building to a distance where Wi-Fi disconnected, playback would go black, followed by the no base URI after the timeout period (30 seconds) had elapsed.
Also having this HTTP issue with the Plex app on iOS - it has been an issue for every single video in the app since the New Plex Experience launched, so the app is currently unusable.
I also have had this problem for a while. I don’t know how long but around 2- 3 months.
And as for everyone else its an irritating bug, since it worked great before.
My setup is no special, Plex installed on a Windows machine streaming to an Android device. I update every time there are an update, so I should not be way behind on version.
Please let me know if there is anything I can do to make this bug, yes I call it a bug, since it appear, as I said 2- 3 months ago.
PS. I did see someone mentioned that they had UniFi system, so do I, if that is something to go on!?!
This bug makes the app completely unusable for me on my android phone. It works just fine on my TVs, so it’s just this new experience that’s broken. My server is running on windows and up to date as well as my android app is up to date as well
Thanks for the advice, but I’m honestly not even sure what you think we should check. Which local network configurations and settings are you talking about? It’s not that we can’t access it from the android app, it’s that it’s too buggy to use and enjoy our content with.
I meant for you to check ALL network settings on ALL devices and review your configuration in general.
And remember, your network is your responsibility, Plex has no control over the settings or configuration of your network.
Also make sure your files have been fully analysed. Sometimes, during maintenance, a file may lose it’s analysis data, especially if you have large libraries and that can cause playback issues.
And for what it’s worth, I have no issues with my Win11 PC PMS v1.42.0.9975, DS1815+ PMS v1.42.0.9975 or DS1813+ PMS v1.42.0.9975 serving my Samsung A16 5G - Android 15 - Plex App 2025.20.0 and two FireTV 4K Max sticks.
I also use an NBN supplied Cable Modem and an Optus supplied Sagemcom F@st3864AC router connected to a Cisco SG200-08 managed switch and other sundry devices.
Also, play something on your Android device and when it fails, grab your server and app logs and post them here. That may help to narrow down the issue/s you are having.
I have only seen a few reports of this occurring on Android on Reddit. For the most part, this issue is related to the iOS version of the app.
There is an issue with the media decision engine timing out when recovering from a network interruption. Pretty hard to dispute it being an issue on our end when this issue was nonexistent before the “New Experience”. Also, setting up a test Plex server on a system connected directly to the internet using a dedicated business fiber, and being able to recreate the issue by simply turning off Wi-Fi and connecting to cellular, regardless of the remote network I’m using to connect (Home, Starlink, Business primary circuit).
