Cannot claim server after migration - Error 403/429 in logs (Docker, Ubuntu 24.04)

Plex Media Server
1

Hello Plex community,

I’m experiencing a critical issue where I cannot claim my Plex server after migrating to a new host. Even a fresh Docker installation without any data backup results in the same error.

Environment:

  • OS: Ubuntu 24.04 (Noble)

  • Setup: Docker (official plexinc/pms-docker image)

  • Network: Host mode

  • Scenario: Migrated from old server to new server, but also tested with completely fresh install (deleted /config folder) - same result

Problem Description: When attempting to claim the server (either via PLEX_CLAIM environment variable or manually through web UI), the claim initially appears successful (HTTP 200), but immediately after I get “Error 403 Forbidden” and “429 Too Many Requests” errors in the logs. The web interface shows “Not authorized” / “You do not have access to this server.”

Key Log Excerpts:

Apr 04, 2026 11:30:45.723 - HTTP/1.1 (0.2s) 200 response from POST https://plex.tv/api/claim/exchange?token=... [CLAIM SUCCESS]
Apr 04, 2026 11:30:46.346 - ERROR - MyPlex: Error 403 requesting JSON from: https://plex.tv/api/v2/server/users/features
Apr 04, 2026 11:30:46.489 - DEBUG - [HttpClient/HCl#74] HTTP/1.1 (0.1s) 429 response from POST https://plex.tv/servers.xml?auth_token=...
Apr 04, 2026 11:30:46.489 - WARN - [Req#169] MyPlex: Invalid response when mapping state (code=429)
Apr 04, 2026 11:30:58.711 - ERROR - MyPlex: Error 403 requesting XML from: https://plex.tv/api/v2/server/access_tokens?auth_token=...
Apr 04, 2026 11:30:58.711 - ERROR - MyPlex: Couldn't get list of access tokens from myPlex.

The server then continuously tries to fetch access tokens but receives 403 Forbidden errors repeatedly.

What I’ve tried:

  1. Deleted entire /config directory and started fresh - same issue

  2. Used brand new claim tokens from plex.tv/claim (multiple attempts)

  3. Removed all PlexOnline* entries from Preferences.xml and restarted

  4. Ensured proper permissions (PLEX_UID/GID matching host user)

  5. Tested with both network_mode: host and bridge networking

Questions:

  1. Is this a rate limit (429) that will resolve itself, or has my account been banned/restricted?

  2. If it’s a rate limit, how long should I wait? It’s been ongoing for several hours now.

  3. Is there a way to reset my claim status or lift the restriction?

Any help would be greatly appreciated. I’m happy to provide full logs privately if needed.

Thank you!

2

Is your server hosted at Hetzner?

3

yes its an dedicated Server by Hetzner

4

Plex, Inc. has banned all Hetzner IPs.

5

Really? I had it running successfully on a Hetzner Cloud KVM server.That’s really strange. but okay any other provider suggestions for server with igpu cpus ? Thanks for the quick reply !

6

See Not Allowed to use Hetzner

7

Hi,
I am having issues with my PLEX server, running on a Synology NAS after installing the latest update. I had to do a reinstall, and now I cannot claim my server. I have tried many times with not success. Help would be much appreciated.