Plex Employee to Reset Server Certificate? "API rate limit exceeded" error

PM sent.

I don’t know if a reset of my Certificate would help me, but if you think so i would like to give it a try.
I moved my PMS to new hardware a couple of months ago and i have some issues while trying to stream remotely. Works on my lan.
Seeing this error in the logs:
[CERT] TLS connection from 192.168.1.11:1384 came in with unrecognized plex.direct SNI name ‘192-168-1-11.285b0c681a254657982a9c3d9fde3813.plex.direct’; using installed plex.direct cert

And if you do, do i need to remove the cert-v2.p12 file or will it update automatically?

Cheers
jonsjo

I’m having the same issue as others. Can I get my cert reset please @ChuckPa ?

@ChuckPa

Receiving this error in the PMS log.

Apr 05, 2023 10:21:41.622 [3332] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>


I’ve temporarily renamed the cert-v2.p12 files and restarted but still receiving same error. Please advise. Thanks!

After having my server stopped for about an hour it came back up and acquired a new cert. I don’t know if you reset it or not @ChuckPa but the problem has been resolved.

@kmount4 @ehupp

It was not announced in the release notes;

PMS 1.32.0 switched to openSSL v3.

The result of this is that some hosts will have initial flutters.

There was a big problem with Windows hosts. I think that’s resolved but don’t know whether PlexPass was replaced or not.

Linux hosts fared a bit better in this.

Anyone with their own domain/cert needs to make changes to the certificate generation as the most common encryption methods were deprecated by v3

@kmount4

I have reset your server certificate . Restart the server then restart the clients.

@ChuckPa

Much appreciated. Back in business!

Thanks for the quick reply @ChuckPa . I have restarted the server and it’s working fine now.
Have a great one.

@ChuckPa I’m Getting the cert error, filling up the logs for my Windows plex server. All of my clients get an error about connecting due to this, I assume. Not using any custom certs or anything like that.

Tried renaming the p12 cert in the cache folder for the plex media server, but still having the same issue. Tried rebooting the machine as well, just in case.

Apr 05, 2023 15:28:09.633 [16328] ERROR - [CERT] CERT: Error acquiring new certificate: Failed to upload CSR: 429, error code=“1003” message=“API rate limit exceeded” status=“429”
/errors

@jjflanigan

Your server consumed a whole bunch of certificates in one day.

You should only need 1 per month.

I can send you the details if you wish.

I have reset your certificate. Please restart the server and all clients.

edit: was thinking ‘months’ but wrote ‘day’. apologies.

@ChuckPa

Is that something I can somehow control or need to change? I haven’t changed the configuration or anything on the server (other than the most recent version update to 1.32.0.6865). It’s pretty much a straight “install and run” on Windows without any real tweaks or customizations.

I restarted the server and the clients and everything appears to be working again now, thank you.

If I should change anything to prevent this from happening again, I’ll happily do so.

This is a small issue with 1.32.0.

It impacts a few users. Engineering has already addressed it and implemented the correction for 1.32.1.

1 Like

You help me last time - hopefully again? I had a hardware crash, did the best to follow the migration info at https://support.plex.tv/articles/201370363-move-an-install-to-another-system/ and on start, seeing the "Apr 15, 2023 17:57:41.693 [8120] ERROR - [CERT] CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?> 

" errors. Could you reset again for me please?

Certificate reset.

Restart the server.

Don’t know what you’re moving from or two but your certificate was maxxed out for today . Gotta be more careful

Thanks! Not sure what that means (old server was offline, and on the new I could see the Plex Server Log constantly retrying the cert although I wasn’t doing anything other than starting the service for the first time 
)

@ChuckPa

Would you be able to reset mine as well? I’m not using a custom certificate but it seems to have gotten stuck when I upgraded to 1.32.0 about an hour ago, guessing 1.32.1 isn’t released yet as .0 was the latest stable release on the site.

@CFarence

restart the server and devices.

the certificate has been reset

Hello @ChuckPa

Is it possible to reset it for me too? Same issue than @CFarence, no more certificate after upgrade to 1.32.0.6918.

I am not able anymore to access my content from app.plex.tv (and the iOS) but this is working fine in local and with the public IP.

Thank you very much!

@azn0viet

I"ve reset your cert as well.

Restart the server

I had plex stopped until I got the all clear from you and when I started it back up it calmed it down for about a minute, then went right back into a loop trying to get a certificate. Eventually it started to get the “API rate limit exceeded” again. Right now it’s just spamming this over and over again

Apr 17, 2023 02:41:06.135 [0x7fba7b4f5b38] ERROR - [CERT] PKCS12_parse failed: error:0308010C:digital envelope routines::unsupported
Apr 17, 2023 02:41:06.135 [0x7fba7b4f5b38] ERROR - [CERT] Found a certificate, but couldn’t install it.
Apr 17, 2023 02:41:06.135 [0x7fba7b4f5b38] DEBUG - [CERT] CERT: Forcing refresh.
Apr 17, 2023 02:41:06.137 [0x7fba7b4f5b38] ERROR - [CERT] PKCS12_parse failed: error:0308010C:digital envelope routines::unsupported
Apr 17, 2023 02:41:06.137 [0x7fba7b4f5b38] DEBUG - [CERT] CERT: Unable to parse existing certificate, fetching a new one.
Apr 17, 2023 02:41:06.137 [0x7fba7b4f5b38] DEBUG - [CERT/HCl#13d] HTTP requesting GET https://plex.tv/api/v2/devices/{id}/certificate/subject
Apr 17, 2023 02:41:06.248 [0x7fba7aac7b38] DEBUG - [HttpClient/HCl#13d] HTTP/2.0 (0.1s) 200 response from GET https://plex.tv/api/v2/devices/{id}/certificate/subject (reused)
Apr 17, 2023 02:41:06.690 [0x7fba7b4f5b38] DEBUG - [CERT/HCl#13e] HTTP requesting PUT https://plex.tv/api/v2/devices/{id}/certificate/csr?reason=unreadable&invalidIn=0
Apr 17, 2023 02:41:06.795 [0x7fba7aac7b38] DEBUG - [HttpClient/HCl#13e] HTTP/2.0 (0.1s) 429 response from PUT https://plex.tv/api/v2/devices/{id}/certificate/csr?reason=unreadable&invalidIn=0 (reused)
Apr 17, 2023 02:41:06.796 [0x7fba7b4f5b38] ERROR - [CERT] CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>