Server Version#: 1.17.1841 (ish, last for correct) Player Version#: ALL
PMS on Shield Fire TV Clients Android (and Fire tablet) Clients Media and server files on external drive Shield via ethernet to Google WiFi Mesh Point
I’m by no means a Plexpert…but I’ve tried everything I can come up with to just have Plex function normally. While it could be coincidental, I believe most of this broke with Shield Experience updates.
I have a single Plex account, and a single server running on my Shield. It’s a complicated matter, so I will simply list out some of the points of interest:
When checking the Plex web app, it’ss hit or miss as to whether or not it connects securely and flawlessly. Lately it hasn’t been willing to connect securely.
When checking the Plex Shield app, my primary user can typically see everything just fine, while all other home users either show the dreaded exclamation, or don’t recognize any active server at all. Yes, all libraries are set to be shared with these home users. When I check settings on these other home users, the Plex server shows as Stopped, and cannot be started, even though it shows as Running on the primary user.
When checking other client apps like Android, a similar issue happens. Primary user looks alright, all other users show nothing and ask to add a library.
I’ve completely cleared, reinstalled, and rescanned the Plex server more than once, to no avail.
I’ve done numerous combinations of logging in and out, and attempted to remove and reclaim the server, only to have the Claim Server button spin around, then reappear, spin around, reappear, etc.
To summarize, I’m trying to just have a normal functioning Plex Shield server with a primary user and 4 home users all working as they should, and ideally without randomly losing access to the server once they are functioning properly. A completely fresh install and all of the proper updates didn’t do the trick. To top that all off, after removing the server from my account, now I can’t even get it back even though it’s running and exists. It doesn’t show up to claim when I check directly on the local bundled app.
Unfortunately, no, it’s not going to be that easy. Currently, on the web app it tells me my server is unavailable, and the direct local bundled app currently says it can’t be reached for some reason. Sometimes it has different issues depending on logging in, logging out, etc. Plex software seems to be very finicky in that regard.
Your suggestion seems like an interesting one that for all I know could work, but currently I can’t even get in to the server properly or attempt to claim it…
UPDATE: So for some reason, even though the server had been running, it decided to stop. I just went in to the Plex Shield client app, did absolutely nothing other than click on the primary user account, and under settings the server said ‘Stopped’. 5 seconds later it said ‘Running’. So color me confused on that. Now the server shows in the web app for the main user, but won’t let me connect securely.
UPDATE #2: The Plex server stopped again, minutes after the above update. It shows up as unavailable once again even on the primary account, and it wouldn’t start when I tried to get it ‘Running’ through Plex on the Shield.
Did not yet. Seemed like that was intended to happen after I’ve made user changes, which I can’t do until I can access the server. I’ll go do it now and see if the server responds.
Roger that. We’re stepping back a bit because like you said, it’s unstable. Once it’s up for 6min, don’t bother trying to connect to it using a Player. Instead have Shield shut down the Plex Media Server if that is possible, then manually copy the log file folder, zip it up, and attach it.
NVIDIA SHIELD
When running the server on NVIDIA SHIELD, the log files are located on the internal storage.
Even hardwired to the same switch, laptop isn’t even recognizing the Shield as a networked device (yes, I turned on file transfer over network). I really, really appreciate you being kind enough to take some time to try to help me out here.
For now I’ll have to wait for additional responses and continue to just futz around and hope something magically works. Very, very disappointed in how awful Plex has been in keeping their paid product stable across all devices and throughout all updates.
Well, I’ve got my logs now. Anybody know which to check and what to look for? Or which of the many log files I should be putting out here for somebody to look at?
Zip up whatever it gave you and attach it here with your reply. It’s never certain which logs will show the problem. If you cycled the power on the Shield as requested before grabbing the logs, then we only need the ones with that timestamp or later.
I’ve done a few things since then (after the above logs).
I got rid of DNS rebinding on my Google WiFi to fix the insecure connection issue, though that didn’t actually seem to work.
I removed all users, had a family member create a Plex account, and added them as a Plex home user as opposed to the previous managed user.
Currently, client apps seem to work for primary user AND additional home user which is a tiny tiny step forward, but with a MAJOR caveat. Even though I believe I have the settings proper, the secondary home user can NOT see the Live TV & DVR section, which is a big part of our usage. As for the web app (main, not the bundle local one), it still won’t connect securely even though I’ve adjusted all the wireless settings I could think of.
I’ll have a look at the logs. Our goal would be to make the admin account work correctly with a secured connection. Then we could try again the Plex Home. There was a website article on deleting all users and creating the Plex Home again to solve weird issues like this. That’s why I suggested it, but ofc I couldn’t find the link for you :-/
EDIT: oops I should have asked you to be sure VERBOSE is off. It tends to fill the logs, but I’ll try to make some sense of them. If you get around to it, capture some again like this
Interesting. I know in some cases IPV6 has been helpful, and even strongly encouraged…but hey, you could be right. The server is rebooting. I’ll follow this up in 5-10 min when I can verify it’s up and running. I’ll either have new logs or a massive thank you.
