v0.7.1 — servers with newer certificates connect again

If 0.7.0 told every profile it had no access to your server, this release is for you. Some Plex servers now present a certificate that older LG televisions cannot check, and 0.7.1 can check it. Everything else in 0.7.0 is unchanged.

If 0.7.0 said every profile has no access to your server: update to 0.7.1

Since early October 2026 some Plex servers' secure addresses (*.plex.direct) chain to a newer Let's Encrypt root, ISRG Root YR, that the certificate lists of older webOS versions do not contain. On those televisions 0.7.0 could not verify the server, could not connect, and told every profile that it had no access to the server, although the server and the accounts were fine. It was confirmed on a webOS 4 set and reported from a webOS 5 set.

What to do: install v0.7.1 over the PlxNative you already have. You do not need to sign out, uninstall or delete local data, and nothing about your profiles or sign-in changes.

What is fixed, and what is not: the app now carries four Let's Encrypt roots (ISRG Root X1, X2, YR and YE). Only for a *.plex.direct address, and only after the television's own list reports that it does not know the issuer, the app repeats the check against those four. The server's name, the certificate's dates and the whole chain are still verified, verification is never switched off, and no other host is checked against the bundled roots. A server that presents its own private or self-signed root is not covered, and the message "Update PlxNative" will not help there.

Fixed

• Servers that answered were reported as "no access". Sign-in and the profile picker now tell three situations apart: the television does not trust the server's certificate, plex.tv listed your servers but none of them answered, and a real refusal (the server said that profile has no access). Each now says its own thing, so the message points at the right place. The new sentences are English only on this release.
• Trailers and other media that your server redirects elsewhere. They are followed one hop at a time, each host checked on its own, and your Plex token is not sent to the place you are redirected to.
• A television with the wrong clock can still reach a server it has verified before. If the clock is wrong enough to fail a certificate's date check, the app can use the server's remembered public key instead, which the certificate fix builds on. A system toast is intended to tell you when it does; that toast has not been seen on a television yet. The reason line and clock symbol that trunk shows on a failed Home or Library screen are not part of this release.
• Logs can be collected from a Developer Mode session. The event, crash and error logs are readable by the app's group (mode 0640), so webOS Dev Manager can fetch them on a television that is not rooted. The app scrubs local addresses from what it writes; a few lines written by the C part of the app skip that scrubbing, as SECURITY.md states, so read a log before you share it.

Compatibility

• Plays video, verified by watching it — 2019 LG sets. One television: an LG 49SM9000PLA, which reports platform release 4.10.2 (LG markets this generation as webOS 4.5). For this version it was used to check the certificate fix, not to repeat the full playback checks.
• Plays video, reported by someone else — one 2019 set and one 2021 set. Robert got playback back on a 2019 set built on LG's k5lp chip after repairing its video sandbox, running v0.6.3, on 2026-09-11: issue #74. mariotaku of webosbrew ran v0.2.1 on an LG 65UP7560AUD (platform release 6.5.2) on 2026-08-11 and got a picture: issue #22. Neither report has been repeated on this version.
• Starts, and nothing further is known — every other firmware from webOS 4.0 up is expected to start. Images from 4.4.2 to 11.2.0 were checked against this binary's libraries and symbols; the matrix is in the technical audit. That grades startup and says nothing about whether video plays.
• Does not start — webOS 3.9.2 and older. Symbols the app needs are missing there, so the process is killed before anything appears.

If your set is in the middle two groups, tell us what happened. It working is as useful a report as it failing.

Known issues

• A server that presents a self-signed or private root is still not trusted. The message says to update PlxNative, and an update does not help in that case; the server's owner has to fix it.
• The wrong-clock path and its toast have not been run on a television, and the picker's new sentences have not been seen on a real panel.
• The certificate fix was checked on one television. The same fix was confirmed by the webOS 5 reporter on a development build of trunk, not on this release.
• Every known issue in v0.7.0's note that is not mentioned above still applies.

Help test this release

If 0.7.0 said your profiles had no access to a server that is working, update and tell us whether the picker and Home now reach it. If your television's clock has been wrong, tell us whether the toast appeared. Open an issue. It working is as useful a report as it failing.

Installing

Download com.beb.plxnative_0.7.1_arm.ipk and install it with the Homebrew Channel or dev-manager-desktop. You do not need a rooted TV.

Nothing in this distribution chain is signed, so this sha256 is what tells you the file you have is the file published here:

7231a6e020da18abbdd46d6991e915deaabc96d73daddb767055b598bb04cd01  com.beb.plxnative_0.7.1_arm.ipk

Installing and checking a download covers the other assets, how to check the hash on each platform, and the Developer Mode expiry that uninstalls your apps. PlxNative is licensed GPL-3.0-or-later and bundles FFmpeg under LGPL-2.1-or-later; the complete corresponding source for both is attached to this release. Exactly what was built, verified and shipped is in the technical audit for v0.7.1.

Full Changelog: v0.7.0...v0.7.1