ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429

I have been trying to install my own custom ssl certificate (using a local root CA that I use internally), and it hasn’t been going well. This is probably my fault, and I am still learning exactly what I need in my ssl certificate for the PMS to let it use the local cert.

In doing this, I have been restarting the plex server and resetting the Cache as I try to debug the issue. Unfortunately, doing so has caused a 429 error with uploading the LetsEncrypt CSR. In retrospect, I see how I caused this, but I don’t know how to proceed to reset the process. Do I just wait? Do I need help?

-Greg

You cannot use self-signed certificates.
You must use publicly accepted certificates, like those from Letsencrypt etc. This is what Plex uses by default, btw.
You get a personal cert automatically from Plex. Why do you need your own?

https://support.plex.tv/articles/200430283-network/

As I mentioned above, I’m still learning about certificates. I’m also new to Plex. I have my plex server at 10.0.5.x behind my lan and direct access to that IP throws an ssl error. I was simply trying to remove that error as I have done with other devices using a self-signed cert with my own rootCA cert registered on all my devices. My hope was that Plex could use my cert for local connections and whichever cert Plex preferred for the central server.

I don’t doubt that you are right about not needing to do this. I was just trying to neaten up some internal bits while learning about the certificate process. What I didn’t realize was that my playing around was taxing an external server when I failed. It wasn’t my intent to be pinging LetsEncrypt for new certificates.

I didn’t imply that this is the case.
All I’m saying is, that using your own certs will make things more complicated, instead of easier to diagnose.

  1. make sure you didn’t “require” secure connections on your server. (1st setting here: https://support.plex.tv/articles/200430283-network/)
  2. Make sure your local DNS resolver (usually in your router) is not applying “DNS rebinding protection” to the domain plex.direct
    See detail information about that in here: https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/

Thank you for these tips. I removed my custom certificate (and no longer require secure connections).

My inference that I am pinging an external server is coming from the 429 error in the log files:

Nov 19, 2024 07:41:33.528 ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>


Am I interpreting this incorrectly?

…and thank you, I really do appreciate your attention to this question and your generosity in linking me to the right resources.

Having now read the linked articles and (many) other posts on this forum about a similar error, it seems like I made a couple mistakes that led me here:

  1. Trying to use a self-signed cert. My self-signed cert (which included my ip address) was not recognized by plex and then defaulted to the LetsEncrypt cert. The rejection of my self-signed cert was fairly silent so I didn’t know what the issue was leading to my trying repeatedly. Or at least, I didn’t see the error.

  2. From other posts here, I was deleting my Cache while trying to get my cert to work. Unbeknownst to me, this was generating a csr upload for a cert renewal on each restart. This put me over some threshold on the plex server.

At this point, it seems that my certificate account likely needs to be reset. I see on some older posts @ChuckPa has been able to do this in similar situations.

I had no idea I was generating repeated renewal requests.

@gse1977

quite the mess in there…

I reset it. Cert generated and ready to go

Restart the server.

Thank you. I appreciate it. I now know what I was doing that was driving the repeated csr requests as I messed with the cache. I apologize. I did not know that my swapping certificates and restarting the server was generating external CSR requests using plex resources. I assumed (wrongly) that everything was local.

It is now working again.