LG plex player suddenly not connecting to working servers

My TV is a OLED55B8 and runs WebOS 4.4. However, using the built in browser, I can successfully access any website that uses Let’s Encrypt, including my self hosted services.

Why the built in browser is able to do so, but Plex not?

I’d like a technical response.

2 Likes

Exactly, i did few test and seems it is not LG fault, other apps able too access plex server. It plex and they refuse to at least answer this. If this is LG issue we can target LG for fix. BUT for now all proof shows it is PLEX issue.

Update: LG Web Browser unable to load letencrpyt cert page. So this is likely LG fault but PLEX can easily fix it like other browser to embed root cert into the plex.

Indeed. LG is still actively updating 2018 OLED TVs, I received an update the last month.
I’m sure there is something more behind this story, and I’m also sure there’s a real fix.

Start reporting to LG since PLEX claim that it is LG issue

I suggest everyone here should start calling their LG support.

Does anyone else have the issue whereby Changing the Secure Connection to Disabled in the Plex server results in IOS devices not being able to connect to the Server.
Thanks in Advance

Ok found the fix,

Confirmed this works. Thanks for the info!

This didn’t work for me. the Plex app on my OLED55E6V (AKA: the E6) won’t connect to my PMS I set the server and app settings to allow insecure connections but that had no effect.

What else can I do? I’ve added my comments to the LG Web OS forum. I imagine it will fall on deaf ears. Seems crazy, and it’s infuriating, that these things happen to relatively new devices that cost £1000’s. Smacks of built-in obsolescence. This should be illegal.

1 Like

Just set to always the « allow insecure Connections »

Do we have any clear movement on this yet?

Are we 100% sure Plex is right and it’s LG’s issue?

Do we know if Plex themselves have contacted LG on this issue?

LG are the second-largest TV manufacture on the planet (behind Samsung), you would think solving this issue would be a priority?

Here is what happened.

I verified the issue is cause but the letsencrypt cert expired. Check LG other team and confirm the cert on LG Webos 3.5 Cert expired. Yes, we are 100% sure it is cert expired issue.

I contacted LG customer service - reply. We will forward the issue to the relevant department
I contacted LG developers - reply. Plex need to embed the cert bundle in their app. I posted the link in another post.

As for now, we don’t have any clear solution, nobody wants to make effort.
Who wanna start class action sue LG for not updating OS less that 2 years old?
I would say start reporting to LG in your country and demand a fix.

3 Likes

I’ve tried the “unsecured server” solution, as suggested pr the email, but it still doesn’t work for me. Can’t connect to the server at all. Every other device in my home is fine, it’s just the LG TV.
I guess I can’t really blame Plex for this. It’s LG who decided to let their security certificates lapse, just because they don’t want to support “old” (3 year old) TVs.

1 Like

This resolved my issue :+1::+1: thanks

On the face of it, that’s crazy…

How can LG expect a client app to install a new certificate for WebOS? - am I missing something here?

Time to dump this on my LG retailer (the people I have a purchase agreement with) and let them argue it out…

Can somebody come up with the right technical wording to present to them, please?

Thanks!

OK, got onto LG (UK)…

After well over an hour of back and forth, this is what they said (after I suggested they seemed not to want to support these TV’s any more):

That is not the case, no, we do still provide updates to our older models and they are still supported. The C8 that you have will not be upgraded to a later Web OS version as these are built into the mainboard of the TV and cannot be changed. As for the certificate, speaking with my Technical Team, they have advised that this is something we suggest raising feedback about as we have not been informed of any issues related to this. If you would like, I can raise a VOC (Voice of Customer) to my Head Office regarding this issue for you. This will be an internal process that submits feedback regarding any issue with either products or services that you may have. This will not receive a response unless we require more information from you.

I’m pushing them to escalate this internally, as they (the Aftersales Team) are in the dark (or so they are saying).

Might help of a few more people get on their case?

there are TWO places that must be set to allow for the insecure connections.

the plex SERVER must be set to PREFERRED

the plex client/TV must be set to ALWAYS (sometimes in TWO options as indicated @ LG plex player suddenly not connecting to working servers - #31 by jadance

ALLOW insecure = ALWAYS
PREFER insecure = ALWAYS

if you are using someone else’s server, THEY must check their server settings to show:
secure connections = PREFERRED

2 Likes

Simple Solution, get an Cert from Zerossl, convert it to pfx install your own pfx in Plex
and enjoy secured Connections. Valid Domain required, no DynDns. It works :slight_smile:
Web0s 4.0 tested and confirmed working
Web0s 4.5 tested and confirmed working

Can you detail how to do that?

check below :wink:

https://forums.plex.tv/t/player-issues-after-30-of-september-and-how-to-get-back-secured-connection-and-no-more-playback-errors/749234

I am having the problem on a webOS 5.10 system… I really don’t want to go the insecure route if I can avoid it.

U got Firmware 5.10.25 I Guess not webos 5.10, link in the Post before fixes it.