Secure remote access with my custom domain

Server Version#: 1.25.6.5577 (QNAP NAS)
Player Version#: Plex web provided with the server (Cannot find version number).

Hi everyone,

I have a custom domain which is mapped to my home IP address using duckdns. On my router, I have forwarded a port to the plex instance. I have set up a p12 certificate for that domain and added it to the plex settings.

Unfortunately, it seems that sometimes, when I log on to Plex, I still get the following certificate issue (see attached image) where the plex https certificate is used rather than my own one for my own domain. I don’t really know how to force plex to use the right certificate. Suggestions would be welcome!

It would be really useful to get this sorted, it seems it sometimes impacts on certificate authentication with third party apps too, so I’d like to get it resolved if possible.

James

have you entered you custom domain at the bottom of the networks page, too? Also, if plex is running on a subdomain, is that subdomain covered by your cert (wildcard or explicit)? might be, that plex sees you cert, but doesn’t use it cause it doesn’t match.
Also check your logs on start up. It usually says “importing cert”, “overriding cert with user supplied cert” and such. it’s one of the first 50 lines usually

1 Like

As a Custom server access URL?

This shouldn’t be necessary because Plex automatically publishes the Custom certificate domain to the Plex cloud.

It also shouldn’t be necessary if accessing Plex directly in a browser.

That’s a great question. Plex uses SNI to determine which certificate to serve. If what’s requested by the browser doesn’t exactly match the Custom certificate domain, the default certificate (.plex.direct) will be used instead.

:+1:

Also look for - I’m trying to find an example - log messages about “a request for a hostname that wasn’t recognized”.

Thanks both.

Some fiddling with these settings appears to have fixed this.

I have multiple subdomains pointing to the same IP, and all explicitly stated on the same certificate.

However, I think I wasn’t always using the subdomain that I had set on the Plex network settings to access the plex server remotely.

I’m not sure, but it doesn’t seem possible to access one server through multiple custom domains? (And it also isn’t very necessary; except in a silly edge case I had, which in sure I can work around!).

I am using Custom server access URLs in the form https://My.CustomSub.Domain:CustomPort as I’m not accessing through the default SSL port (443).
Anyway, right now it appears to be it working ok, apart from the fact that remote access occasionally reports as unavailable. (But when I test it, it always works)

Plex uses the Custom certificate domain to set up TLS SNI, so it can deliver the certificate associated with the requested domain.

I haven’t tried entering multiple domains in that field, but I don’t expect it to work with multiple entries.

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