"There was an unexpected error during playback" on all media (MacOS v1.87.2.87-87488d5a)

Server Hardware: Synology DS1621xs+ (INTEL Xeon D-1527)
Server OS: DSM 7.2.1-69057 Update 4
Plex Server Version: 1.40.0.7998-700

Client Hardware: MacBook Air M2
Client OS: Sonoma 14.4
Original Installed Version: Version 1.86.1.4076-a3ab948d
Auto updating to Version: Version 1.87.2.87-87488d5a

After auto updating (is it possible to stop this?) from 1.86 to 1.87 on my MacBook of all (least as many as I have tried) it stops playing after a few minutes (is variable) with the following message:

—

Playback Error

There was an unexpected error during playback. Please visit out forums if you continue to experience problems.

—

If you close it and start playing the media again it works straight away and then another few minutes and it stops with same message.

All media works on the previous version and also on Apple TV, and iOS devices so it is def the updated version and when I roll back to the originally installed version.

I keep rolling back to the originally otherwise I can’t watch anything on my Mac, but it keeps forcing an upgrade when you restart it.

11 Likes

Same here, I’m running the server on a Linux Mint machine and haven’t tried it on other apps, and I’m not sure this is exactly the right error log? But this is what the app showed:

[
  {
    "type": "info",
    "host": "",
    "userAgent": "Plex; 1.87.2.87-87488d5a; Freedesktop SDK 23.08 (Flatpak runtime)",
    "browser": {
      "platformVersion": "0",
      "id": "unknown",
      "name": "Unknown Browser",
      "version": "0",
      "platformID": "unknown",
      "platform": "Unknown Platform",
      "platformModifierKey": "ctrl"
    },
    "version": "4.124.1",
    "primaryServerUrl": "http://127.0.0.1:32400/",
    "primaryServerAuthToken": true,
    "username": "pasanov",
    "cloudUrl": [
      {
        "scheme": "https",
        "address": "clients.plex.tv",
        "uri": "https://clients.plex.tv",
        "testState": "connected",
        "isBundled": false,
        "isFallback": false,
        "relay": false,
        "isUntested": false,
        "isPending": false,
        "isConnected": true,
        "isUnauthorized": false,
        "isUnavailable": false,
        "isFailed": false,
        "isAborted": false,
        "isLoopback": false,
        "isPrivate": false,
        "isHttps": true,
        "isSecure": true,
        "isPlexDirect": false,
        "currentTest": null,
        "sources": [
          {
            "id": "internal"
          }
        ]
      }
    ]
  }
]

Currently experiencing this as well on a windows system.

2 Likes

I can confirm that I’m seeing the same sort of misbehavior on the Windows 10 client version 1.87.2.87-87488d5a. The error doesn’t seem to be linked to any particular media type. I have had it happen when I am streaming 4K video at 20+Mbps or music at 330 Kbps.

For added context, I have two Android devices that are both updated and on version 10.8.0.554 (86193d4). They do not seem to be affected by the issue whether accessing media via direct play or via transcoding, or whether they are local or remote. I had thought this was an issue with my LAN until noticing that my Android clients were completely unaffected.

Server OS: Ubuntu 22.04.4 LTS
Plex Server Version: 1.40.0.7998-700

Client OS: Windows 10 22H2
Plex Client Version: Version 1.87.2.87-87488d5a

1 Like

I thought it might have something to do with this report: App.plex.tv unusable - re-renders every few seconds - #2 by suvik so I changed the time plex rescans my library from 30 minutes to 1 hour, it didn’t work. It still took about 30 minutes before the error reappeared and the stream got interrupted.

i think i have a similar situation (with the windows app), happens in the webapp too

This happens to me on all media. Chrome browser on windows. Just started.

Note, rolling back to the prior snap (ubuntu host) didn’t fix it. Logging out and back in didn’t fix it.

I suspect the problem is on plex.tv.

NOTE: None of my plexamp installs are affected. Neither is the standard plex app on iOS. Its exclusive to the browser.

1 Like

Ditto here, somebody broke something!

Edit - attaching logs

Plex.1.log (3.6 MB)
Plex.2.log (1.8 MB)

Edit to confirm turning off library scanning fixes it.

@peter.a.bayliss → same problem as in this thread MacOS Player Crashes Streams - Plex Players / Desktop Players - Plex Forum
Can you please upload your Desktop player logs ? Plex staff @BigWheel said this would help them.

Note - if I connect directly to my plex server (ip:port) rather than going through plex.tv it is rock solid.

So in the meantime, stop using plex.tv I guess.

Updated my plex for windows client to the latest flavor this morning. Experienced approximately 3 crashes over the course of 15 minutes in the first use.

I am having the same issue as well, normal video play back used to be fine. Starting few days ago the Plex Windows version is having some update problem. Keep getting “cannot get elevated priviliage” error. Finally able to upgrade tonight but now getting this play back error.

Reinstall this desktop player from the latet version seems to resolve the issue.

v.1.87.2.87-87488d5a
February 16, 2024

sadly this is the version that is causing the problem so downloading and installing fresh from the website doesn’t fix the issue (i’ve just tried again today)

plex-mac-desktop-logs.zip (121.4 KB)

I’m also experiencing this; playback stops mid-stream, seemingly at a random point, and this alert pops up. Happens every few minutes, seemlingly regardless of content. Resuming restarts at the point it was interrupted, without any errors.

Plex Player 1.87.2.87-87488d5a-x86_64 is running on Windows 11 Home 23H2. Plex Media Server 1.40.0.7998-c29d4c0c8 is running under Ubuntu 23.04 (Lunar Lobster), inside an LXC container under Proxmox. Both OSes are current with updates.

Machines are connected over 10GB ethernet, with one network switch between them. Both machines are high-performance, with plenty of resources.

Plex.log.zip (41.1 KB)

1 Like

disabling all scanning fixes it until they can release a patch on monday.

1 Like

Dito on 3 different windows machines running 1.87.2.87-87488d5a connecting to the same local server.
2 x windows 11
1 x windows 10 (same machine as the server runs on)

Thank you for posting! In my limited testing this morning, that does seem to be the source of the issue.

My scan interval was set to 15 minutes, and sure enough, 15 minutes was the longest session I could stream anything for. Disabling the scan allowed me to stream for longer than 15 minutes, so I until I have an interruption while scanning is disabled, this seems to be the best workaround for now.

1 Like

do you mean the 3 checkboxes are the top of the “Library” settings, or are there more? I just disabled them and it stopped again.

I just rolledback PMS to 1.32.8.7639using instructions from
PSA: Here’s how to roll back to a prior version of Plex Media Server on Windows. : PleX (reddit.com)

fingers crossed…