Server Version#: 1.32.5.7516 Player Version#: 1.59.1.3398 Hi, I’m using the docker version of PMS on a RHEL based Linux (Rocky). Plex in general is working quite well but I would like to use my own certificate. What I did: Created a certificate with RSA 4K and put in in a p12 Mounted this p12…

I got pretty much the same, but it works on mine. Docker container on Ubuntu 22.04 SSL cert from Letsencrypt automatically generated and updated from my reverse proxy Convert that into a pkcs12 format and copied it to the data directory Add the password for the cert Add your custom domain name bel…

I’ve looked again at the permissions and on the file they were 755. But the owner was not correct (using rootless docker). After changing the owner and group to the subuid/subgid the user inside was plex insted of “nouser”. Unfortunately this didn’t fix the issue. @MatthKarl You mentioned someth…

Regarding the https. When I first accessed the server in my browser via the IP address, it used he http protocol. Once I added the cert information, silly me, only changed the IP address to the domain name, but didn’t add the s to http in front to switch to an encrypted protocol. And I kept wonderin…

Okay you just mean in the browser as an protocol. This I have already checked and I still get the self signed cert instead of the correct one. I could only forward http from IIS (Reverse proxy) to plex but then there wouldn’t be encryption all the way (what I want to have). As I’m quite strict IIS…

The first thing you have to check is, whether you get the https working if you connect direct, without the proxy. Once that is done, you figure out, how to add the proxy.

Yes, that is true and that’s what I’ve tried to accomplish. The proxy is the second step. But exactly there lies the issue. I do not know why this doesn’t work even though I already got it to work once on a windows system (without docker). But for certain reasons I have to change to linux.

So what happens when you connect direct?

That what I explained further up. Connecting directly only gives me the self-signed (*.[hexnumber].plex.direct) cert instead of the correct one. I’ve tried it also with icognito to be sure no cache is interfering but still the same.

Well, here is my setup. Feel free to compare it with yours. This is the docker run command: docker run -d \ --name=Plex \ --restart=unless-stopped \ -p 32400:32400/tcp \ -p 8324:8324/tcp \ -p 32469:32469/tcp \ -p 1900:1900/udp \ -p 32410:32410/udp \ -p 32412:32412/udp \ -p 32413…

I figured out that plex has some issues reading the cert. After applying a fix mentioned here one error message about enveloping was gone. But now I still have the following error message even in DEBUG and I won’t get any more infos: Sep 27, 2023 17:32:03.319 [140503353031312] DEBUG - [CERT] Subj…

PMS on docker: Certificate not taken

Plex Media Server

nightmare1942 September 27, 2023, 6:24pm 12

Okay I’ve found the issue.
It was a P12 problem. Somehow it wasn’t build so plex could understand as it uses libs from openssl v3.

So I’m using openssl as mentioned on this page. Now it works.

Topic		Replies	Views
Custom domain ssl does not work after update to server version 1.42.1.10060-4e8b05daf Plex Media Server server-docker	43	558	November 11, 2025
Moving Plex DSM package to container certificate issue Help Plex Media Server server-docker , server-synology	1	40	June 24, 2024
PMS SSL Uses *.plex.direct Let's Encrypt SSL certificate instead of custom configured certificate Plex Media Server server-linux , networking	11	549	November 3, 2023
Certificate error accessing plex on windows server x64 xxxx.plex.direct Plex Media Server server-windows , plex-web , player-windows	6	329	July 19, 2023
Add custom ssl certs, now available for everyone. How to? General Discussions	33	33514	January 7, 2020

PMS on docker: Certificate not taken

Related topics