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

reset @CeriousAurelius

reset @maxt1967

thank you!

Hi I have this API rate limit exceeded and I just see my server offline
kindly assist

Hey there !
Facing the same issue with certificate renewal.
Could you please reset my certs also ? :slight_smile:

Thx a lot !

I am having the same issue. HDD crashed so I had to get a new one and reinstall the server. It happens every day to me. Can you reset my certs?

Hi There,

Facing the Cert renewal issue like other -

CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>

Could I get it reset please?

Thank you kindly.

I’m getting the same error :
CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
Could I get it reset?
thanks

Hi!

Same issue here. My server has been reinstalled, and my family member’s iPad does not recognize new server. I reinstalled the app on the iPad, since then, I cannot sign in with error message: “API rate limit exceeded!”

Can a Plex employee reset the cert for my server: Dell OptiPlex?

Thank you and I wish you a merry christmas!

I need my cert reset please.

EDIT: Nevermind, I deleted the server and started from scratch without importing previous instance settings. Thanks.

Hi, I am experiencing the same issue after moving my plex instance from Centos to Rocky Linux.

Anyone can help to reset the certificate issue so I can use app.plex.tv.

CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>

Looking for a certificate reset for my server as well after having moved it to another computer. Cannot delete cert-v2.p12 as it doesn’t exist in the data directory/cache.

I experienced this issue as well. Typically the API limit should auto reset after X time. It took about an hour before the certificate was redownloaded and installed. I moved my app data contents from one windows machine to another and experienced this. Not sure why the hard lock, but Im sure its something to do with me forgetting to move the registry keys as well.

just moved my server to a new nuc11 and am now getting this issue. plex is working for remote users, and on some of my devices but not on the web app nor my PS5 (which apparently requires secure connections). Thinking a reset may be needed?

error:
CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>

I have just moved my server from Windows to Linux and have problems with clients using the old certificate. Please can you reset the certificates on my account? Thanks in advance.

TLS connection from 10.10.10.10:53213 came in with unrecognized plex.direct SNI name '10-10-10-15.<oldhash>.plex.direct'; using installed plex.direct cert

I’m having the same issue and think i need a cert reset @BigWheel @ChuckPa
ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>


@dTos it is reset. you might have to restart your server.

Thank you muchly! All good again on this side! :slight_smile:

Hi
I guess i have also messed up with Preferences.xml moving my Plex directory.
Log file is filling out with:
Feb 03, 2022 23:33:11.581 [0x8076c5a00] WARN - [CERT] TLS connection from 192.168.0.179:61571 came in with unrecognized plex.direct SNI name ‘192-168-0-100.87ff9281ec2946c89c4867876f2233bf.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:33:25.129 [0x8076c5a00] WARN - [CERT] TLS connection from 192.168.0.179:61578 came in with unrecognized plex.direct SNI name ‘192-168-0-100.c34db42929dc4089a46b0e0c076cf31e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:33:42.769 [0x8076c6e00] WARN - [CERT] TLS connection from 192.168.0.179:61590 came in with unrecognized plex.direct SNI name ‘192-168-0-100.87ff9281ec2946c89c4867876f2233bf.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:33:55.850 [0x8076c5a00] WARN - [CERT] TLS connection from 192.168.0.179:61596 came in with unrecognized plex.direct SNI name ‘192-168-0-100.c34db42929dc4089a46b0e0c076cf31e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:34:13.492 [0x8076c6e00] WARN - [CERT] TLS connection from 192.168.0.179:61609 came in with unrecognized plex.direct SNI name ‘192-168-0-100.87ff9281ec2946c89c4867876f2233bf.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:34:26.570 [0x8076c6e00] WARN - [CERT] TLS connection from 192.168.0.179:49249 came in with unrecognized plex.direct SNI name ‘192-168-0-100.c34db42929dc4089a46b0e0c076cf31e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:34:44.211 [0x8076c6e00] WARN - [CERT] TLS connection from 192.168.0.179:49262 came in with unrecognized plex.direct SNI name ‘192-168-0-100.87ff9281ec2946c89c4867876f2233bf.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:34:57.291 [0x8076c5a00] WARN - [CERT] TLS connection from 192.168.0.179:49268 came in with unrecognized plex.direct SNI name ‘192-168-0-100.c34db42929dc4089a46b0e0c076cf31e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:35:13.259 [0x8076c6e00] WARN - [CERT] TLS connection from 192.168.0.179:49281 came in with unrecognized plex.direct SNI name ‘192-168-0-100.87ff9281ec2946c89c4867876f2233bf.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:35:27.795 [0x8076c6e00] WARN - [CERT] TLS connection from 192.168.0.179:49307 came in with unrecognized plex.direct SNI name ‘192-168-0-100.c34db42929dc4089a46b0e0c076cf31e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:35:44.452 [0x8076c6e00] WARN - [CERT] TLS connection from 192.168.0.179:49319 came in with unrecognized plex.direct SNI name ‘192-168-0-100.87ff9281ec2946c89c4867876f2233bf.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:35:58.491 [0x8076c5a00] WARN - [CERT] TLS connection from 192.168.0.179:49327 came in with unrecognized plex.direct SNI name ‘192-168-0-100.c34db42929dc4089a46b0e0c076cf31e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:36:15.051 [0x8076c6e00] WARN - [CERT] TLS connection from 192.168.0.179:49346 came in with unrecognized plex.direct SNI name ‘192-168-0-100.87ff9281ec2946c89c4867876f2233bf.plex.direct’; using installed plex.direct cert
Feb 03, 2022 23:36:29.013 [0x8076c6e00] WARN - [CERT] TLS connection from 192.168.0.179:49350 came in with unrecognized plex.direct SNI name ‘192-168-0-100.c34db42929dc4089a46b0e0c076cf31e.plex.direct’; using installed plex.direct cert

Also I tried deleting cert-v2.p12 but this won’t help.

Can you please? :slight_smile:

thx!

Same issue here and think i need a cert reset @BigWheel @ChuckPa

CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>