Pause/Resume on Hosting Desktop hangs with spinning indicator without really resuming

Plex Media Server
,
1

Server Version#: 1.26.2.5797
Player Version#: servers player for 1.26.2.5797

Hey guys,

I’m have a issue where on my hosting windows Plex Media server, I start up Chrome, hit the 127.0.0.1 url, login start watching a move/video (doesn’t matter what), then I hit Pause and after some time, not sure how long, say longer than a few minutes, I go to click resume and it’ll play the next 30 seconds or so then hang with spinning indicator like it’s trying to catch up with it self but never does. The external drive never even acts like it kicks back in to resume, no disk activity. I have to close chrome to straighten it out. This has happened on several version s of chrome and several versions of Plex Media Server. I am in the process of trying to figure out the logs but I need to narrow down the the time frame so I can better see the logs for that issue… I will post back what I find… But in the mean time I was wondering anyone had any suggestions on what this issue be…?? Please note that the storage drive for my movies are on a External usb 3.0 6TB WD HDD. I don’t remember having issues like with “some of the earlier versions” of Plex Media Server. But can’t pinpoint when this started other than maybe within the last 3 versions of Plex Media Server. So just a procedural recap:

  1. Open Chrome to local host login 127.0.0.1…
  2. Play any movie or video
  3. Pause for ‘a little while’ say 5+ minutes for instance
  4. Try to resume movie/video
  5. Movie/video will play for the next 15+ secs then hang with spinning indicator without ever resuming.

Quick Update: here is what I see for errors in log, I have masked IP for security reasons:
May 26, 2022 15:53:57.662 [15644] ERROR - XML: Entity: line 1:
May 26, 2022 15:53:57.662 [15644] ERROR - XML: parser
May 26, 2022 15:53:57.662 [15644] ERROR - XML: error :
May 26, 2022 15:53:57.662 [15644] ERROR - XML: Start tag expected, ‘<’ not found
May 26, 2022 15:53:57.662 [15644] ERROR - XML: status=ok
May 26, 2022 15:53:57.662 [15644] ERROR - XML: ^
May 26, 2022 15:53:57.662 [15644] ERROR - Error parsing content.
May 26, 2022 15:53:57.662 [15644] ERROR - Error parsing XML: Error parsing file.
May 26, 2022 15:53:57.662 [15644] ERROR - SSDP: Error parsing device schema for http://192.168.X.X:9080

I have about a 4 minute swath of log information i can share that shows DEBUG, WARN and the ERRORs. I will share as needed. I just need a developer to tell me where to upload it at. these 4 minutes appears to have a set of repeating information throughout the 4 minutes.

2

So this only happens with bundled web app? Does it happen with app.plex.tv or any other Plex player?

3

Sorry for the delay, lots of graduations happening. Hehehe.

If I’m not mistaken, i have seen this with firestick as well. I will check firestick and Roku Plex app in the next day or 2 and report back. Not sure about app.plex.tv. My assumption is it will do the same since this appears to be a server side error. But again I’ll figure that out 100% for sure in the next 24+ hours.

4

so I just check my android phone plex app, that one did not hang after resuming play from a 15 minute pause. I do still see the error in the log though, just didn’t affect my phone play/pause/resume. I’ll check the others later today.

5

that error is just the server detecting a device that is announcing itself on the network vis SSPD and not being able to figure out what it is because it cannot read the devices XML. The server looks for things like DVR tuners on the network via SSPD.

6

LOL, no offense but what you just stated was ‘greek’ to me as I’m not familiar with how the app works in detecting devices on the network ‘persay’. BUT on another note, I have been trying to reproduce this issue within a Roku TV, 2 Firesticks and could not reproduce it. I then came back to my server desktop and tried to recreate on the desktop that had the issue to begin with, guess what I cannot recreate it now :frowning: SO NOW, I’m down to disregarding this request for help until I be to consistently get the issue again so I can further troubleshoot it. So sorry the chasing a ghost rabbit down a ghost hole. heheeheheh

7

I just meant the error has nothing to do with your issue. That error is the server seeing a device on your network and not being able to figure out what it is