API Rate Limit Exceeded (429) - New Server Setup - Certificate Reset Request

Plex Media Server
1

Hi,

I’m setting up a new Plex Media Server on a remote VPS (Docker container) and have been hitting rate limits for approximately 18+ hours now.

Issue:

  • Server claims successfully and obtains a token
  • However, servers.xml returns 429 and access_tokens returns 403
  • The server appears in my account but with no accessToken, so I cannot authenticate
  • app.plex.tv shows “Not authorized - You do not have access to this server”

What I’ve tried:

  • Multiple fresh installs with new claim tokens and new machine identifiers
  • Waiting 18+ hours since first rate limit hit
  • SSH tunnel to access locally (still fails due to missing accessToken)
  • Fixed IPv6 connectivity issues (server was defaulting to broken IPv6)
  • Verified all file permissions are correct

Server details:

  • Platform: Docker (plexinc/pms-docker:latest) on Ubuntu 24.04
  • Account: Philwebb3 / philwebb3@me.com
  • Server name: PlexCloud

Log errors:
429 response from POST https://plex.tv/servers.xml
403 response from GET https://plex.tv/api/v2/server/access_tokens

Could someone from the Plex team please reset my certificate/rate limit? I’ve seen this resolved by staff in similar threads.

Thank you!

2

@phil123

Is the server on Hetzner ?
If so, you will not be able to claim it. Plex blocked Hetzner due to excessive ToS violations.

Otherwise,

  1. SSH into the host
  2. docker exec into the container
  3. Run this from inside the container.
3

Yes on Hetzner, ok wonderful. time t ostartagain somewhere else lol

4

This ToS violation should only apply to individual user accounts, not a blanket ban.

5

@Diaruemnus

AFAIK, (I’m only a contractor, not FTE), the decision to ban the entire ISP was for multiple reasons most of which were the overwhelming number of ToS violators using that provider.

This is not up for discussion or debate.