Certificate error accessing plex on windows server x64 xxxx.plex.direct

[the_plex]

Server Version#: 1.32.0.6865 on Windows Server 2022 x64
Player Version#: chrome; firefox latest versions
Hi All,
I have issues with certificate when accessing PMS on Windows. The issue is that PMS is trying to connect to {mykey}.plex.direct, but this SAN does not exist in my certificate and throw an error, that connection is not secure. With version 1.31.x.xxxx no issues at all.
Any suggestions?

[FordGuy61]

Are you using a private certificate / your own domain?
If so: OpenSSL v3.0.0 and PMS.

For those using their own domains and certificates with PMS, PMS 1.32.0.6865 and above updates OpenSSL from v1.1.1 to v3.0.0.0.

[the_plex]

Yes, I’m using own lets encrypt certificate and everything is configured properly. I have haproxy in front which is forwarding the connection to PMS. I haven’t found this article (maybe cause it is in Linux tips). I will add SSL 3.0 and give feedback.
Thanks.

[the_plex]

thanks mate, working fine.
cheers!

[james815]

Hey the_plex, I’m having the same issue, but I’m not sure how to fix this. Did you just recreate the p12 file with the new changes? “-certpbe AES-256-CBC -keypbe AES-256-CBC -macalg SHA256” I did this, but it didn’t fix it for me. Can you let me know how you fixed this?

Thanks

[the_plex]

Hi James,
yes. I just recreate .p12 cert from my personal let’s encrypt certificate. In fact the cmdlet was not OK for me, I add another line for let’s encrypt. My cmdlet was:
sudo openssl pkcs12 -export -out /path/to/location/myplexcert.p12
-certpbe AES-256-CBC -keypbe AES-256-CBC -macalg SHA256
-inkey /etc/letsencrypt/live/mydomain.com/privkey.pem
-in /etc/letsencrypt/live/mydomain.com/cert.pem
-certfile /etc/letsencrypt/live/mydomain.com/chain.pem
-password pass:mypassword
This is linux cmdlet and \ is used to continue the command on the next row. If you use windows/powershell you have to use symbol ` instead of .