I have a custom domain—let’s call it mydomain.com, a QNAP NAS with the most recent version of Plex installed, and a wildcard SSL cert— *.mydomain.com that I’d like to use for Plex. My domain is set up with DDNS and my QNAP is signed and updating accurately. The QNAP also has the *.mydomain.com cert configured on the main webpage and I can get to it via nas.mydomain.com with it working perfectly. So far, so good.
When I open the Plex app from the NAS, it defaults to HTTP, as expected (it gives me a warning saying as much). Following Plex’s instructions here, I set up Plex to use HTTPS and currently prefer secure connections. However, I cannot get to the HTTPS page with the wildcard cert working. Instead, I get a notification that the connection is not private and that the cert is for *.STRING-OF-RANDOM NUMBERS-AND-CHARACTERS.plex.direct—obviously not my custom domain.
When I ssh into my NAS and check the Plex logs, an error message shows: “ERROR - CERT: Found a user-provided certificate, but couldn’t install it.”
I know that I successfully chained the domain cert, CA cert, and private key together as a PFK file and uploaded to the NAS—it’s the same cert used for the main NAS webpage though the storage location for Plex is different than for the main page. Within the Plex app, I’ve pointed it to the Custom cert path on the NAS at /Web/ssl/*.mydomain.com.pfx and I’ve entered the correct password used for the encryption key and the custom certificate domain is set as plex.mydomain.com—all of which seems to be correct given the cert is a wildcard.
More info: Router is setup correctly with 32400 ports forwarding and Remote Access available.
