Force reload… (if using a browser – Control+F5)
force restart apps. (don’t just close and reopen)
Force reload… (if using a browser – Control+F5)
force restart apps. (don’t just close and reopen)
This has nothing to do with the apps or a browser. These are the Plex logs on startup. Please escalate to someone that can help.
It’s been a while since I had this issue. But chuck resets and reissues new certificate and also clears multiple servers setup from what I remember. Somehow my plex server creates multiple servers or something on the back end of things not visible to us and chuckpa needs to clear them. We need to delete the cert out of folder. He then resets the cert and reissues.
Still not sure what causes it though. But it usually happens when I’m troubleshooting something else in plex. And I delete pms folder and start over or just leave database file in folder and let it regenerate.
Hope this helps…
Please confirm DEBUG logging is enabled, VERBOSE logging is disabled. SAVE if you make changes.
Restart PMS, wait 2 minutes, download the logs ZIP file and attach it here.
What I now see at Plex.tv for “megara” is where the server keeps asking for more certificates.
Coupling a second 429 and this:
Jun 08, 2023 21:15:23.310 [140026378238608] DEBUG - [CERT] CERT: Unable to parse existing certificate, fetching a new one.
most oftent means it can’ SAVE the new certificate locally and is fetching new with each restart.
To remedy this, referencing from your docker container perspective:
/config/Library/Application Support/Plex Media Server/Cache/cert-v2.dat
I have again reset your certificate.
I watched the new certificate generate; which is now ready for your server to download.
Other: I’m quite capable of taking care of this issue.
There is absolutely NO NEED to delete the whole thing and start over.
This is not a ‘Nuclear option’ scenario. ![]()
/config/Library/Application Support/Plex Media Server/Cache/cert-v2.dat does not exist. Closest thing is cert-v2.p12 and a number of cert-v2.p12.tmp.{UUID strings} files.
Plex user has all the needed write permissions. I can see files created by plex uid in this dir with timestamp only a few hours ago when I stopped Plex.
After rm cert-v2.p12* and restarting it was able to get a new cert and appears to be working as expected.
DEBUG - [CERT] Installed certificate with fingerprint …
Thanx.
typo on my part. Sorry
( a lot happening here )
Don’t think I suggested for them to delete everything. Was suggesting what might have triggered it, since you could never figure it out
and for some reason after multiple back forth comments to get the certificate to work again. You eventually found there was multiple servers created which only showed on the back end of things only visible to you not the customer. I guess it’s job security ![]()
![]()
![]()
![]()
.
And since this is the only issue tech support has eventually resolved for me. I wouldn’t be laughing at someone who would suggest to nuke and start over. Even though I was saying I was nuking everything in the folder but the database to troubleshoot any issues with plex because there is simple little to no help from tech support. So at least we the customers are trying to troubleshoot your software. ![]()
![]()
![]()
![]()
![]()
![]()
![]()
whatever floats your ![]()
Have a nice weekend.
Can you please do this for me?
Mac mini is current and only server
I see a fresh newly minted cert for your server, and no errors