Everything is currently working but I’ve looked in my logs (attached) and it looks like I’m regularly seeing the following:
CERT: Certificate did not exist, fetching a new one.
It then takes multiple attempts to retrieve a new certificate:
CERT: Downloaded new cert from plex.tv; took 12 tries.
Not sure if this helps but thought I’d check if this was at all expected behaviour?
Thanks for the info. I also didn’t understand why the certificate didn’t exist in the first place. I can’t see anything wrong with the network set up and it appears to be getting through eventually so I’ll try factory resetting the shield in case it’s an installation issue and see if that makes a difference.
Hi I am having the same issue my web will not work says cant connect secure but can browse to my private address. Can you please reset my cert on your end?
Sorry to pile on but I’m also getting TLS handshake errors. In addition to not being able to connect to my server remotely, when I manually browse to my server locally using SSL I get certificate errors. Can I have my cert reset too?
Edit: Could it be that this is related to the ongoing partial Plex DNS outage? Thinking that the clients might not be able to resolve the obfuscated name in the cert and maybe that’s my problem.
For everyone who just started experiencing this problem: There is currently a partial Plex DNS outage, and it very well might be affecting us. Just in case, keep an eye on the status of the outage here: