why not post them here? just remove any mention of Tokens?
A new version of PMS appeared today for me (Pi so Linux ARM - 1.18.2.2041) but itās made no visible difference to the problem.
I have tcpdump and Wireshark traces run on the PMS device (Pi) filtered on traffic from the LG TV. There are definitely attempts at communication. Happy to paste one or both of them here if any of the devs want to see but there is nothing obviously interesting in them.
The PMS logs Iām looking at are empty of anything containing the IP address of the TV. Iāve turned verbose logging on via Plex web settings, stopped PMS, cleared the logs and started PMS. TV IP is 192.168.0.5. If I go to /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs and run āgrep ā192.168.0.5ā *ā i get nothing seemingly relevant. A couple of hits on SSDP:
Plex Media Server.log:Nov 20, 2019 20:34:58.399 [0xa9ff8450] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.0.5:1802/
Plex Media Server.log:Nov 20, 2019 20:34:58.399 [0xa9ff8450] DEBUG - HTTP requesting GET http://192.168.0.5:1802/
Plex Media Server.log:Nov 20, 2019 20:34:58.402 [0xa9ff8450] DEBUG - HTTP 200 response from GET http://192.168.0.5:1802/
Plex Media Server.log:Nov 20, 2019 20:34:58.404 [0xa9ff8450] DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://192.168.0.5:1802/
Plex Media Server.log:Nov 20, 2019 20:34:58.404 [0xa9ff8450] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.0.5 ([LG] webOS TV UJ750V)
Same log file has lots of info detailing the other devices on the LAN polling PMS - iPads and plexweb in this case.
It does look like an issue with the actual app running on the TV, rather than a network or server issue. I think the āUncaught TypeError: Cannot read property āpopā of undefinedā does tell us which component has the issueā¦ and will point the developer straight to the problem or typo in the manifest\equiv.
We just need to get this information in front of the right developer.
Happy to engage more and/or provide more info.
Cheers.
Here is the Wireshark capture.
plex1.pcapng.zip (2.0 KB)
TV = 192.168.0.5
PMS = 192.168.0.251
Capture Filter = āhost 192.168.0.5ā
Sockets for context:
pi@raspberrypi:/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs $ sudo netstat -tulpn | grep -i āplexā
tcp 0 0 127.0.0.1:32401 0.0.0.0:* LISTEN 22878/Plex Media Se
tcp 0 0 127.0.0.1:39829 0.0.0.0:* LISTEN 22894/Plex Plug-in
tcp 0 0 127.0.0.1:32600 0.0.0.0:* LISTEN 22943/Plex Tuner Se
tcp6 0 0 :::32400 :::* LISTEN 22878/Plex Media Se
udp 0 0 127.0.0.1:43825 0.0.0.0:* 22878/Plex Media Se
udp 0 0 0.0.0.0:1901 0.0.0.0:* 22878/Plex Media Se
udp 0 0 192.168.0.251:49624 0.0.0.0:* 22878/Plex Media Se
udp 0 0 192.168.0.251:34296 0.0.0.0:* 22878/Plex Media Se
udp 0 0 192.168.0.251:50256 0.0.0.0:* 22878/Plex Media Se
udp 0 0 127.0.0.1:33873 0.0.0.0:* 22878/Plex Media Se
udp 0 0 0.0.0.0:32410 0.0.0.0:* 22878/Plex Media Se
udp 0 0 0.0.0.0:32412 0.0.0.0:* 22878/Plex Media Se
udp 0 0 0.0.0.0:32413 0.0.0.0:* 22878/Plex Media Se
udp 0 0 0.0.0.0:32414 0.0.0.0:* 22878/Plex Media Se
udp 0 0 0.0.0.0:54503 0.0.0.0:* 22943/Plex Tuner Se
Let me know if I can provide more.
Bump.
Any ideas, more tests or info we can provide?
+1 also broken for me.
+1, switched accounts and got stuck in the login loop where you input the 4 digits, says successful, and loops back to the login screen.
Same issue :
Uncaught TypeError: Cannot read property āpopā of undefined
on LG WebOS TV
I have made this :
- Uninstall app on the TV
- Restart from power source (TV)
- Remove Device from server. (Authorised Devices) - Done
- Install app - Done
- Link : I donāt go that far. The error pop first ā¦
Every things works well on my Android Phone and my Xbox.
I tried all that and it didnāt help. I even built a new plex server on a test box and tried to connect to it. Still didnāt work. Itās not the plex server itās clearly an issue with the TV app.
1 Like
Does anybody know if Plex support / staff read these forums? We were directed here by the error message to report the issue. Is there any other way of contacting them? Or finding out if they are aware of this discussion?
1 Like
Ok, try looking in Announcements for team member involved in LG app @markus101
Thanks for the ping.
This came up in our error reporting and has already been fixed, but not yet released. Itāll be in the next release which should be going out early next week.
I believe the only way to reset the settings for webOS applications is to do a full factory reset, uninstalling and installing the Plex app again will not clear the settings from storage.
Thanks for the update! Will the new update for the app require us to factory reset our TVs? I had mine professionally calibrated and donāt want to lose my settings.
No that shouldnāt be necessary.
Thank you!!! We are excited to get plex back!
@markus101 Thanks for taking the time to update us and your efforts to fix it. Great to know something is on the way. Will wait for the update.
D
Just an update. Plex is now working on my tv as of today!!! Thanks plex team!!
Happy for you, well done Markus 101
Likewise, working here now too. Thanks @markus101 and the team.
Yeah, mine was working last week too. Wished it was a bit faster, but at least itās working.
Was about to make a new thread but may as well post here. Suddenly started getting Error Code 337 at random. In the off-chance it DOES open, it will see remote Plex servers just fine. The server on the same LAN with it says not connected. Try to reconnect and it says nothing is there. Other SmartTVās and FireTV sticks connect and work fine.
TV is an LG B8 OLED connecting to Synology DS1618+ with whatever the latest is for everything. Going to try an older version of Plex on the NAS since this started shortly after updating. Remote plex server is a pretty basic PC with Windows 10 running PMS, which connects just fine.
EDIT: It looks like I cannot connect to ANY Plex servers hosted on Linux (the 3 I have in my list anyway running on QNAP or Synology). All Windows servers (4 total remote) connect fine.
