Server Version#: 1.32.7.7571
Player Version#: 4.116.1 - web
Remote connectivity has stopped working for some remote clients to my server unless I set Secure Connections to Preferred rather than Required. The clients that are affected are an Amazon FireStick and a Sony TV.
I’m also unable to connect to a different remote Plex server from my web client. My web client logs show this:
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] is unavailable at https://.plex.direct:32400/media/providers (Status 0)”,
“time”: “2023-10-16T12:16:21.353Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] Prevented fallback to insecure connection for ”,
“time”: “2023-10-16T12:16:21.354Z”
},
If I try and browse directly to the IP address:32400 of the remote server, I can connect but the CN of the returned certificate doesn’t match the URL used - so something has gone screwy with it.
I’m seeing this issue with the certificate CN mismatch too. Stopping Plex, removing the certificate on disk and then restarting Plex Media Server will make it recreate / retrieve the certs again. In my case though it just retrieved the same incorrect certs
I thought it might be something like that. I wonder if some remote clients have a cached certificate which is still valid and matches properly and therefore they still work.
Any idea how to revoke the certificate at source and get new ones generated?
I’ve tried rebooting the server and think it may have fixed it. Will wait until after they’ve tested properly
I’m not sure about revoking the certificates. I’ve only seen how to make Plex re-retrieve them which you can do by deleting the .p12 (or perhaps .pfx) file in the Cache directory whilst the plexmediaserver process is stopped
Think mine started failing at the end of September. I’ve found another forum post that mentions expired ssl certs due to change in supported ssl methods so I think it might be related to that.
