Plex server cannot claim — PlexOnlineToken resets to empty, /api/servers returns size="0"

Plex Media Server
1

Server Version#:v1.41.6.9685-d301f511a - Synology DS920+ x86_64 - build: linux-x86_64 synology-dsm72
Player Version#:N/A
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I’m running Plex Media Server on Synology. After an identity reset, the server will not claim.
Symptoms:

  • PlexOnlineToken resets to empty on every startup

  • Identity reset completed successfully (new MachineIdentifier + ProcessedMachineIdentifier)

  • accounts table cleared — SELECT * FROM accounts returns zero rows

  • WAL/SHM removed — db-shm/db-wal deleted

  • Preferences.xml edited correctly with fresh claim token

  • NAS can reach Plex.tv — curl to /api/claim returns expected 404

  • /api/servers returns size=“0” with my X-Plex-Token

  • Cloud UI always shows server unreachable

  • Local UI never shows claim prompt

Everything local is clean and working. The server runs normally, but Plex.tv rejects the claim handshake and wipes the token.

I believe my Plex account is in a backend‑locked state and needs the hidden server identity record cleared.
Please advise

2

Remove whatever you added to Preferences.xml.

Then try FAQ 31:

Has nothing to do with claiming a server.

3

Hi, thank you for the suggestion. I’ve actually already performed the identity reset, DB cleanup, and claim token injection manually. /api/servers returns size=“0” for my account, which indicates a backend identity lock. I’m waiting for Plex staff to review and clear the hidden server record.

4

Run the FAQ. If it does not work, provide a screenshot of the error message.

5

I think the main thing was this querying https://plex.tv/api/servers with my X-Plex-Token returns:
(tried to include xml here but it gets redacted)

The size=”0” says that plex.tv says I own zero servers in the backend registry and so it rejects any attempts for my NAS to claim itself.

Of course AI is helping me and isn’t always reliable, but this seems to be a definitive thing. In the meantime I’ll see if there’s any more in the FAQ, thanks.

6

Don’t. It is giving you incorrect information.

Adding a claim token to preferences.xml will not work. Delete it from the file.

Deleting / modifying any of the db files will not work (and may damage the db).

The server is unclaimed, so it is removed from your account.

Run the FAQ. If it doesn’t work, provide a screenshot of the message and a copy of the server log files.

3 Likes
7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.