I was, I will re-check now I’m home from work>
BRB
Edit: Its now working, no manual was set.
Thanks to all involved, now hopefully the devs can code a solution for us all.
Can this work around be published more widely for LG Smart TV users PLEX Employees?
Still not connecting, despite all suggestions. I know it is 3rd party, but XPlay finds it without problems. However, that project appears to be dead and gives “red circle of death” when trying to play media. Maybe it would be possible though to use the part of the code in that app that handles (manual) connections? Or just check what is the difference with your previous version 4.29.9?
That said, it looks like there is some kind of connection if I look at the log files (I’m no expert, but the IP’s of both my tv’s with the old and new version, seem to connect without errors), but the app doesn’t recognize the connection as the actual server. Perhaps the log file gives you some more info as to how to fix this issue?
Plex_Media_Server[1].log (1.4 MB)
Yes, I did it in the network section of the server settings.
We’re unable to access your logs. If you can upload them again we can take a look.
I’ve reproduced your network setup the best I can with the information you’ve provided and I’ve been unable to reproduce the failure.
WAN
Router LAN IP: 192.168.5.254 (LAN1)
webOS TV: 192.168.5.61
Second Router WAN IP: 192.168.5.137
Second Router LAN IP: 192.168.50.254 (LAN2)
PMS Server IP (behind second router): 192.168.50.100
In the webTV app, both Allow Insecure Connections and Prefer Insecure Connections are set to On same network as server. Internally On same network as server is allowed when the connection is using a private IP address and both the server and the app share the same public IP, if you’ve got a multi-WAN IP setup you’d need to change that it always, though manual server connections ignore that setting.
Out of the box nothing works, the webOS app is unable to access the PMS server nor is another computer on LAN1. Since I’ve configured no routing between the two networks and there is a firewall between the two, this was my expected outcome.
After adding a firewall rule on router2 for source/destination port 32400 TCP pointed to 192.168.50.100 again nothing works out of the box.
I added a manual server connection on the webOS TV for 192.168.5.137:32400 (pointing to the second router) and allowed 192.168.5.61 to connect to PMS without authentication (List of IP addresses and networks that are allowed without auth in the server’s Network settings). Result: Success.
I reverted the TV and server settings I made above and instead added a Custom server access URLs of http://192.168.5.137:32400 (again in the server’s Network settings), restarted the webOS app and the app automatically connected to the server.
I’ve been comparing the current and previous versions of the app as it relates to server connections (manual or from your plex.tv account) and haven’t found any differences in my tests, but if there are differences between my test setup and yours that is something we can look into.
This is not a configuration issue. This is an issue with the rewrite of the Plex app.
I am having the same issue. When I first bought my LG OLED TV, I spent hours troubleshooting not being able to connect to my local plex server (Synology NAS running plex in a docker) and my only solution was to “leave early access." This has now been replaced with “sign out” in the user options. Plex access works on every other device in my home (and outside my home) and works on the older version of the application.
If you can’t fix this issue, I’m going to have to find another solution as I have designed my home media system around Plex.
I don’t see why you aren’t allowing users to revert to the previous version when there are glaring issues with local plex server connection.
We need a solution to revert back to the previous version quick. I designed my media system around Plex and this completely breaks it.
Thank you so much for taking the time to look into this. After hours of fiddling with the settings in the app and my routers, I finally managed to establish a remote connection to my own local server. This is a bit silly and an inferior set-up, but at least I can watch all my media and as my internet is decent, in original quality.
However, as @jsil is saying (and several others), there is definitely something wrong with how the new lg-webos app is handling manual server connections, at least in some cases or with certain set-ups. So I would also still like the option to revert to the previous version, at least as long as this issue is not resolved.
Below is a part of the log-file, maybe it helps tackling the problem.
Once again, thank you for all your efforts. I’m happy I can watch my media on both my tv’s now, though the situation is not ideal (yet).
Mar 28, 2021 14:19:32.729 [5380] DEBUG - Request came in with unrecognized domain / IP ‘185.XXX.XXX.19’ in header Host; treating as non-local
Mar 28, 2021 14:19:32.729 [5380] DEBUG - Auth: authenticated user 1 as BartVdeC
Mar 28, 2021 14:19:32.729 [9832] DEBUG - Request: [185.XXX.XXX.19:45332 (Allowed Network (WAN))] GET /player/proxy/poll?deviceClass=pc&protocolVersion=3&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cplayqueues&timeout=1 (54 live) TLS GZIP Signed-in Token (BartVdeC)
Mar 28, 2021 14:19:32.729 [9832] DEBUG - Content-Length is -1 (of total: -1).
By the way, how can I adjust the subtitle offset in the new version?
I’ve compared connections to various servers in the old app and the new app and besides relay (indirect) connections I have not found an issue with what I’ve tried, including manual connections. If you can provide more information on how Plex in docker is configured, network type being the big one, I can try to reproduce the issue.
Can you elaborate on what you’ve done to get things working currently? and maybe explain a bit more about the setup of your network/where the VPN is running as well? If you were using manual connections before what IP address were you using to connect?
Is this with a manual connection in XPlay or with an auto discovered one?
After getting an authentication token (https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/)
If both of you could replace xyz with the token in the URL below and PM me the output
https://plex.tv/api/v2/resources.json?includeHttps=1&includeRelay=1&X-Plex-Client-Identifier=12345&X-Plex-Token=xyz
it should tell me what connections to the server your TV is seeing.
Markus, the network type is bridge in docker. Below is a screenshot of the container.
I have successfully connected to this PleX server via browser on multiple computers, PleX app in Roku, older app in LG WebOS, app on an ios and android. The only app that cannot connect is this new version of the LG WebOS app.
Why is the option to revert to the previous version gone? I may have to go out and buy an Nvidia Shield TV Pro or some other streaming device to get my setup working again…
Thanks, that’s the same way mine is setup.
When you do that are you going straight to the PMS server running (https://IP:32400 or from https://app.plex.tv/desktop)?
It was only available during early access, which has finished and the final version of the app was published by LG.
Can you go to Network settings for the server (in Plex web), show advanced and check what if anything is entered for Custom server access URLs?
For my setup (I’m using port 32401 which passes to port 32400 in the container) I need to add the following otherwise the docker container only publishes it’s internal docker IP (and is unaware of my mapping from 32401 → 32400):
If nothing is there could you add http://IP-of-synology:32400 and save the settings, then restart the app on the TV?
Either way works fine.
Pretty short sighted removing the ability to revert… lots of people’s setups were just rendered unusable by not allowing us to use the old version.
There was nothing there. I added http://192.168.0.150:32400 as you suggested, restarted the app and still will not connect.
On my second router (192.168.18.2) I added this rule:
Triggering port: 32400 (TCP)
External port: 22700 (TCP)
On the first router (192.168.18.1) I added:
Internal host: 192.168.18.2
Protocol: TCP
Internal port number: 22700
External port number: 22700
In the TV apps (old and new) a manual connection:
IP: 192.168.18.2
Port: 22700
On the old version, that works just fine and nearby server is found. New version, no connection on nearby server, only remote.
If the VPN is running (only use that on the windows PC where PMS runs), no connection on the new version. The old version still connects without problems and detect PMS as nearby (though responds a bit slower).
XPlay auto-discovers the server.
I’ll PM you the token.
5.12.2 should resolve the manual server connection issue, allows the manual server to authenticate via token, instead of IP-only when it’s a connection to a known server. Functionally this should be similar to the server publishing an alternate address and the webOS discovering it that way or allowing the TV’s IP address access without authentication.
The relay server connection fix will also allow servers that are not accessible directly become connected (and show in Media Server Status as Indirect), which might be able to help if additional troubleshooting is needed.
This did fix it. Thank you! I’m sure a lot of people will be very happy.
The latest update fixed everything for me as well. I’m very happy this issue now has been resolved.
Edit: well, not everything. What about the subtitle-offset? Where can I find that?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
