Custom domain ssl does not work after update to server version 1.32.0.6918

Server Version#: 1.32.0.6918
I used to love plex and have a custom domain using port 32400 to access it locally and remotely, too (by using split dns settings on my router).
The certificate is supplied by Let’s Encrypt now for ages. This used to work perfectly.
Now I did the last server version update (running on a QNAP NAS, btw) and it broke. I can only access plex via browser using https://app.plex.tv.
Going via https://my.domain.com:32400 results in an SSL mismatch as something…plex.direct is the cert and not the right address though.
Apps on iOS and Android do still work and the dashboard says I have a secured connection to the server but what is going on here? Why is my cert not used any more but an arbitrary third-party one?

See OpenSSL v3.0.0 and PMS.

1 Like

Ah i see, thank you!
I just dug up the logs. After I found out in which file I should search for it I noticed these lines:

ERROR - [CERT] PKCS12_parse failed: error:0308010C:digital envelope routines::unsupported
ERROR - [CERT] Found a user-provided certificate, but couldn’t install it.

and right after that that I stumbled upon SSL became broken after latest PMS Update - #14 by plentyoftimeto69

So yes, I just made that assumption and you pointed me that out.
My pfx-file is causing the issue. Will try to make a new p12 file tomorrow. But I won’t enter a password as command parameter at any time if I can avoid it :wink:

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.