Plex Server Registration Issue

Plex Media Server
1

Server Version#: 1.43.1.10903-e5521bd8c
Player Version#: 4.160.0

Hi there,

I am experiencing a recurring issue where a Windows Plex Media Server successfully claims to my Plex account, appears normally for a while, and then disappears from the account’s server list.

Environment

Plex Media Server:

  • Windows 11

  • PMS version: 1.43.4.10903-e5521bd8c

  • Server name: Gator’s NAS

  • Machine identifier: 172b39e2f46c3984760c431319f068967d23a978

  • LAN address: 192.168.1.209

  • Plex port: 32400

There is also a second Plex Media Server on the same Plex account named “Tillie.” Tillie continues to appear normally when Gator disappears.

What happens

Gator was successfully reclaimed and initially appeared normally in Plex alongside Tillie.

Local /identity immediately after claiming showed:

claimed = 1
machineIdentifier = 172b39e2f46c3984760c431319f068967d23a978
version = 1.43.4.10903-e5521bd8c

Later, Gator disappeared again from Plex’s server list.

The server itself did NOT go offline.

From another PC on the LAN:

  • Ping to 192.168.1.209 succeeds with 0% loss.

  • TCP connection to 192.168.1.209:32400 succeeds.

  • Plex Web can be opened directly at the server’s LAN address.

On Gator itself, /identity still reports:

claimed = 1

The machine identifier is also unchanged.

Account token is valid

Using the current PlexOnlineToken stored by PMS, I tested:

https://plex.tv/api/resources

The request returns:

HTTP Status: 200

So the account token itself is accepted by Plex.

However, querying the returned Plex resources shows only my other server:

name: Tillie
owned: 1
presence: 1

Gator is completely absent from the Plex resource list.

Server-specific Plex endpoint returns 403

Using the same current token against:

https://servers.plex.tv/api/v2/server/access_tokens

returns:

HTTP Status: 403

Plex Media Server itself is seeing the same response.

Relevant PMS log entries include repeated instances of:

HTTP/2.0 403 response from GET https://servers.plex.tv/api/v2/server/access_tokens

MyPlex: Error 403 requesting XML from:
https://servers.plex.tv/api/v2/server/access_tokens

MyPlex: Couldn’t get list of access tokens from myPlex.

There are also repeated 403 responses for:

https://servers.plex.tv/api/v2/server/users/services

Later, PMS logs:

MyPlex: mapping state set to ‘Mapped - Not Published’.
MyPlex: Last published value didn’t change, we’re done.

Remote Access

While Gator is missing from the Plex account’s resource list, Gator’s Remote Access page reports:

“Fully accessible outside your network”

So the server is still running, reachable, claimed, and reports successful Remote Access.

Previous claim/authentication cleanup

Before the current claim, the old PlexOnlineToken had become invalid and returned HTTP 401.

I backed up the Plex registry settings and removed only:

  • PlexOnlineHome

  • PlexOnlineMail

  • PlexOnlineToken

  • PlexOnlineUsername

I then restarted PMS and confirmed:

claimed = 0

The machine identifier remained unchanged.

I used the normal Plex claim/sign-in process to reclaim the server. Afterward:

claimed = 1

The machine identifier was still unchanged, and the newly issued PlexOnlineToken successfully returned HTTP 200 from the general Plex API.

Gator initially appeared normally in Plex after this reclaim.

It subsequently disappeared again.

Current reproducible state

At present:

  • PMS is running normally.

  • Gator is reachable over the LAN.

  • TCP port 32400 is reachable.

  • /identity reports claimed=1.

  • Machine identifier has not changed.

  • The current Plex account token returns HTTP 200 from the general Plex API.

  • Remote Access reports Fully Accessible.

  • /api/resources contains Tillie but not Gator.

  • /api/v2/server/access_tokens returns HTTP 403.

  • PMS logs the same server access-token 403 errors.

  • PMS reports “Mapped - Not Published.”

I have not reinstalled PMS or deleted/reset the Plex database. I have also avoided repeatedly reclaiming the server so that the failed state remains available for diagnosis.

Is there a Plex backend/server-resource issue that could cause a successfully claimed server’s machine identifier to lose its server registration or server-specific authorization while its Plex account token remains valid?

I can provide sanitized Plex Media Server logs covering the successful claim through the subsequent 403 errors and disappearance if needed.

Thanks in advance