And that is interesting. The files I was expecting to see aren’t in there. But other files have been modified recently - so they might just be elsewhere. Or have you uninstalled/reinstalled Plex in the last few hours?
I was looking for certificate.p12. Plex gets a magic SSL certificate from the Plex mothership. On the systems I’m familiar with, it’s stored as certificate.p12 in the Cache directory. It might be elsewhere, OR, the lack of that file could be why SSL isn’t working.
Paging anybody who is familiar with the snap packages!
Let’s see what user your Plex Server is running as. Can you do this?
I did remove and reinstall plexmediaserver yesterday, in an attempt to resolve the issue. But it didn’t help. When removing it, snap made a “backup” which I restored after seeing that the reinstall didn’t help.
OK, it looks like Plex is running as root, which is … well, whatever. That might be reasonable for the snap package. (All you should take from this is that I’m not familiar with snap or these snap packages, nothing about snap itself.)
But the …/Cache/ directory was owned by root, so Plex would have permission to write there.
As far as logs go, Plex does a really good job sanitizing the Plex Token out of them. But they still contain things like your external IP address, internal IP addresses, usernames, path to your files and movies. So it’s up to you.
You could search Plex Media Server.log for “certificate” and share that, if you like. Might miss the relevant context, but it also might tell us where to look next.
@ChuckPa, I wonder if you could help. Are you the person for these packages? Is running as root normal? Where’s the certificate.p12 supposed to be, if not in Cache?
OK I’m confident that Plex not being able to find the certificate is why you can’t enable SSL/Connect Securely.
I’m equally NOT sure why it isn’t successfully fetching a certificate. I don’t know what error 429 means in this case, and hope for a response from the Plex folks now.
Aug 16, 2020 10:44:10.861 [0x7fecc2bdb700] DEBUG - CERT: Certificate or intermediate did not exist, fetching a new one.
Aug 16, 2020 10:44:10.861 [0x7fecc2bdb700] DEBUG - HTTP requesting POST https://plex.tv/devices/5369507eef9145786cd313cfa2e81519af2167bb/certificate?version=2&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Aug 16, 2020 10:44:11.076 [0x7fecc2bdb700] DEBUG - HTTP 429 response from POST https://plex.tv/devices/5369507eef9145786cd313cfa2e81519af2167bb/certificate?version=2&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Aug 16, 2020 10:44:11.077 [0x7fecc2bdb700] ERROR - CERT: Could not fetch certificate from the cloud: 429
429 would normally mean that a web server was annoyed with you for making too many requests too quickly.
It’s POSSIBLE that Plex has some rate limiting around certificate requests, and that your server did make too many requests, at some point, when you were testing/upgrading/changing things. If so it might calm down and work again “soon”.
But you said this was a while ago? Or it’s also possible something funny is going on, and they need to kick it for you.
Well, I’m not really sure when it started. I’m been at home all summer since June, and didn’t personally have problems or notice it until I was back at work this Wednesday. Though a friend and my brother who I share my libraries with, claim it’s been like this all summer. That is about the time I got the new isp. Had problems with my last isp and was without internet for a week before the new one got connected. First week in June I think.
Nah. If it hasn’t fixed itself by now, I don’t think leaving it off for a day will make any difference.
You don’t want to enter any credentials on an unsecured page, but the biggest risk of not running Plex with SSL is that your ISP could, if they’re inspecting your traffic, see what movies you’re watching remotely.
That hasn’t been a huge issue in the US, most people just want to stay private in case. I don’t know what the rules are in the EU.
Yes, thank you! Tested from outside and inside network and from plex.tv. It all works now. Though in Firefox on android I get a messege something like “certificate not trusted, proceed anyway”. But it does work!
Yeah browsing by IP you will get the cert error but using the fqdn assigned by plex it will work without error. Just make sure your remote access works for you and your friends and you should be good.
@Volts Yeah I didn’t do anything, that 429 you saw was the issue and the plex cloud must have eventually stopped giving the 429 and he got a good cert.
