Server Version#: Version 1.32.6.7468
Now, about every day, my server randomly goes unclaimed. Why is this. What is happening you think?
Plex Media Server Logs_2023-09-15_20-41-48.zip (4.3 MB)
Also, when I reclaim, all library access is eliminated for every user in the Plex home.
This means the Preferences.xml file is being damaged.
When itâs damaged. PMS has no choice but to start over with a new ID.
Are you deleting the old servers from your account ?
If not, I very much suspect someone has access to your account and is deleting it from plex.tv because under normal conditions, I would see the duplicates but I see only one.
Next time it is unclaimed,
- Stop PMS
- Manually make a ZIP / tar.gz of the âLogsâ directory under Plex Media Server
- attach it here so I can see the last activity.
Also, I recommend changing your password and Force Sign Out all devices.
(Itâs a pain but it guarantees nobody has access except you)
yeah happened again today.
will change password and sign all devices out
Logs.zip (4.9 MB)
of note, after password change and forcing sign out of connected devices, server again asked to be reclaimed
ALSO of note, mentioned it before, every single plex home user loses access to everything every time this happens and I have to manually add access back for each user to the libraries
also, no not deleting old servers or anything like that
I see one problem right away:
Sep 16, 2023 06:53:44.387 [139625653812024] DEBUG - Completed: [192.168.6.239:52531] 401 GET /status/sessions (10 live) #23d8eb GZIP 0ms 357 bytes
Sep 16, 2023 06:53:44.394 [139625653812024] DEBUG - Auth: authenticating user as guest
Sep 16, 2023 06:53:44.394 [139625653812024] DEBUG - Request: [192.168.6.239:52532 (Subnet)] GET /status/sessions (10 live) #23d8f6 GZIP Signed-in Token ()
Sep 16, 2023 06:53:44.394 [139625653812024] DEBUG - Completed: [192.168.6.239:52532] 401 GET /status/sessions (10 live) #23d8f6 GZIP 0ms 357 bytes
Sep 16, 2023 06:53:53.637 [139625154591544] DEBUG - Request: [192.168.7.7:53543 (Subnet)] GET /:/timeline?ratingKey=163662&key=%2Flibrary%2Fmetadata%2F163662&playbackTime=25582&playQueueItemID=903022&state=paused&hasMDE=1&time=25000&duration=255000 (9 live) #23d8f5 TLS GZIP Signed-in Token (scarbrtj) (Chrome)
192.168.6.x -VS- 192.168.7.x
You and the server MUST be on the same subnet, or you ssh tunnel into it, to claim it.
If youâre not on the same subnet (your computer) then it wonât ever find it.
(UDP and broadcasts do not cross subnet boundaries)
Thatâs why you cant find it to claim it.
expressly:
Sep 16, 2023 07:14:43.203 [139625651702584] DEBUG - Completed: [192.168.6.239:54604] 401 GET /status/sessions (10 live) #23e6d6 GZIP 0ms 357 bytes
Sep 16, 2023 07:14:43.690 [139625154591544] DEBUG - Request: [192.168.7.7:53543 (Subnet)] GET /:/timeline
401 = DENIED (it will not allow crossing subnets. Itâs seeing you as âRemoteâ and saying âNO, not until claimedâ
Why do you have two subnets? You have more than 250 devices ?
Getting it claimed is never a problem. Snip snap, claimed, all is back to normal. Just over a course of a day, occasionally Iâm accessing with a client, and Plex is totally generic. Go to server, login, oh, ok, youâre unclaimed. Time to reclaim. Hit reclaim button. Rinse. Repeat.
I donât have two subnets, I have my netmask (in my router) as 255.255.254.0. Itâs been this way for years with no changes or hiccups.
For me, 192.168.6.x - 192.168.7.x are the same subnet.
But, and I donât know if this specifically addresses the problem, when I login localhost in a browser on the linux server itself (192.168.7.100), it shows unclaimed even then. It doesnât matter from what ip address Iâm accessing.
Is it possible those DENIED things were from other clients or PCs showing DENIED with the password changes and client disconnects I did?
-
Apologies on the /23 subnet . I donât see it that often.
-
It is possible those are from clients not yet signed back in. Do you know which devices they are and does the timeline make sense?
-
Lastly, This is going to be perhaps the stupidest thing but Iâve seen stranger things. Editing as appropriate for your config:
sudo bash
cd /var/lib/plexmediaserver
chown -R plex:plex . &
find . -type d -exec chmod 755 {} \; &
find . -type f -exec chmod 644 {} \; &
wait
When the prompt returns, all 3 tasks will be complete.
I run them in parallel because the directories are cached so might as well capitalize.
1 Like
Woke up this morning to unclaimed server again.
Will try the thing above. Report back. This is quite ⊠troubling.
Also, again, as usual, every user has lost access to all libraries and live tv. Have to re-add that manually for each and every user every time.
Please grab the logs right now and attach the tar.gz or ZIP
No idea whatâs happening to your machine but Iâm becoming VERY suspicious of nightly âcronâ activities
Logs.new.zip (5.0 MB)
Would having auto-update on, and recently trying beta channel, and switching back off beta channel, have anything to do with anything?
Youâre running 1.32.6.7468 right now.
That build has been rescinded due to the faults which got through.
I recommend:
- Reinstall 1.32.5.7349 (Public download if you donât have it)
- Turn off auto update until we resolve the bug
Your logs are showing a whole bunch of failures.
Yikes, ok.
Server kicked into unclaimed status again, but hadnât âdowngradedâ from 1.32.6.7468 to .7349.
So I installed 1.32.5.7349, just now, but strangely it said something about this was actually a downgrade in install.
Will report tomorrow to see if we can keep the server claimed >24h.
I wonder what next steps will beâŠ
When using DPKG to install. it tells you itâs a downgrade.
Thereâs no harm because the package already understands the metadata is stored separately
1 Like
I am glad to report the server has not unclaimed itself since the instructions you mentioned (changing the PMS version) were followed. In other words this was the first night the server didnât suddenly become unclaimed by morning.
Fingers crossed.
Server randomly went unclaimed again. Just now.
Plex Media Server Logs_2023-09-19_20-39-39.zip (4.8 MB)
While a user was watchingâŠ
Will try upgrade in public channel to new version.
Any other thoughtsâŠ
