@ChuckPa I use the acme.sh script with letsencrypt. I get an “intermediate CA cert” and a “full chain cert” file. Which one should I use with the certfile option in openssl?
This is the error I am getting:
Aug 06, 2025 21:05:01.114 [140572162636432] DEBUG - [CERT] Subject name is /CN=*.stuff.plex.direct
Aug 06, 2025 21:05:01.114 [140572162636432] DEBUG - [CERT] Installed certificate with fingerprint ##:##
Aug 06, 2025 21:05:01.114 [140572162636432] DEBUG - [CERT/OCSP] no URL available
Aug 06, 2025 21:05:01.114 [140572162636432] WARN - [CERT/OCSP] getCertInfo failed; skipping stapling
Aug 06, 2025 21:05:01.114 [140572162636432] ERROR - [CERT] Found a user-provided certificate, but couldn't install it.
When I create the certificate using the acme.sh script, when I specify the domain, I use -d *.mydomain.com because I want not only plex.mydomain.com but anything.mydomain.com. So in the Settings->Network, what should I use for the “Custom certificate domain”?
When you get an ACME cert, it’s based on the CA from the provider.
That CA is all you need with your CRT and KEY.
“Full Chain” stuff ie messy.
Also … DO NOT supersede plex.direct. You will break it. plex.direct is an INTERNAL domain, tied to your Plex-issued cert, which expires every 30 days, and is used by PMS and players for DDNS resolution
Okay, I tried that and it didn’t work. Should I upload my logs?
About the plex direct stuff, I edited the log. I wasn’t sure if that and the fingerprint are supposed to be private, so I just obscured the log when I posted it here. I did not mess with the plex.direct stuff in reality.