Issue Summary
Following the recent Linux repository migration (Plex Media Server v1.43.0+), the Roku client is unable to successfully “Resume” from a saved position or “Seek” (FF/RW) during playback. When a resume or seek command is initiated, the Roku player fails to find the timestamp and defaults to restarting the video from 0:00. This issue is exclusive to the Roku client; web and desktop clients function as expected.
Environment
-
Server OS: Linux (Debian/Ubuntu) running on Proxmox (ext4 internal storage).
-
Server Version: 1.43.x (Updated via new
repo.plex.tvrepository). -
Client Device: Roku (Roku Plex App v9.x).
-
Filesystem: ext4 (50% utilization), verified
execmount flags.
Steps to Reproduce
-
Open any partially watched video on a Roku client.
-
Select “Resume at [Timestamp].”
-
Actual Result: Video starts over at 0:00.
-
Actual Result (Seek): Pressing Fast-Forward or Rewind during playback causes the stream to break and restart at 0:00.
Attempted Resolutions (Non-Functional)
-
Database Repair: Executed
DBRepair.sh(Option 2/Auto) to rebuild indexes/integrity. No corruption found. -
Maintenance: Performed “Optimize Database” and “Clean Bundles.”
-
Permissions: Verified
plex:plexownership and775/777permissions on/Cache/Transcode. -
Cache: Cleared all Transcode caches and Plug-in caches manually.
-
Client Side: Reinstalled the Roku app and performed a deep system cache clear.
Temporary Workaround
- Disabling “Direct Play” on the Roku client while keeping “Direct Stream” enabled allows the video to resume correctly. This suggests a failure in the initial handshake/seek-request when the Roku native player attempts to direct-play the file structure provided by the new FFmpeg 6-based server engine.
Desired Solution
A fix for the Roku Client Profile or Server-side Transcoder logic to correctly pass the start_time parameter for Direct Play sessions on the new Linux package builds.