Plex getting stuck with infinite buffering during playback

Plex Media Server Desktops & Laptops
, ,
1

Server Version#: 1.23.6.4881

I’m having an issue where every now and then while I’m streaming Plex it will stop and start buffering and hang there forever. If I’m using Chromecast with Google TV (whether casted or through the native app), I’ll have to totally restart the Chromecast to fix it. It also happens when playing back through the web app but there I can back out and restart playback and it’s fine.

This seems to usually happen in the last half to last third of the runtime of the media file. For some TV shows it seems to happen within the last 30 seconds

I run Plex through a Docker on a Open Media Vault Linux media server.
I’ve had this issue for a few months now probably. Any help is appreciated.

Here are my logs, the most recent issue happened around 6pm 7/31:
Plex Media Server Logs_2021-07-31_18-39-59.zip (3.8 MB)

2

Hit another instance of this. Here’s the logs:
Plex Media Server.3.log (10.0 MB)
The issue happened around 8/2 10:39pm

I noticed in the logs around that time this is repeated a few times:

DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.1.226:9080
DEBUG - HTTP requesting GET http://192.168.1.226:9080
DEBUG - HTTP/1.1 (0.1s) 200 response from GET http://192.168.1.226:9080
ERROR - XML: Entity: line 1: 
ERROR - XML: parser 
ERROR - XML: error : 
ERROR - XML: Start tag expected, '<' not found 
ERROR - XML: status=ok 
ERROR - XML: ^ 
ERROR - Error parsing content.
ERROR - Error parsing XML: Error parsing file.
ERROR - SSDP: Error parsing device schema for http://192.168.1.226:9080
DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.236844 seconds: 192.168.1.211 (Chrome Raptor)
DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.1.211:8008/ssdp/device-desc.xml
DEBUG - HTTP requesting GET http://192.168.1.211:8008/ssdp/device-desc.xml
DEBUG - HTTP/1.1 (0.0s) 200 response from GET http://192.168.1.211:8008/ssdp/device-desc.xml
DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://192.168.1.211:8008/ssdp/device-desc.xml
DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.211 (Chrome Raptor)
DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.1.226:9080
DEBUG - HTTP requesting GET http://192.168.1.226:9080
DEBUG - HTTP/1.1 (0.0s) 200 response from GET http://192.168.1.226:9080
ERROR - XML: Entity: line 1: 
ERROR - XML: parser 
ERROR - XML: error : 
ERROR - XML: Start tag expected, '<' not found 
ERROR - XML: status=ok 
ERROR - XML: ^ 
ERROR - Error parsing content.
ERROR - Error parsing XML: Error parsing file.
ERROR - SSDP: Error parsing device schema for http://192.168.1.226:9080
3

Had plex infinite buffer yet again. Was playing back on chromecast so I caught the chromecast logs this time. Here they are, I attached them along with the server log. The problem happened somewhere around 22:05-22:15 in the logs
logs.zip (828.5 KB)

Looks like it might be something with transcoding?

4

Bump. Can anyone help with this?

5

Is there a more official way to submit a support ticket?

6

Sometimes my Roku client will lose connection to the Plex server while watching Live TV and it will sit there buffering for a few minutes before dying. I’m also using podman on CentOS. Seems similar to what you’re saying.

7

This happened yet again, here are the logs. Occurred somewhere around 12:30-12:50pm 9/1 in the logs
logs.zip (718.4 KB)
Any way to tag plex support in these posts?

8

Had the hang again. I was playing through plex web player in chrome this time. I had direct play and direct stream disabled so I guess those can be ruled out.

9

Having a similar issue with my Google TV too. Always have to back out and replay the file. Occurs roughly 10-20 min of start of playback, so maybe a transcode buffer issue? I’m playing it off-site.

10

I figured it out for my situation. I have an USB C hub connected with an Ethernet connection. I just unplugged the Ethernet and it works without infinite buffering. Seems like the connection is getting dropped for some reason if you’re using Ethernet, which is pretty weird. I have it connected to make streaming games work, but seems like this is my workaround for Plex.

11

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