Plex not working anymore with latest LG WebOS

I want to specify that I got a LOT of support by Chuck in private messages, but unfortunately he never succeeded in replicating the issue.

I have a OLED65CXAUA and am having this issue. Won’t even load the Plex app. I’ve uninstalled and reinstalled and same behavior.

Please note that this is a different issue and should be discussed in a different topic. Thank you.

Getting the exact same issue on my LG G2, went to latest version and playback becomes impossible. There’s nothing of note in the console logs, with Plex registering that play back attempts to begin, then simply stops.

1 Like

Getting transcoding errors only on an LG TV. Getting this error in logs [Req#e29] Unable to find client profile for device; platform=webOS, platformVersion=4.10.0, device=webOS 4.10.0, model=65UM7300AUE. And then another error that Transcode runner appears to have died.

same problem for me. Updated the app and my server to the latest versions.

[Req#24de] Unable to find client profile for device; platform=webOS, platformVersion=9.2.1, device=webOS 9.2.1, model=55UR9000PUA

Clear Filters and Jump to Context

I have a whole bunch of problems with the WebOS Plex app, but one of the biggest issues is that, at random, the Plex app throws an “unexpected playback error” at me when using autoplay.

E.g. I’m watching a series and episode 1 finished playing. It should autoplay episode 2, but gives me the error. After that, I can’t play any content at all and need to completely exit the app, open the app again and manually select episode 2. Episode 2 will play fine. Episode 3 might play fine. Episode 4 will throw me the error again.

If I repeat the same thing, it might be that 1, 2 and 3 play fine but I need to intervene for episode 4. If I repeat again, it might be that I need to do it for every episode. Again, and maybe the whole season plays without issue.

It looks super random - I can’t find a pattern when it’ll fail and when it won’t - and I can only replicate this on the WebOS app. Any other app (iOS/iPadOS/Web/PS5/Apple TV) doesn’t have this behaviour. It’s regular old 1080p H264 content, nothing fancy.

Another issue, probably for another topic, is that every couple of days, the Plex for LG webOS client somehow manages to crash the server itself. I checked the regular logs and can’t find a reason except for the “unable to find client profile for device”, but that happens more often and also when the server doesn’t crash. I have the report crash logs to Plex thing enabled so these should make their way towards Plex devs. It’s a weird one as it only happens while watching using the WebOS app and never using any other apps.

While not normally my area, I have both Syno and LG. :slight_smile:

I have an LG C1 OLED.

I’ve started it running and will see how long it runs before failure.

Not sure it matters and/or if there’s different app versions for different WebOS versions.

I’m on a LG G3 OLED (2023 model) running WebOS 24.

Do you have your server on a Synology NAS and have “Download station” app active on it, by chance? Even if you are not DL/UP anything? If so, could you try to close “Download station”?

I don’t own anything Synology and will never own anything Synology, especially not now that they’re feature locking stuff behind their own rebranded hard drives.

That said, no, Plex Server is running on a dedicated M4 mac mini with 16GB RAM and a 10Gbit NIC, and there’s a HDD array connected to it for storage.

Same here. Made sure everything was updated, no help. I decided to get a Roku Streaming Stick 4K and plugged that into a spare HDMI input, and Plex works just dandy from there. It’ll be nice when/if the bug (WebOS? Plex app? Or?) gets diagnosed and fixed, but till then I set the input to the Roku and Bob is once again my uncle.

Unfortunately, the issue keeps coming and going. Even recreating a server from scratch did not work. Something got broken a few builds ago, either with the Synology NAS PMS or the LG Plex app. :frowning:

I have a LGOLED65C3PUA and also have been experiencing this playback issue for at least six months. Not sure of the cause.

I can confirm that media that previously played perfectly fine, now shows the playback error. But oddly all media that previously played perfectly fine, seems to continue to play if I Force Direct Play. I haven’t seen anyone mention trying that, but it’s been a workaround. I’ve inspected the debug logs and did not see anything odd, concerning, or out of the ordinary.

On all of my other LG TVs and misc. devices I do not have these playback issues, and I do not have to use the direct play workaround ever.

Note: I do not use a Synology NAS, and I have the latest versions of both PMS and WebOS installed on my devices.

Same here, brand new 65C5PUA, same issue. Really a bummer, hope we’ll have a fix soon.

Brand new LG OLED 55C5 in UK. Very random different codecs, some remuxed without subs - still happens. Fully power cycle the TV and it works for a bit.

Newest PMS, WebOS updated, newest Plex App

Upgraded to a new LG OLED65C5PSA a few weeks back and the Plex experience has been pretty terrible. Content that played on my old LG OLED55C9 for last 5 years now either exits quickly with a memory error, or stutters and grinds to a halt before the opening credits are finished. Pretty much anything with an external subtitle file dies immediately with a transcoder error.

Content is coming untranscoded off an Intel NUC media server running Windows 11. I don’t have these problems with the same content via Plex from my Windows 11 laptop, nor do friends remote streaming.

I saw the post about media files with too many subtitles. I tried removing all but 2-3 English subtitle tracks using MKVToolnix but it doesn’t fix the problem on the LG TV.

TV is fully updated. Have not encountered any problems with external streaming apps.

Came here looking for answers to the latest “Not enough cpu for conversion of this item”-issues.

Upgraded to LG WebOS 33.22.80 yesterday, and it didn’t improve. Only way to solve it it seems is to restart the Plex Docker Container (running on Linux) even though I have plenty of CPU to spare.

Any advice? Anyone I can send debug logs to?