Server Version#: 1.40.2.8395-c67dce28e (Ubuntu)
Player Version#: Plex for Samsung v5.81.1 / Platform v5 (Samsung TV UE43RU7170UXZT / T-MSLDEUC-1420.0)
Hello Community, I need a bit of help.
I have several devices (Android TV, Android mobile, LG TVs, Samsung TV) connected to my home Plex server.
They all work flawlessy, except for the Samsung TV that keeps randomly unlinking from Plex.
The unlinking only happens after some power off / power on cycle, never during usage (so this is not a network connection issue). It can stay linked for several days, sometimes for some weeks, but invariably there will be a time when I power on the TV and find it logged off, having to relink the device.
On the same TV I have Netflix and Amazon Prime, that don’t have the same problem.
The issue is somehow similar to this one (but I have only a single user):
I’m replying simply to report a similar or same problem.
Just got a brand new Samsung DU7200 yesterday. I assigned the TV a static IP address in my hardware firewall, updated the TV, then downloaded the Plex app. I then successfully signed in and connected to my server. Plex worked flawless through the afternoon. Later that evening, I ran the Plex app and it could not find my media server. Things I tried:
Exit the app and re-open app - Did not work
Exit app, power cycle TV - Did not work
Checked TV’s network connectivity - Fine
I even tested my ethernet cable with my network cable tester and it passed.
Ran other apps that needed network access - They worked perfectly.
At this point, I switched to the older Roku set top box I was using with my old TV, ran Plex and it worked.
Switched back to Samsung Plex app and, again, no connection to media server.
Getting frustrated, I rebooted everything, exited the Plex app, rebooted the media server, and power cycled the TV - That worked.
That was until this evening where I had the exact same problem. I didn’t bother rebooting the media server this time. I simply returned to the Roku and everything worked fine.
I hope I’ve provided enough details and troubleshooted effectively enough for somebody to be able to track down why this is happening and patch the app.
