I recently migrated my Plex Media Server to a new machine (“Falkenstein”, a Hetzner host) as part of a home-lab move. Since the migration, the new server cannot complete registration with plex.tv.
The specific failure: the server’s “Published Mapping State” call to plex.tv returns HTTP 429 (Too Many Requests) on every attempt. This has now persisted for 17+ hours and re-triggers on every server restart. As a result the server shows as “not authorized” / “not available” in the Plex apps and web, and it cannot be claimed or used for remote access.
- Account: alexander@szeremeta.org
- Server name: Falkenstein
- Current machineIdentifier:
ad3a2662b58ca0f379fba05bdb32f226322c3ddc
Likely cause: during the migration there was rapid server-identity churn — the machineIdentifier was changed / re-registered several times in a short window, and an old server briefly shared an identity. I believe that tripped the rate limiter on the mapping-publish endpoint into a sustained ban tied to this account/server.
What I have already tried, all still returning 429:
- Left the server completely untouched for 17+ hours
- Configured manual port-forwarding
- Enabled Plex Relay
- Generated a fresh, clean server identity
The 429 persists regardless, so this looks like a server-side limiter that will not clear on its own within a normal cooldown.
What I’m asking for:
- A manual reset / clearing of the rate-limit ban on the “Published Mapping State” (device/resource mapping publish) endpoint for this account and server, so the new server can finish registering and obtain remote access.
- Guidance on the recommended cooldown period and the correct migration procedure to avoid re-tripping this limiter (e.g., how to move to new hardware without identity churn).
I’m happy to provide full Plex Media Server logs or run any diagnostic you need. Thank you for the help.
