It’s not clear to me whether we have to request a certificate refresh as well as waiting for the outage to be resolved and server restarted? So, please confirm we all just have to sit and wait.
Do you mind elaborating on what plex.direct DNS is and how/why it’s affection functionality? Why is it that even my android app set to connect with a manual connection w/ my server manually port forwarded can’t connect?
plex.direct is how PMS and Plex.tv identify every host , independent of location (local or remote) by a FQDN which always has an IP address assigned.
Locally, it overlays the LAN and resolves to the LAN IP/
When out in the WAN space, that same name resolves to the WAN IP of the server.
This is how mobile apps seemlessly trasition from local → remote. The mechanism is used Plex-wide for sharing servers because it removes all IP addresses from what the apps see (it handles ISP DHCP changes intrinsically)
Normal service has been restored.
Update: I’m not sure if any Plex Employees did anything, but I’m able to connect to my Plex server via plex.tv now. Original request follows:
I was getting rate limit errors yesterday, but now I’m getting:
Jul 19, 2021 14:07:54.881 [6324] ERROR - CERT: Error acquiring new certificate: Failed to retrieve cert from plex.tv: 502,
Jul 19, 2021 14:07:54.887 [8420] DEBUG - [CERT] MyPlex: Last published value didn't change, we're done.
And when I try to connect via plex.tv, I get the error
app.plex.tv is unable to connect to "GANON" securely
I’m not sure if this means I need to have my cert reset.
I’m having the same rate limit log message, and unable to access plex via the web app
attached logs, I might need a reset as well @ChuckPa can you help?
logs.tar.gz (37.5 KB)
Jordan, you may restart your server
Sage, I reset both servers’ certificates. You may restart both.
I think i need to have my certificate reset as well, not sure though, but it looks like it. ??
Im moving server, and starting from scratch.
And i am getting this error : WARN - [CERT] TLS connection came in with unrecognized plex.direct SNI name ‘46-232-210-60.f92a22c3df114e0483e78730f7ff10ed.plex.direct’; using installed plex.direct cert
And this error : WARN - [CERT] TLS connection came in with unrecognized plex.direct SNI name ‘46-232-210-60.f92a22c3df114e0483e78730f7ff10ed.plex.direct’; using installed plex.direct cert
Plex Media Server.log (29.5 KB)
EDIT :
My email is correct, But my Username here on the Forum isnt the same as my Plx username.
Plex username is Kp1003.
Just in case you need it.
-
I have reset your certificate. Please restart the server
-
While there, I cleaned out all those dead (deleted) Docker containers.
Same issue for me. on version 1.24.0.4897
Plex Media Server.1.log (4.1 MB)
MODERATOR EDIT Certificate removed
That log doesn’t show me the certificate.
- Restart the server
- Wait 2 minutes
- Download the logs
- Attach that ZIP file
I also have issues connecting to my server from plex.tv. (unreachable. Make sure it’s running, double check your network, and try again.)
I get > WARN - [CERT] TLS connection came in with unrecognized plex.direct SNI name ‘---.9654c0d5b9334819804015ecf20c92a2.plex.direct’; using installed plex.direct cert
Plex Media Server.log (2.7 KB)
Can you please reset my certificate?
Thank you sir.
Seems to up and running again, and even better than before 
Next time? don’t forget to clean up after yourself ? 
any ideas? Now I cannot connect locally either
@ChuckPa It would be great if support could help me with this issue as well.
@davdev – Cleaned up and reset . You may restart the server
@vivid.water – Also cleaned up those servers you had deleted then reset the certificate. You may restart the server.
@ChuckPa Thanks a lot, its working as it should now.
