Http request failed

Server Version#:DSM 8.2.2-72806 Update 3
Player Version#:1.41.6.9685

Hi all. I hope someone has an idea how to fix my issue. Since around a week, when I stream something from my plex server from my iPhone (it might also happen if streamed with other Software, can’t really try) I am received this error regularly: Http request failed: /liblary/metadata “bla bla” includeChapters “bla bla” status: HomeServer has no basi uri: status notConnected.

I am using my plex server sinse a long time, never had any issues. Still the same internetprovider and they are not faving issues. I also tried to restart my router, nothing changed. Id doesn’t matter what I stream, the errer will occure sooner or later…

Thanks in advance for any ideas on what I could try.

6 Likes

I am experiencing the exact same issue, I created a support post in the Discord server here: Discord

Is your server set to Secure Connections Required?

If not, seeing your Syno’s DEBUG log files (from PMS) , the ZIP file, capturing you attempting to connect, will be of great help.

Most of these are simple fixes

It was not, would setting it to that maybe help?

What are Syno’s DEBUG log files and where can I find them? Do I need to enable verbose logs in the General server settings as well?

1 Like

There is a significant emphasis in these later releases (PMS and Apps) for EVERYTHING to be HTTPS.

This is why I asked if you had it set to Required – but perhaps the the request you’re making can only be HTTP (unencrypted) ?

As for Verbose logging – That is of no help here.
Verbose shows us every single packet of data.

This issue is at the level before we get packets (it cannot connect)

Well I had it set to “Preferred” before, I have yet to test after switching to “Required”. If it persist I will check the server logs for any indicators.

I only connect to my server from within my internal network so it to being HTTPS was less of a concern for me, but if the new app needs it to be that then it would probably be nice to have this noted somewhere, ideally in the serverside settings.

when you connect to it locally, do you use a hostname/domain name or do you use only the LAN IP address ?

I don’t really connect to it manually through the app, I’ve just connected my server to my account when I set it up and now log in to my account to access it, I am on the same network as my server.

Switching to “Required” for HTTPS did not solve it either.

To restate the issue, the app keeps disconnecting when browsing around and the player keeps resetting to the start and occasionally shows the error message described in the original post. These things happen constantly (as in every 15 seconds or so).

The linked Discord support post has many more people who experience this as well.

This issue has been going on for a long time now and needs to be fixed asap, this really is outrageous.

I’m running into this same HTTP Request Failed issue. I’ve been trying to diagnose with what I’ve read online and with Gemini assisting (I know, but I don’t know what else to do)

Has anyone been able to fix this? Or are is this a Plex issue we need a big fix for?

One of my users sent me a message today as they’ve started getting this error also. It happened after updating to the new Plex iOS app. The error stated:

Http request failed: /library/metadata/60601?checkFiles=1&includeChapters=1&includeMarkers=1, status: [FRIENDLY SERVER NAME] has no base uri, status: notConnected

This user is accessing the server from outside the server’s home network. I tried to replicate myself with no success. I had the user set Local/Wi-Fi/Cellular streaming qualities to Maximum, no difference; ensured Direct Play and Direct Stream were both on, no difference. Although monitoring the streams when I tried to replicate, I can my user was still being transcoded, possibly incorrectly, from h264 1080p to h264 1080p; the same media will direct play for me. I’ll see if I can do some additional troubleshooting with the user and update. If there are specific logs I should be capturing, please let me know.

Just for the record, I am also having this error with an Android player and a macOS server, both on the latest versions as of this date 2025 May 20.

It seems like the beta app from TestFlight has fixed this? I haven’t had the issue after installing the beta one on iOS: Join the Plex: Watch Live TV and Movies beta - TestFlight - Apple

Edit: Lol nevermind still happening. Maybe less frequently.

Any update on this?

1 Like

Hello @ChuckPa,

Could you forward this issue to someone who can potentially fix this? Plex has been basically unusable as my main client does not work at all. This has to be fixed asap.

1 Like

One of your users ?
Should I be looking for a server under a different account than where the forum connects to ?

Which “FRIENDLY SERVER NAME” (if it’s not too personally identifying)?
( we can discuss in PM if you prefer )

@Celarye

I’ll gladly get this written and forwarded once we can figure out what’s happening.

I’m stating to suspect the apps aren’t handling the case where a pinned library no longer exists and now points to either a non-existent server or section ID

EDIT: May I see a DEBUG server logs or app logs which capture this?

Getting reports of the same issue here on the iOS app. Apparently the movie was playing fine for 30 minutes, they stopped playback and closed the app for a break. Re-opened the app and tried to resume and got this message every time they tried to resume.
Other media was playing fine, they just couldn’t resume their playback.
I confirmed at the time that I was able to watch the media without issues on my PC.

Using secure required, custom domain + cert. Standard port forwarding. Has been working without issues for years.

I got this error today - as well as my partner experiencing it recently.

Appears to be a relay issue (not that I was even aware I was using relay - debugging that now).

2025/05/29 20:58:14.880 (1120101) 🔧 (private) | Setting default whitelist 'http,https,tls,rtp,tcp,udp,crypto,httpproxy'
2025/05/29 20:58:14.881 (1120101) ❌ (private) | Failed to resolve hostname 88-80-190-127.fef14e1511c84ce18dd67229c7fd430f.plex.direct: nodename nor servname provided, or not known
2025/05/29 20:58:14.881 (1104851) ⚠️ (private) | shutdown
2025/05/29 20:58:14.881 (1120101) ⚠️ (private) | 清空formatCtx
2025/05/29 20:58:14.881 (1120608) ⚠️ (private) | 清空formatCtx
2025/05/29 20:58:14.919 (1104872) 🔧 (private) | ct_type:0 pic_struct:0
2025/05/29 20:58:14.919 (1104872) ⚠️ (private) | 清空formatCtx
2025/05/29 20:58:14.919 (1104872) 📝 (private) | Statistics: 20907641 bytes read, 0 seeks
2025/05/29 20:58:14.919 (1104872) 📝 (private) | Statistics: 88440105 bytes read, 0 seeks
2025/05/29 20:58:14.919 (1104872) 📝 (private) | Statistics: 10853 bytes read, 0 seeks
2025/05/29 20:58:14.919 (1104872) 📝 (private) | Statistics: 158 bytes read, 0 seeks
2025/05/29 20:59:03.652 (1120188) ➖ (private) | selectTrack 1
2025/05/29 20:59:03.652 (1120188) ➖ (private) | selectTrack not loaded 1
2025/05/29 20:59:03.665 (1119878) ➖ (private) | selectTrack 1
2025/05/29 20:59:03.665 (1119878) ➖ (private) | selectTrack not loaded 1

Have full app/server logs from the event - happy to share more privately.

I have custom access URLs in place I get the no base uri message followed by a second error that plex is unable to access via the *.plex.direct:324000 whenever I disconnect from my home Wi-Fi. Remote access on port 32400 is not configured, remote clients connect using custom URLs.
plex_iOS_Logs.txt (1015.0 KB)

If you will give me a bit with this , I’ll setup a custom URL again to test the new apps with

In the past, the old apps worked ok.
Looking at the logs provided, plus my own logs, leaves me somewhat confused.

As soon as I help a few more folks today with the exploded DB problem, I’ll come back to this. (their machines are hard-down status)