Thanks for offering but what we need is the sequence (Steps to reproduce) the failure.
I’m asking for this so we can start PMS in the debugger, set a breakpoint on the error, then recreate the error on demand.
We only need to to capture it once in the debugger to see where the error is coming from in the code. As we do this, we’ll see what all the variables’ values are and what causes it (which is what we’ll be able to fix)
Is it possible to get a beta build that can output more error codes to help with this issue?
I am willing to run anything on my windows machine to help resolve my issues.
We’ve seen the error manifest in multiple logs.
What we don’t have is the exact , reproducible , Steps to reproduce.
This is most likely going to be:
If I can reproduce it on ANY of the various machines I have, that’s all we need.
It’s the " It’s reproducible THIS way " that we need.
So an update today that my wife discovered: We had begun a movie before all this happened, according to Tautulli on July 14th.
On my laptop, that movie is unplayable via the web interface and the Linux Plex app with the same error when attempting to resume the movie, “An error occurred loading items to play.”.
However, on the GoogleTV projector that we were watching the movie on previously, playback resume worked! I don’t think the movie was cached on the device. So then we tried a different movie. Movies are playing fine on the Google TV interface. Trying the same movie on the Android app, Linux app, or direct web interface fails with the error above.
Another oddity, is that Plex Dash and Tautulli do not believe anything is currently being played, despite this movie playing right now. the debug logs show that it is in-fact transcoding the movie:
Transcoder segment range: 498 - 593 (592)
Session 59d11d03efd2b7c6-com-plexapp-android (3) is throttling
So movies will play on Google TV it appears, but not currently on anything else, Plex is not tracking the movie we are currently watching in the “continue watching” category, and Tautulli and Plex Dash don’t believe anything is playing.
If capturing some specific sequence of logs with these events would help, I can provide those. I re-walked the plexmediaserver releases back to the current and rechecked the database, it is an odd mystery to me that previously working server installs now won’t play anything via any app interface that I have, other than playing already started videos in one fashion or another.
Okay, another data point, when trying to play a movie trailer from “trending trailers” I get the same error! And those aren’t local files at all. It must be some video playback library that updated and isn’t being downgraded as I perform downgrades of the server.
This plexmediaserver instance is running on Ubuntu 22.04.
would you mind repeating that sequence, with server DEBUG logging enabled?
My hope is that with all those events, we see what reproduces it reliably.
( We need 100% repeatability so we can track where it’s happening )
I’m not sure if this is helpful, maybe others can chime in on their settings to see if it’s something we have in common.
General:
Network:
Transcoder:
Scheduled tasks
OK, I tried playing a movie via app.plex.tv and got the “An error occurred loading items to play.”
I then went to the Google TV player, and directly navigated to the same movie, clicked on play, and it spun with the loading circle for a long while before I canceled it (this is a local server on the same network). I then backed-out of the attempted playback, and clicked on “Play” again. This time, the movie started up instantly.
I let it play for 30 seconds, confirmed that the Plex Dashboard did not show anything playing, and then exited the movie. On the card for the movie, there was no “resume” option added either.
I then tried to play a “Watch the Trailer” on a movie, on Google TV, and it worked fine. Then, from app.plex.tv I tried to play the same trailer for the same movie, and got the same error as above.
On the Google TV, I then went to a TV show and at the top level hit play and received the error “Unable to play media”. I then went into a Season of the same show on Google TV, and the first episode played fine.
I can share my server settings, but I haven’t touched them in ages, and not in particular just before it broke. I turned off Verbose mode and then exported the logs to attach here. I hope these help!
Plex Media Server Logs_2025-07-20_23-45-52.zip (2.9 MB)
My settings (bold are not equal to @Lylesback2’s settings).
General:
Network:
Transcoder:
Scheduled tasks:
So nothing we watch when playing the video directly in Google TV Plex gets logged on the server as being watched. I think the only playback possible is where playing the file skips the tracking system or the update to the database is after playback has begun. On the web interface, because it’s directly through the server, it always tries to update the watch status first, and when that fails, playback doesn’t begin. On the TV, it’s a little more lax with how it records watch status in an effort to get the user their content faster.
When playing a trailer on any platform, Plex tries to log that to a database somewhere, and when that fails, it refuses to playback.
Could some part of our playback database be corrupted in a way that the regular database checks aren’t validating, or it could be fine but a write lock is being held on some table that is preventing more updates to the rows in it?
I think this might be helpful.
Using my browser and inspecting the developer console, when i try to play anything, i get this error:
426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
POST https://192-168-0-101.742adb8….plex.direct:32400/pl…4&X-Plex-Drm=widevine&X-Plex-Text-Format=plain&X-Plex-Provider-Version=7.2 500 (Internal Server Error)
(anonymous) @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
send @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
ajax @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
(anonymous) @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
S @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
(anonymous) @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
(anonymous) @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
u @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
add @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
(anonymous) @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
each @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
(anonymous) @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
Deferred @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
then @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
U @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
ui/player/playerLifecycle/startPlayback @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
ui/player/playerLifecycle/startPlayback @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
e @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
metadata/redispatchLegacyMetadataAction @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
e @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
(anonymous) @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
(anonymous) @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
(anonymous) @ main-8792-240f4f89d4….148.0-f37f4e0.js:2
ol @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
xu @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
(anonymous) @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
_u @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
uu @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
Ho @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
(anonymous) @ 426-426-85d9cf5e34b8….148.0-f37f4e0.js:2
Here is the full url:
POST https://192-168-0-101.742adb82e85c4323975f64623ec692b1.plex.direct:32400/playQueues?type=video&continuous=1&uri=server%3A%2F%2Fee005634794eb1fec84cafdd737e7a0091b2523b%2Fcom.plexapp.plugins.library%2Flibrary%2Fmetadata%2F72781&repeat=0&own=1&includeChapters=1&includeMarkers=1&includeGeolocation=1&includeExternalMedia=1&X-Plex-Product=Plex%20Web&X-Plex-Version=4.148.0&X-Plex-Client-Identifier=z881c5tst91nltie6vn5so14&X-Plex-Platform=Chrome&X-Plex-Platform-Version=138.0&X-Plex-Features=external-media%2Cindirect-media%2Chub-style-list&X-Plex-Model=standalone&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=2190x1075%2C2189x1231&X-Plex-Token=REMOVEDTOKEN&X-Plex-Language=en&X-Plex-Session-Id=6c4a3c94-9053-4f15-8668-2db0835590c0&X-Plex-Playback-Session-Id=d7acc9f5-72d0-417c-8190-3ebf61a42380&X-Plex-Playback-Id=f45db8a7-914f-4b34-8d91-9c4ac7fa24c4&X-Plex-Drm=widevine&X-Plex-Text-Format=plain&X-Plex-Provider-Version=7.2 500 (Internal Server Error)
It’s throwing an error on this JS file:
(anonymous) @ 426-426-85d9cf5e34b86c42fbeb-plex-4.148.0-f37f4e0.js:2
This is the part of the code where it throws the exception
e.prototype._wrapXHR = function(e) {
return function() {
for (var t = [], n = 0; n < arguments.length; n++)
t[n] = arguments[n];
var r = this;
return ["onload", "onerror", "onprogress", "onreadystatechange"].forEach((function(e) {
e in r && "function" == typeof r[e] && (0,
i.GS)(r, e, (function(t) {
var n = {
mechanism: {
data: {
function: e,
handler: (0,
a.q)(t)
},
handled: !0,
type: "instrument"
}
};
return t.__sentry_original__ && (n.mechanism.data.handler = (0,
a.q)(t.__sentry_original__)),
(0,
s.LV)(t, n)
}
))
}
)),
e.apply(this, t)
}
}
I have the same issue. I keep restoring the snapshot of my VM from the last day it worked. The next day in the morning it is not working anymore. Could this be related to the nightly maintenance jobs? I did all of the db check and rebuild instructions on the help site. The problem does not seem to be related with db corruption. Another thing I noticed the plexmediaserver service seems to constantly use about 25% of the cpu even if there are no clients connected.
Update: whoops, I just noticed this is in the docker subforum. I do have the same issue but I run Plex ‘natively’ in an lxc container on Proxmox.
Update 2: I also noticed a huge increase in memory consumption since about may. I have relatively small library, so 2GB was fine for for the past years. In may, I had to first extend to 4GB, then to 6GB. Just before the error started I extended to 16GB, where 11 GB were beinng used after one day (used memory, not cache/buffer).
@ChuckPa a few of us have provided some debugging information and it’s been a couple of weeks. Any update from Plex on what to do? I have had this server running since 2023, I’d like to keep it, but if the Plex engineers can’t figure out why it’s broken, I’m going to have to try to reinstall I guess, or take some other drastic measure. But it’d be a colossal pain, and I’d really like to figure out what broke here (since it’ll probably happen again and it is impacting other server operators) and get it resolved, but this has been a long standing bug since the last release!
I have no feedback about what the Plex/web team is doing.
All I know is that folks have been reprioritized a bit to fix problems.
I do not have any idea which “problems” are being worked on.
For me, Something as simple as Plex/web issuing a “something went wrong” loading the page seems very specific because it’s easily recreatable but that’s just my thoughts as support engineer.
With no update for a while, is there a way we can escalate this server bug with the Plex developer team? A bug we can open or any additional recourse? I really don’t want to have to build a new plex server merely because of a database conflict.
For what it’s worth, I had the same issue, ended up reinstalling Plex media server and now it works again.
(I am just on a standard windows 10 machine for my server).
I found an old backup from a few versions earlier. Since the issue does not seem to be of interest for the Plex team unfortunately, I reverted to this version, which worked fine.
A few weeks later I directly updated to the current version and things still work stable.
I have tried reverting to older PMS on my windows 11 machine, It didn’t address the issue. What version did you try to get it to work again?
Did you uninstall and install an older version, restoring for backup?
Or did you just reinstall an older version on-top of the existing application?
I am currently running Version 1.42.2.10102 and I am still experiencing the issue
I went back to version 1.41.6.9685 which was released in April. Somewhen in May Plex started to request more memory, which got worse. In July it stopped working with that error message posted above.
I am running plex as LXC container on a Proxmox host - which is basically a ‘lite’-version of a virtual machine. So I was able to restore the whole machine, including Plex server, the database and everything else to that previous state. I just lost three months of viewing history.
