PMS stuck in certificate acquisition loop - Persistent API Rate Limit Exceeded (Error 429)

Plex Media Server
1

My Plex Media Server has been unable to acquire a certificate for several days. I have tried waiting over 48 hours, restarting the service, and even manually clearing the Cache/OCSP directory and backing up the cert-v2.p12 files, but the server immediately hits a rate limit upon restart.

Environment:
OS:* Ubuntu 24.04.4 LTS (Noble)
Plex Version:* 1.43.1.10611-1e34174b1
Server ID:* a36e2623836dd9279f2cd3090e009afcefcffe0f (from logs)

Log Findings:
Every time the server starts, it attempts to fetch a new certificate and fails with a 429 error:

1 > DEBUG - CERT: Certificate did not exist, fetching a new one.
2 > DEBUG - [HCl#16] HTTP requesting PUT
  https://plex.tv/api/v2/devices/[ID]/certificate/csr?reason=missing&invalidIn=0
3 > DEBUG - [HttpClient/HCl#16] HTTP/1.1 (0.0s) 429 response from PUT ...
4 > ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
5 > <errors>
6 >   <error code="1003" message="API rate limit exceeded" status="429"/>
7 > </errors>
8 > ```
9 >

Steps Taken:

  1. Waited multiple days for the rate limit to reset.
  2. Restarted the plexmediaserver service multiple times.
  3. Stopped the service, cleared Cache/OCSP/*, and renamed cert-v2.p12.old to force a fresh request.

Despite these steps, the 429 error is returned instantly. It seems my server is “stuck” in a rate-limited state on the Plex side. Could an admin please check if there is a block on my server ID or if there’s another way to force a reset? Thanks!

2

Please stop and restart your server now.

3

That did it. Thank you very much!