Seeing the same ■■■■here. My home lan access works, but outside my lan is dead because the cert is expiring and not renewing??? Plex??? What’s going on?
@OttoKerner please help?
I think I’m experiencing the same. I’ve been unable to connect outside my network for about 30 hours and I just finished all the networking troubleshooting suggestions I could find before seeing the same entry in my logs.
Please. It’s Friday night. Please don’t let this be broken all weekend. I have had friends texting me asking why Friday night movies aren’t working.
Same thing here. I was sent here by a helpful person on Reddit who mentioned this had happened before.
What’s really weird is that I have two Plex Media Servers on the same network (one for 4k only content, one for everything else) and the 4k server is fine but the other is not.
Getting this in my error logs so I’m assuming that’s what others are experiencing?
CERT: Error acquiring new certificate: Failed to upload CSR: 429
Same here
May 16, 2026 10:38:24.280 [4044] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
<errors>
<error code="1003" message="API rate limit exceeded" status="429"/>
</errors>
Same Here, 429 Rate Limit request reset
Server Version#: v1.43.1.10611-1e34174b1
Machine Identifier: c83a5daba59d120134fbfe2d8eddc5853ebf843a
Same 429 CSR issue. LAN access works, remote access broken. Log shows:
CERT: Error acquiring new certificate: Failed to upload CSR: 429
@ChuckPa @BigWheel @OttoKerner — could one of you please reset the rate limit on my account? Thanks.
I am retired as of February. I no longer have access to certificates.
I am having the same issue. I just spent 4 hours looking through all of this and it’s still the same. I have tried removing the cert-v2.p12 file from the Cache folder, and the Remote Access shows a green checkmark, but I am getting the same CERT: Error 429 as above (API rate limit exceeded).
Same issue here. 429 API rate limit exceeded retrieving updated SSL Cert.
[mod edit: Your certificate is valid and has been successfully renewed a few hours ago.]
All the other posters in here: I have reset your server certificates. They were stuck during their automated renewal process.
Please stop and restart your server(s) now.
I am having this issue as well, so whatever magic needs to happen, I would appreciate it if someone could work it on my account also!
ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429
[mod edit: please stop and restart your server now.]
EDIT: All set now, thank you!!!
Thank you. Confirmed my server renewed its cert overnight last night and was working externally this morning again.
Are these certificates supposed to renew 30 days before expiration like standard let’s encrypt stuff? I am wondering what the threshold is for “uh oh this is broken” before we get to “plex is down”.
Thanks for the info.
They are valid for ~90 days. I actually don’t know how far in advance they get renewed. But I assume it’s quite shortly before they elapse.
The issue here is not that they weren’t renewed far enough in advance. The issue was that the renewal process got stuck, for some reason.
And what has Plex done to insure this doesn’t happen yet again? This was an issue 6 months ago. It’s an issue today. Is it going to still be an issue 6 months from now? It seems like monitoring your api end point for 429 error would be an extremely simple mitigation for at least the time being… 
Sorry, I don’t have anything to share at this point.
Hey team.
Getting the same HTTP 429 response this morning, interestingly only my Apple TVs are impacted.
May 16, 2026 07:39:07.514 [139703170968376] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
<errors>
<error code="1003" message="API rate limit exceeded" status="429"/>
</errors>
On the client:
2026/05/16 07:41:57.709 (4082) 📝 PMKConnectionTestOperation.m:70 | Error during test of <PMKPlexServerConnection: 0x1096b1d60>[ 192-168-4-105.REDACTED.plex.direct:32400 - plex,published,direct,verified ] (remaining attempts 0): Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “192-168-4-105.REDACTED.plex.direct” which could put your confidential information at risk." UserInfo={NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorDomainKey=3, NSErrorPeerCertificateChainKey=(
"<cert(0x111a7e000) s: *.REDACTED.plex.direct i: E7>",
"<cert(0x111a7e800) s: E7 i: ISRG Root X1>"
), NSErrorClientCertificateStateKey=0, NSErrorFailingURLKey=https://192-168-4-105.REDACTED.plex.direct:32400/?X-Plex-Language=en-US&X-Plex-Device-Name=Apple%20TV, NSErrorFailingURLStringKey=https://192-168-4-105.REDACTED.plex.direct:32400/?X-Plex-Language=en-US&X-Plex-Device-Name=Apple%20TV, NSUnderlyingError=0x123bfb5a0 {Error Domain=kCFErrorDomainCFNetwork Code=-1202 "(null)" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x123911380>, _kCFNetworkCFStreamSSLErrorOriginalValue=-9814, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9814, kCFStreamPropertySSLPeerCertificates=(
"<cert(0x111a7e000) s: *.REDACTED.plex.direct i: E7>",
"<cert(0x111a7e800) s: E7 i: ISRG Root X1>"
)}}, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask <3A4B9610-6AE1-4AC9-AD4B-9698E40E214B>.<6>"
), _kCFStreamErrorCodeKey=-9814, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <3A4B9610-6AE1-4AC9-AD4B-9698E40E214B>.<6>, NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x123911380>, NSLocalizedDescription=The certificate for this server is invalid. You might be connecting to a server that is pretending to be “192-168-4-105.REDACTED.plex.direct” which could put your confidential information at risk.}
Quick question. If I setup custom SSL certs on a domain I own and configure to point to my server would this work around the issue?
[mod edit: you can stop and restart your server now.
Using a custom cert is supposed to avoid the issue. https://support.plex.tv/articles/200430283-network/ However, it must be a certificate which is trusted by all your client devices. These will usually only rely on certs which are provided by their manufacturer, via firmware updates.]
Edit: Thanks that resolved it.
Can’t wait, in 3 years the Cert will renew every 47 days.
# SSL Certificate Lifetimes Are Shrinking: What the New 47-Day TLS Certificate Rules Mean
