Purging your logs made it worse. 
I’ll reset you again and we can retry
1 Like
I was able to successfully downgrade to 1.29.2.6364 and confirmed I do not have custom certificates enable nor custom host names. I do however have secure connections set to required.
That’s not a solution.
PMS 1.32.0 has new certificates openSSL v3.0.0
PMS 1.29.2 will stop working sometime after Sept 11, 2023
1 Like
Will do. I did rename the cert in the cache folder then uninstalled and reinstalled and claimed.
Still did not work and did not recreated the cert file.
Should I rename the cert the the original
I understand that, I wanted to be able to see what the current settings are, as you mentioned the one log indicated a custom certificate might be in place. However I was fairly certain I didn’t have anything custom setup.
This now confirms I’m having the issue without anything custom setup in regards to certificates.
delete the cert-v2.p12
Then give it a shot.
@ChuckPa seems like turning on debugging scared it into working. Thanks!
Was trying to get logs with debugging turned on and it grabbed a new cert and is working again.
For others, what I did was delete the cert-v2.p12 file. Start the server for about 5 min. Turn off for 10min. Turn server back on and enable debug logging. Restart server for a final time and cert file should regenerate. No idea if the amount of time mattered.
I have this running on truenas if that helps. I think the logs are clearing out after restarting the container
Works now. Weird.
I move the cert file and some other temp files out of the directory. Then started
appears that the cavalry has responded and cert issuance has been resolved…THANK YOU!
HAHAHAAHA!
You rock. We appreciate you!
Reporting all systems nominal
1 Like
Confirm, I am up and running again. Thank you guys for the hard work
1 Like
There’s one employee who can now go back to
2 Likes
FWIW - removing the cert-v2.p12 stops the CPU usage and logging. Seems to have no negative impact, I do get one occurrence of API rate limit exceeded on startup, local Plex clients work fine. Putting cert-v2.p12 reverts state and CPU load and lots of logging return.
So removing the file seems to resolve it for me, and so far no negative impact.
Thanks for the help @ChuckPa and all.
Normal behavior is for PMS to manage its internal certificate (cert-v2.p12)
I have reset the certificate for you.
Please stop PMS.
Delete the cert-v2.p12 file you have
Start PMS
It will get a fresh one.
This will allow it to get back in sync with Plex.tv by itself.
You won’t have any “API rate limited” errors.
ALL:
They are still working on it; experiencing a few bumps
“Please keep your seatbelts attached with your arms and hands inside the ride until it comes to a complete stop”
Worked perfectly! Thanks!
1 Like
Thank you very much! Yesterday I wasn’t able anymore to see the error rate limit in the logs but I wasn’t able to have the p12 certificate. After a good night for me, it is now magically working because I now have the certificate.
Thanks a lot again @ChuckPa
