It does seem to me to be an error output at the TV OS level..but the TV displays NO network issues with anything else (youtube, netflix etc.) and no other device on my network has plex connection issues. Also, if I use the TV to stream anything through DNLA from the same Plex server it works perfectly.
I seem to get these in the console when the -337 is displayed:
[CompanionProxy] player ffyjop4r2op6vl1brtemtgf2 was last refreshed 10 seconds ago
This shows up in console right when it happens.[Plex Media Server
Failed to stream media, client probably disconnected after 63819152 bytes: 104 - Connection reset by peer
That is an LG error. We have no control over that.
That first Plex message is harmless, it just means that a Plex device couldnāt be found. This is used for identifying other players so you can use one Plex client to send playback to another Plex client.
That second error is a result of the loss of network connection, not a cause so that would be expected to see if the TV losses connection.
I my experience. Iāve seen lots of issues with the WiFi on LG TVs. Not sure if itās an interference issue or just a bad WiFi card on the TV. I get that from time to time on my own TV, even when not using Plex. If possible, use the wired connection. That works much better.
I get that the LG OS is putting out the errorā¦but I have NEVER seen that error on my TV except when using the LG Plex app. It ONLY shows up when when using the LG Plex app and streaming from the same Plex server via DNLA never has a similar issue. Also, a few PMS versions ago I never got this error. It is new.
It is clearly triggered by something in the Plex app. The plex app wonāt even load and go to the home screen most of the timeā¦it just displays the plex logo for 30 seconds or so and then goes to this screen. All other apps works flawlesslyā¦ALL THE TIME.
Itās not a TV wifi issue or it would be displayed just as often using netflix, youtube or any other network reliant app etcā¦or streaming from the same server via DNLA but it NEVER doesā¦not once.
Itās not an interference issue. I live in a remote area and Iām the only wifi signal around.
I ran an Ethernet cord to the TV. Still got that same -337 error screenā¦all other apps work fineā¦DNLA works fine.
Itās like the Plex app crashes the TV network driver or something like that. It doesnāt act like thereās an actual network issue. Or maybe PMS doesnāt recognize that its asking for data?
Power off TV and disconnect from power for ~30 seconds.
Reconnect power, turn on TV, download app, login/authorize.
I have a LG B7 OLED. A few times the Plex app has not worked after Plex or LG updates. A basic remove/reinstall along with disconnecting the power fixed things. Cannot explain why. Seems to clear out the system. Somewhat like the Plex Dance when there is trouble adding media to a library.
@FordGuy61 This fixed the issueā¦weāll see how long it lasts. (IPv6 has never been enabled)
Iāve done those same steps beforeā¦but the issue had come backā¦I never associated the issue with PMS/LG client updates. That could be what makes it show up.
Of note: the My TV has had lots of pairing/authorized device strange things (bugs). Previously when I did the āremove authorized deviceā then re-added, the TV didnāt show up in the authorized device listā¦but would connect and play videos etc.
@anon18523487 You still think itās an LG error you have no control over?
Itās possible the Plex app is making more network related calls than other apps and this could be overwhelming the tv. Iāve seen this happen to some cheap routers. But if removing the app and reinstalling fixes things, I canāt say itās the Plex app either.
Do you have the Plex DLNA server enabled? Iāve also seen DLNA mess things up.
I donāt normally have Plex DLNA server enabled. I just enabled it to test the network connection. It was and has been disabled otherwise.
I donāt have a cheep router. The TV is connected via 5 GHz wifi with a good signal and can play 80Mbps+ 4k HDR streams no problem.
The issue showed up even when the TV was connected via LAN cable.
The issue is not related to playing a video/audio stream. It will display the -337 screen when I am just in the Plex browse menuā¦or just opening the plex appā¦it will also display while playing video though.
If the TV is offline (intentionally I disconnected from the network) this is what you get:
If I take my Plex server offline then I get the -337 page on the LG Plex app.
Edit: Connection problem came back. Itās also hard to believe itās related to the router because I can stream a 4k HDR video to my phone/computer no problem while the TV is having connection issues.
Doing the steps FordGuy61 mentioned consistently fixes the issue temporally for me. Works great right after re-pairing. After I turn the TV off and let the TV/PMS sit for a while it comes back.
Having the TV and/or PMS on LAN cable vs. wifi makes no difference.
Itās clearly specific to ONLY the LG Plex app. All other clients I have work great while the TV is having issues.
Probably is specific to nVidia Shield as PMS w/LG TV combo?..I have 1.18.8.2527.
Probably also related to PMS/client comboā¦I havenāt always had this issue.
Possibly also specific to something about that combo and my Asus RT-AC68U router?..but nVidia Shield seems to have no issues with any other device combo either wired or wireless.
Did you find a solution for this, have the same damn issue. Sometimes it logs in no problem but as soon as I start playing a movie it pops up. Then i have to restart plex and do it again. Sometimes I need to turn the TV off and unplug it for it to work.
No I have not. The responses Iāve received from a plex team member:
This clearly isnāt a true statement. It is an LG TV OS level error message. It is also clear that it is related to how the Plex TV client and PMS interface with each other and/or āphone homeā to plex serversā¦it is clearly not an issue with the TV and/or network.
I get the same result using wireless and wired.
I donāt have a cheap router and no other combination of devices on my network or apps on the TV etc. have any issues whatsoever.
