Server Version#:1.42.2.10156
Player Version#:Plex lifetime pass
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
I was in the process of updating my Plex server, and did a bunch of changes which looked to trigger disruptions with how Plex was interacting with my server. Eventually, my SSL.connection stopped working. Now, my logs show 429. It’s been almost 24 hours. I thought it may resolve. But has yet to do so.
Any suggestions?
Looking at your account I see Ares and a deleted Ares
It look looks like Plex.tv started throttling you because of the number of certificate requests (it couldn’t write the downloaded cert in the Cache directory).
When it can’t save the cert, it asks for another upon restart.
Do that too many times before the old fall off and you get “429” throttle".
First thing to check:
STOP PMS now before Plex.tv locks you out hard.
Can the plex user (user you run PMS as --or-- ‘plex’ (default) write to the ‘Cache’ directory under ‘Plex Media Server’ ?
What would you like to do with the certs once you get the saving/permissions resolved? I can reset the certs for you so you get a fresh one. You only need be careful of Plex.tv itself locking you out for an hour.
Hi, I have stopped my plex service. waiting for further guidance as to what i need to do next.
My plex user can access/write to the Cache directory under Plex Media Serer
owner=plex group=plex mode=755 path=/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache
READ: OK
WRITE: OK
WRITE FILE: OK
READ FILE: hello
CLEANUP: OK
aresit@ares:~$
In terms of “what would I like to do with the certs”, sorry i dont really understand what you mean. I want to restore my plex service. i am not sure why at one point, plex saw two versions of my plex server (ARES), then i had to remove one, and reclaim a new one of the same name…
also, do you know what may have triggered my 429 limiting access? right now, I am in the process of trimming down my linux server, removing unnecessary services and apps.
Please get into the Cache directory,
cert-v2.p12 (perm 600)The trigger was PMS itself asking for more certificates than is reasonably allowed (you have 15+ requests)
so the folder is 755, inside the folder files are 644, the sub folders are 755.
i dont see cert-v2.p12 in this folder.
that’s the problem.
Let me reset the certificates for you and see if we can pull one.
Please start the server and let it sit completely idle.
I will watch for Plex.tv to generate a new certificate for it.
plex has been re-enabled, i wont touch it. i’ll follow up in a bit if I dont hear anything 
You have a new, and valid, certificate
Give it a go
this is great, it looks like its working. During my updates, i rebooted multiple times in a short time frame, i was removing unnecessary services, and trying to harden my server. I think all of this combined in my short time frame caused me to trigger the 429.
so for next time, a 429 issue, is this something that will resolve over time or will i have to reach out to forums for support to have it “reset” ?
If you know you’re going to reboot the host a lot,
disable PMS (systemctl disable) until you’re done
It’ll keep plex.tv from getting paranoid
Yes, 429 resolves over time
