"API rate limit exceeded" When Getting Certificate

Server Version#: 1.22.1.4228
Player Version#: 1.29.1.1974-a65b3ef3

One of my servers can get a certificate without a problem. The other can’t. Users can’t connect to the server (app.plex.tv is unable to connect to “Plex 1” securely). Secure Connections set to Preferred.

Mar 25, 2021 16:50:18.037 [0xa3efe430] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>

<error code=“1003” message=“API rate limit exceeded”/

Rate limiting occurs when PMS queries for an updated certificate and, for whatever reason (usually file permissions) can’t save and use that certificate.

The other common reason why it can’t obtain its own certificate is if a host certificate is superseding what PMS has by default. HTTPS fails but Plex.tv will remember the IP.

After confirming file permissions (owner:group) of all the files in “Library” are as they should be ( a sudo chown -R plex:plex takes care of it in short order)

and letting PMS sit idle.

A certificate can be downloaded.

I might be able to help if efforts can be coordinated. (I can reset what exists if PMS has been stopped for a while. This will clear the counters so it can then pull correctly that first time)

How long should I shut down PMS? I shut all of them down for an hour and restarted just one. Still getting the rate limit exceeded.

Thanks.

@MarkJH

Normal rate limiting idle time required to clear throttling is that the API will remove the limit 24 hours after first triggered.

So if it was first throttled at noon, and persisted for several hours, shutdown until noon the next day is the normal self-clearing time.

I see you have several servers. which one is having this problem?

Plex 1, Plex 3, Plex 5 can’t get the certificates.
Plex 2 and Plex 4 are fine.
Is there a way to keep PMS running, but not have it try and get a certificate for a day to avoid the rate limit?

There is no method to keep PMS from requesting a certificate.
It needs that certificate for HTTPS communication with Plex.tv and your users.

Knowing which machines are having trouble we can reset them, one at a time and bring them back online.

Did you check the file ownership & permissions in /var/lib/plexmediaserver ?
I find it very odd that everyone for you went out at the same time. What changed on your end?

Knowing the worst case is the machine might need be off for several hours , which would you like me to reset first ?

I did chown on all of the servers. I don’t think anything changed on my end. Starting with Plex 1, then 3, then 5 would work.

I have reset “Plex 1”.

While there, I removed the duplicate of “Plex 1” which has been idle for over a year and also has no shares or users attached.

You may restart “Plex 1”

If it doesn’t get a cert, power it down and let sit for several hours (4) and then try again.

Plex 1 was able to get a certificate!

I have reset “Plex 3”.

You may now restart it.

Plex 3 was able to get a certificate!

Plex 5 has been reset.

You may now restart it.

They all have certificates. Thanks for your help!

Glad I could help.

This is happening again on my Plex 1. Any idea why?

@MarkJH

What changed on the server ? Freshly issued certificates don’t ask for a new one spontaneously 3 days after having been issued

No change other than additional content added. No config changes.

Looking at the logs, it looks like it could not find the certificate at 1:07 am. There was a short power failure on the system. Possibly got corrupted with the power failure?

That’s possible.

Still , it should not be stuck in 'Generating" status.

Certificate reset.

Restart the server.