Server Version#: 1.42.2.10156-f737b826c
OS Version#: Debian 11 (Bullseye) / Remote Host
I am reporting a persistent and localized HTTP 429 (Too Many Requests) error originating from the Plex authentication servers. This block is preventing my server from completing its security handshake and is resulting in a “Not Authorized” loop.
Despite leaving the server offline for several hours to allow for a natural cooldown, the moment the service is started, it is immediately met with a 429 response when attempting to publish the server mapping state.
Confirmed Log Evidence:
text
[HttpClient] HTTP/1.1 429 response from POST https://plex.tv/servers.xml
MyPlex: Published Mapping State response was 429
WARN MyPlex: Invalid response when mapping state (code=429)
Technical Details:
- Environment: The server is a remote host accessed via a secure SSH tunnel mapping local port to 32400.
- Attempted Fixes: I have performed a complete “clean-slate” reset of Preferences.xml, removing all existing MachineIDs and Tokens. However, since the server cannot talk to plex.tv/servers.xml without being throttled, it cannot generate a new valid certificate.
- Impact: The server appears in my “Authorized Devices” list on my account, but because of the 429 error, the local identity is never validated, making the server unusable.
Request:
Please manually reset the throttle/rate-limit for my account and my server’s IP address. This appears to be a “sticky” block that is not clearing automatically. I need to be able to claim the server and establish a secure connection without being immediately flagged by the anti-spam system.
