Server Version#: 1.42.2.10156
Player Version#: 5.93.2
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Hi team,
I’m reporting a reproducible login issue with the Plex client on Philips 6000-series TVs running TitanOS. After linking the device via plex.tv/link, the app loops straight back to the login screen instead of proceeding to the home interface.
Environment
TV model: Philips 6000 Series (TitanOS)
Plex client version: 5.93.2
OS version: TitanOS TPN257E_V057.002.236.141
Network: Wired LAN, stable connection verified
Steps to Reproduce
Launch Plex on TitanOS TV.
Receive 4-character linking code.
Enter code at [plex.tv/link] while logged into Plex account.
Browser confirms successful link.
TV Plex app briefly refreshes, then returns to the sign-in screen.
Expected Behavior
TV client should authenticate and proceed to the Plex home UI.
Actual Behavior
App remains in an authentication loop. Device never registers as linked in account settings.
Troubleshooting Attempted
Attempted to clear cache & data in app but nothing happens when I click to reset it, I assume due to the limited opreation of the app.
Attempted to reinstall Plex but it seems to not be possible due to the locked down nature of the TV OS.
Power-cycled TV and router.
Verified successful login on other Plex clients (Windows, mobile, Fire Stick).
Retried multiple new device codes — same result.
Analysis
Appears to be a token persistence failure in the TitanOS Plex client post-OAuth. Other users have confirmed identical symptoms across TitanOS models, suggesting outdated or unsupported app code relative to Plex’s current authentication flow.
Request
Please confirm whether TitanOS builds of Plex are still officially supported.
If supported, can you escalate for review or update scheduling?
If deprecated, can Plex communicate that publicly so Philips/TitanOS users can plan accordingly?
Thanks in advance for escalating this to the appropriate dev team.
The article was updated earlier this year (it looks like TitanOS was released last year); but of course, that doesn’t mean it’s the gospel.
You may want to ensure your Plex Media Server’s Network → Secure connections setting is configured to Preferred (instead of required) as well.
My understanding of Plex’s smart TV apps is that they load via a launcher which is in essence a glorified web browser (or perhaps a container would be a more apt description), with some supporting slightly deeper integration than others (per the linked article).
Thank you for responding, the TV model is 40PFS6000/12 and the TV seems to be manufactured this year.
From the article it does seems like you are correct, nothing after 2021 is supported. Also it does seem like the TV is using the “Plex for smart TVs” app so I hoped I can have at least some usability but it seems like I won’t.
I have the Secured connection setting set to preferred and I did try to manually link the server using the internal IP in the plex client settings but I just got a message that something went wrong. several times so I just gave up.
Sorry you’ve had issues. What you describe is definitely unexpected with that app and we’ve been unable to reproduce similar behavior ourselves. If you’re still having issues here, then our dev team did have a request to help gather more information.
In the smart TV app, go to Settings > Advanced
Enable the Show console log overlay option there
Take a video of the TV screen while you reproduce the issue with the 4-character code linking sign-in not working
Upload the video to somewhere like Google Drive or similar
Share a link to the video in a new reply here in the topic
The hope is that the logs from the overlay will have something useful.
Thank you for the steps, It seems that everything is now working. I talked over email with someone from Plex accessebility and they told me that the issue was due to some errors in the authentication API servers and that the issue was fixed. I waited a couple days and tried today, I was able to log in normally.
