Must reclaim server every Monday morning

Plex Media Server
1

Server Version#: 1.43.0.10467
Player Version#: 1.112.0.359-0d79a49f

I had the server certificate issue a while back that was preventing remote access, and Otto revoked the certificate and everything has worked mostly well since then.

The problem now is that every Monday morning (every week), I have to reclaim my server to get everything working again. This was not an issue until the certificate revocation thing happened.

Everything else works fine, and remote access is fine until seemingly the week-long “timer” runs out. These two things seem to be related, given the timing.

Any insights? TIA!

2

bump for engagement

3

This now happens after an update as well. Anyone have any clue what could be happening here?

@OttoKerner, you have any ideas?

(please pardon me if it isn’t kosher to @ you, but you’re the wizard and I’m at a total loss here!)

4

server logs shortly after this happens?

5

Thank you for your response, and apologies for the delay. I had to wait for the issue to happen again!

Logs are attached! Thank you!

Plex Media Server Logs_2026-04-27_13-12-47.zip (4.5 MB)

6

What time did you re-claim the server?

7

Right after those logs. Here are the logs post-reclaim -

Plex Media Server Logs_2026-04-27_13-13-29.zip (4.5 MB)

8

Looking at logs I am seeing ERROR - Error creating directory "/temp": Permission denied along with WARN - Error scanning directory, we'll skip and continue: boost::filesystem::last_write_time: No such file or directory [system:2]: the temp might be related but the second isnt.

Im not seeing anything that jumps out other than it appears you were running scheduled tasks right before the incident. I would check your /temp permissions as a start.

9

Plex Media Server.1.log: Apr 27, 2026 05:00:12.396 [23215192943416] DEBUG - Ordered to stop server.
Plex Media Server.log: Apr 27, 2026 06:09:49.931 [23391602309776] DEBUG - BPQ: [Idle] -> [Starting]

The server was shutdown at 0500, then restarted at 0609.

What was the reason for the shutdown/restart?

Was this you, some form of automation, something else?


It appears that “something” happens during the shutdown/restart period.

After the restart, Plex Media Server receives “Unauthorized” messages (http code 401) when trying to retrieve features from plex.tv (checking to see if you have a Plex Pass to enable those features).

The process continues every five minutes:

Apr 27, 2026 06:09:53.996 [23391061797688] DEBUG - [HttpClient/HCl#6] HTTP/1.1 (0.0s) 401 response from GET https://plex.tv/api/v2/server/users/features?filterFeatures[]=b83c8dc9-5a01-4b7a-a7c9-5870c8a6e21b&filterFeatures[]=926bc176-58ca-47da-b8e3-080ed14ea6ba&filterFeatures[]=ea791163-c28d-4b7c-af88-bcc9553b206d&filterFeatures[]=6ab6677b-ad9b-444f-9ca1-b8027d05b3e1&filterFeatures[]=56cd352b-0d47-436d-aced-f20db3508de5 (reused)
Apr 27, 2026 06:09:53.996 [23391020596024] ERROR - MyPlex: Error 401 requesting JSON from: https://plex.tv/api/v2/server/users/features?filterFeatures[]=b83c8dc9-5a01-4b7a-a7c9-5870c8a6e21b&filterFeatures[]=926bc176-58ca-47da-b8e3-080ed14ea6ba&filterFeatures[]=ea791163-c28d-4b7c-af88-bcc9553b206d&filterFeatures[]=6ab6677b-ad9b-444f-9ca1-b8027d05b3e1&filterFeatures[]=56cd352b-0d47-436d-aced-f20db3508de5
Apr 27, 2026 06:09:53.996 [23391040547640] WARN - FeatureManager: Couldn't get features. Trying again soon.

...

Apr 27, 2026 13:10:23.579 [23391061797688] DEBUG - [HttpClient/HCl#398] HTTP/1.1 (0.0s) 401 response from GET https://plex.tv/api/v2/server/users/features?filterFeatures[]=b83c8dc9-5a01-4b7a-a7c9-5870c8a6e21b&filterFeatures[]=926bc176-58ca-47da-b8e3-080ed14ea6ba&filterFeatures[]=ea791163-c28d-4b7c-af88-bcc9553b206d&filterFeatures[]=6ab6677b-ad9b-444f-9ca1-b8027d05b3e1&filterFeatures[]=56cd352b-0d47-436d-aced-f20db3508de5 (reused)
Apr 27, 2026 13:10:23.579 [23391044840248] ERROR - MyPlex: Error 401 requesting JSON from: https://plex.tv/api/v2/server/users/features?filterFeatures[]=b83c8dc9-5a01-4b7a-a7c9-5870c8a6e21b&filterFeatures[]=926bc176-58ca-47da-b8e3-080ed14ea6ba&filterFeatures[]=ea791163-c28d-4b7c-af88-bcc9553b206d&filterFeatures[]=6ab6677b-ad9b-444f-9ca1-b8027d05b3e1&filterFeatures[]=56cd352b-0d47-436d-aced-f20db3508de5
Apr 27, 2026 13:10:23.579 [23391042730808] WARN - FeatureManager: Couldn't get features. Trying again soon.

Until you re-claim the server at 1313:

Apr 27, 2026 13:13:17.629 [23391044840248] DEBUG - [Req#714] MyPlex: Did token exchange for claim (returnCode: 200)
Apr 27, 2026 13:13:17.629 [23391044840248] DEBUG - [Req#714] MyPlex: Stored token xxxxxxxxxxxxxxxxxxxx
Apr 27, 2026 13:13:17.630 [23391044840248] DEBUG - [Req#714] MyPlex: Got a token poked, let's act on it.
Apr 27, 2026 13:13:17.630 [23391044840248] DEBUG - [Req#714] MyPlex: username is Funkahologram, login is <redacted>, home is 0, no pin
10

Apologies for the delay!

I was under the impression that this is how you get Plex to transcode to RAM. Is that not the case? Is there somewhere else in Unraid that would indicate how that “drive” is mapped? I’ll revisit SpaceInvader One videos!

Thanks!

11

Apologies for the delay!

We may have lost power at that time?? We have had some bad weather here lately, but I was undoubtedly asleep then! But my UPS settings are set to shutdown cleanly, so that shouldn’t have been an issue..??

I do have backup appdata running at 0500 on Mondays, but I’m not seeing an option to turn on or off an auto reboot after said backup. This seems highly coincidental though…

Mover is also running daily at 0500, but this shouldn’t interfere, right?

I’m going to change Mover to run at 0400 instead and see if there is any change.

Thanks for the help!

12

I don’t use unraid. However, I’ve not noticed any posts regarding mover affecting Plex. Still, changing mover to run at a different time is a good idea.

What is the order of events that happens at 0500 on Mondays?

Something like this?

  1. 0500: Stop Plex Media Server
  2. Run mover & backup
  3. Mover & backup finish
  4. ~0600: Start Plex Media Server

If you can do so without interrupting users, you might also try (a) manually stopping and starting Plex Media Server, (b) manually running the backup process, and (c) manually running mover. See if either one results in the Plex server becoming unclaimed.

Basic “divide and conquer” approach.

See if any individual task causes the problem. And if you can do so without disrupting users, you don’t have to wait for Monday mornings.