Yeah, unchecking the “Scan my library automatically” setting and saving that change has temporarily fixed the playback issue.
A moment ago I started a manual scan for some new music while playing back a documentary and was able to recreate the same error, so it definitely seems to be triggered by the library scans.
In my situation, this is just affecting the desktop clients and browsers, so I’m going to save myself the work of rolling back my PMS version for the time being.
ok, after the rollback to 1.32.8.7639 I successfully played episodes for 2 hours on 3 different machines.
I had the 3 checkboxes still unchecked, so I just rechecked them and ran a lib scan.
A few minutes later, all playbacks stopped, even with the previous version.
So even with the previous version and scans on, it fails.
There must be something on their side.
Hopefully, they will release a patch soon.
Yeah, I unchecked the boxes and watched an episode of Poirot without interruptions. Thanks for the temporary solutions!
I agree that something is going on with the new update. I played one movie and have gone through many of them, but I cannot finish any movies. I kept getting unexpected errors during playback from Mac OS and Windows Plex Media Server. I uninstalled and went back to the previous version, and now I keep getting unexpected errors as well. Just like someone mentioned, the only remedy for me to not get errors now is to connect directly to the plex server, not plex.tv. I guess we will have to wait for a better version that patches these error bugs.
Same issue. Started happening after updating to Plex Media Server 1.40.0.7998 running on Ubuntu (VM in ESXi, with a passthrough GPU for transcoding), and a simultaneous update to Plex for Windows 1.87.2.87-87488d5a running on Win10.
I even get the popup error message when I’m not playing anything but the client is just open and idle.
I’m experiencing the same issues here. Super frustrating and sometimes in very quick succession. I’ll try to turn off library scanning as a workaround until the issue is resolved.
1.40.0.7998 on macOS Sonoma 14.3.1 and files stored on Synology DS1515+. Didn’t happen until the latest update.
This Windows/Mac version works, download and install - do not install updates
I had noticed on Windows being on the main screen the home page would flash and then playback would stop with an error. As of right now, disabling scanning libraries seems to fix it. I had even tried to roll bake on public versions but had no luck doing that, still had the same problem till I disabled scanning.
I have the same issue, disabling library scanning did not stop the interruptions.
I have 2 local clients on my network. 1 client is running N-1 from latest windows client and can play content without issue. Swiveling to the client with the newest windows player is interrupted every 5 minutes no matter what content i play, on the 5 minute mark, every 5 minutes, and its driving me nuts. I’m very relieved to find this thread.
I have used revo-uninstaller and purged everything down to registry, reset to default, and tried the workarounds here.
I hope a fix is pushed soon
My problems were resolved by rolling back to windows client 1.79.1x linked above, tyvm
Just had the issue happening to me. Running Plex server on windows (Version 1.87.2.87-87488d5a)
Was watching without issues until I added a new file to my server, and the auto scan kicked in… While it was working, I kept on getting kicked out.
The moment the scan stopped, no more errors. In my case, like mentioned in previous posts, it seems related to the library scan.
Same issue here on my Mac Studio (running MacOS Sonoma 14.3.1). Running into the error on both app and web with the latest updates (Plex Server 1.40.0.7998). Rolling back and disconnecting from the internet just to use Plex isn’t something I’m going to be doing. And unchecking all library scanning options doesn’t prevent the error either. Hoping for a quick fix!
Confirming that this continues to happen. Been happening for over a week now.
This just started affecting me today. I’m on Plex For Mac on MacOS.
I’m not adding/deleting any media, just happens randomly and very frequently.
Edit: It looks like the suggest workaround of disabling auto-sync works so far.
I presume you may also need to disable the other scans depending how often you edit/update your media files etc…
Not to beat a dead horse but same issue here. No issues when on server version prior to 1.40. Once I updated to 1.40, app.plex.tv will do a partial reload very randomly, but constantly over the last 2 weeks. This causes streams to fail with the errors above. Tested on multiple Windows PCs, using both the Plex app and the web app through Chrome, Firefox and Edge. All other platforms I’ve tested, iOS, Roku, Nvidia Shield and various TV apps all work fine. Happens on multiple servers as well, both local and remote.
The don’t seem to be in any hurry to fix this.
You have to disable ALL scanning, ALL metadata updates. Go to your scheduled maintenance and disable all of those for now, not just auto and scheduled scanning under library settings. I have a feeling this is gonna last another week.
Not to you @ChristianKent but does anyone know if this has actually been acknowledge by Plex as a bug and it is being worked on, or is there somewhere I can actually see a list of bugs? I’ve looked at a few other issues people have raised but don’t seem to find any official person acknowledging this?
No official statement or acknowledgement officially yet unless I’m missed something. There are separate threads on this issues in each sub forum e.g. for every player though.
A bit disappointing to be quite frank.
Yes to both. Plex staff have mentioned this in a couple of threads.
Appears to be a difficult bug to squash with no consistent explanation for the behaviour.
Yes, a few employees from Plex confirmed (around 2 days ago) that they know which code commit is responsible. They said they’re waiting for a fix (whatever that means). This morning, another employee said they were having trouble reproducing the error consistently. So I don’t know which one is accurate!
