Constant buffering/failing in Plex app on Android TV-based devices after upgrading Synology DS218+ to DSM 7.0

Server Version#: 1.22.1.4228
Player Version#:

Hi, I recently upgraded my DS218+ to DSM7.0 Beta and downloaded the most recent PMS, 1.22.1.4228 for DSM7. Up until this upgrade, I was able to use the Plex app on my various Android TV/Firestick devices without issues. In fact, I have a VPN tunnel back to my house and was able to stream using the Plex App/VPN while staying across the country, all without issue.

Now, when I attempt to use the Plex app, I get constant buffering, and sometimes eventual failure. The constant in the logs, from PSM side, is this:

[0x7f3f7efd1700] Debug — Failed to stream media, client probably disconnected after 1474560 bytes: 104 - Connection reset by peer

On the Android side, the constant is:

03-29 23:11:44.241 i: [FFmpeg] [INFO] [Cache] Seeking by reading ahead and waiting for new data.
03-29 23:11:44.319 i: [FFmpeg] [INFO] [Cache] Seeked to 662599862 bytes via read ahead cache.
03-29 23:11:44.330 i: [FFmpeg] [INFO] [Cache] Source seek requested to 679593516 bytes with 0 whence.
03-29 23:11:44.334 i: [FFmpeg] [INFO] [Cache] Seek found to 679593516 bytes.
03-29 23:11:44.650 i: [FFmpeg] [INFO] [Cache] Seek complete to 679593516 bytes.
03-29 23:11:44.669 i: [FFmpeg] [INFO] [Cache] Seek has returned with a response of 679593516.
03-29 23:11:44.768 i: [FFmpeg] [INFO] [Cache] Source seek requested to 662608717 bytes with 0 whence.
03-29 23:11:44.783 i: [FFmpeg] [INFO] [Cache] Seek found to 662608717 bytes.
03-29 23:11:45.015 i: [FFmpeg] [INFO] [Cache] Seek complete to 662608717 bytes.
03-29 23:11:45.017 i: [FFmpeg] [INFO] [Cache] Seek has returned with a response of 662608717.
03-29 23:11:45.018 i: [FFmpeg] [INFO] [Cache] Source seek requested to 680205153 bytes with 0 whence.
03-29 23:11:45.069 i: [FFmpeg] [INFO] [Cache] Seek found to 680205153 bytes.

03-29 23:12:03.681 i: [FFmpeg] [WARN] [Cache] Source or buffer is still interrupted.
03-29 23:12:03.682 i: [FFmpeg] [INFO] [Cache] Thread has been terminated.

If I do this via Chromecast, such as using the app on my phone and cast to my Android TV, it works flawlessly. It also has no issues streaming the exact same stuff on my laptop or desktop.

I’ve tried with enabling/disabling both Direct Play and Direct Stream, as well as Use alternate streaming protocol for video playback. Under Network, I have Enable Relay disabled (based on comments from other threads on here), and I added my local IP subnet to List of IP addresses and networks that are allowed without auth (192.168.50.0/255.255.255.0). Under Quality, I’ve tried everything from 0.2Mbps all the way up to Maximum. I’ve also tried the Automatically adjust quality (Beta). Under Home Streaming I have Use recommended settings checked.

The logs I’m attaching are from last night when it failed continuously with the app, and had successful streams with casting via Chromecast.

Any advice would be greatly appreciated!

Plex Media Server Databases_2021-03-29_23-27-38.zip (5.3 MB) Plex Media Server Logs_2021-03-29_23-27-22.zip (3.0 MB)

Anyone?

Sorry I didn’t see this until now but that’s entirely a client or network issue (most likely client).

This message is very distinct:

Mar 29, 2021 23:20:57.182 [0x7f3f7ece3700] DEBUG - Content-Length of /volume1/Shared/movies/mamoo camera.mp4 is 5582479244 (of total: 6272313539).
Mar 29, 2021 23:20:57.205 [0x7f3f7f2bf700] DEBUG - Failed to stream media, client probably disconnected after 491520 bytes: 104 - Connection reset by peer
Mar 29, 2021 23:20:57.205 [0x7f3f7f2bf700] DEBUG - Completed after connection close: [192.168.50.229:37712] 206 GET /library/parts/6/1577293092/file.mp4?autoAdjustQuality=0&hasMDE=1&location=lan&mediaBufferSize=209664 (13 live) TLS 236ms 491520 bytes (range: bytes=672707540-) 

The client (Android app or network) dropped the connection.

I’ve mostly seen it happen when the Android app gets corrupted. I use iOS so don’t have personal experience with Android devices.

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