Play back crashes with “No base uri status notConnect”

Plex Players Mobile Devices
1

Server Version#: 1.41.6.9685
Player Version#: 2025.15

iOS version: 18.4.1, iPhone 15 pro Max

Will be watching something when all of a sudden the show/movie stops with a black screen error, and at the end of it stating “(server name) has no base uri, status: notConnected”. Most of the time the error auto closes quickly and starts to play again, but the show starts from the beginning, no matter where you were up to. The device is on the local wireless network the whole time with no other connectivity issues.

This issue can occur every few seconds, or only a couple times and does not have issues afterwards.

I do use an NGINX reverse proxy with websockets allowed and https forced on, with the same cert and key used in NGINX and Plex. Caching is disabled.

This exact same setup worked flawlessly for years. It shouldn’t matter, but remote access is disabled in Plex as I use WireGuard when away from home (which is not applicable in this scenario, just an FYI).
log-2025-05-17T18_31_35.195Z.zip (1.3 MB)

IMG_4180
IMG_41801041×480 21.3 KB

2

Same thing here:

Version 1.41.7.9823

In this case I use the official Plex helm chart for running in Kubernetes. With a NGINX reverse proxy and 32400 is port forwarded to plex. It is therefore accessible from the outside as well.

image

The error:

image
image1042×480 24.9 KB

Thanks

3

Yeah ive got people reporting this issue on the plex iOS app.
I dont use a proxy, im a lifetime pass with the built in server remote access enabled + port forwarding. I do use a custom domain + certificate with SSL required enabled.
Has been working perfectly for years, first time ive ever seen this issue since the new plex app update.

4

Same here

5

I have the same issue with the iOS app running behind Caddy proxy.

7

Having this problem constantly throughout a movie or even multiple times in an episode of a show. Using an iPad. It’s incredibly grating.

8

Same here.
No proxy, nothing fancy. Since the big app remake in March.

9

I get this error whenever my connection switches from wifi to cell data or from cell data to WiFi on iOS.

10

I too am experiencing this issue using the iOS Plex app. I rely on NGINX as my reverse proxy. Though, I still experience this problem on my local network bypassing NGINX.

11

This app is just unusable until it gets fixed. I get constant crashing throughout 1 30 minute episode, often resetting to the beginning of the show (or movie)

12

Same here.
No proxy, nothing fancy. Since the big app remake in March. remote or local doesn’t matter

13

Same issue and has gotten progressively worse with each release since the new experience update. It would be really nice if I could just revert to an old release.

14

Hey there,

This is a frustrating issue, especially since your setup has worked flawlessly for years. The error message has no base uri, status: notConnected typically points to intermittent communication issues between the iOS app and your Plex server—often linked to how the reverse proxy handles persistent connections.

A few things worth checking:

  1. NGINX Configuration – Even if it hasn’t changed, iOS/Plex app updates might now handle base URIs differently. Make sure your reverse proxy config includes:

nginx

CopyEdit

proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
  1. Plex Secure Connections Setting – Try toggling the “Secure connections” option in Plex (Preferred, Required, or Disabled) and test each. Some users reported better stability with Preferred behind NGINX.
  2. iOS Background App Refresh & Local Network Permissions – Double-check that Plex has full local network permissions and that background refresh is on.
  3. Test Without NGINX – If possible, test a direct local connection by temporarily bypassing NGINX. If the issue disappears, it likely confirms a reverse proxy issue.

Lastly, check Plex server logs around the time the disconnection happens. Look for any websocket failures or base URI errors for more clues.

Hope this helps troubleshoot the hiccup!

15

That looks like it come out of ChatGPT, but anyways.

Point 1 and Point 4, confirmed NGINX is configured correctly, and after continuing to see the error, tried bypassing it in case it was that (even though there are people in this thread that are not using it having the same issue).

Point 2, tried this already as this has proven varying levels of success from different apps, particularly on TVs (looking at you Hisense!). No change.

Point 3, looked, all fine, tried resetting them, no change.

16

One thing I have noticed is that this issue appears to occur for me, when my device is roaming between APs within the house.

There is a spot where I use the phone frequently that can roam between 2 APs, but if I use a spot where it wont roam then it seems to be ok.
When it does roam, it technically would mean there is around 30ms where traffic would be paused/dropped (these roam events take 5-10ms to complete, plus allowing for ARP table updates on the switch), but the app should not be seeing that level of an issue, especially considering cellular networks can cause latency like this all the time.

This makes me think that the way the IOS app is handling wireless roaming events, either due to how IOS is reporting it to the app or because they have configured it in such a way, is that its handling these roaming events more like an disconnect and reconnect event, and the app then causes an immediate “not connected” event to be fired which then throws the error reported.

Note: my wireless network has not changed, nor does any other app have any issues, this has only occured “since the big update”. I maintain 67-70db RSSI at worst around my house, with 24db SNR at worst as well. Real time apps like Teams, Webex. Zoom etc never have any perceived loss when I roam across APs, so if realtime streaming has no noticeable impact, Plex definitely should not.

It seems to me there is something different in the behaviour in the new app, because it doesn’t even play the content that’s stored in the buffer when this occurs, nor does it remember where you were up to, it just immediately stops with the error, and then restarts whatever is playing, from the beginning. By not finishing what is in the buffer, tells me something is interrupting the app and stopping it unexpectedly.

17

I have also had the same problem. My config is pretty simple with no NGINX. The only way I’ve found to get the app to work on IOS is by connected to a VPN. After that the error never presents itself. Not sure what they changed in the update but it definitely makes the app unusable if you don’t have a VPN set up.

18

I really think you’re onto something here. I haven’t run extensive testing with location of my iPad but I definitely do roaming between 2 APs. And sometimes it seems stable, perhaps when I’m not being pulled from one to the other. I’ll have to do more testing at home but I feel like I was having that issue also and I don’t have to APs there.

19

Just curious if you’re VPNing into your local system where your server is or are you talking about a VPN in general?

20

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.