Server Version#: 1.24.5.5160
Player Version#: 4.68.0
I was able to get a Custom certificate setup with a custom certificate domain, and I can see after logging out and logging in that my traffic is being properly routed through this domain and this cert.
However, after a few hours, I see the traffic is returning to using *plex.direct until I log out and log back in again.
Is there anyway to set my server to never use plex.direct and always use my domain?
In a word? No.
plex.direct is required by the Plex apps and Plex server for Client-Server communication on the LAN. It’s how Plex does its own DynDNS.
If you look at NAS vendors, such as QNAP and Synology, they have a quickconnect.to type domain which does the same thing except, in Plex’s case, Plex applies and utilizes the attached certificate to keep all communication secure.
@ChuckPa but plex allows you to use your own domain, secured with your own SSL for the communication.
And it does work properly, until x amount of time has passed then requests revert back to plex.direct. Which defeats the purpose of using your own Custom certificate domain.
Yes you can use your own cert & FQDN.
You use it as a secondary (added on to) Plex.
By doing this, Plex will accept incoming traffic with your certificate attached
Then, after initial contact and validation, will fip-flop back and forth between your cert and Plex’s cert as needed for the particular task.
The P12 you give Plex must include Key, Cert, and CA to that Cert
openssl pkcs12 -export -out my-fqdn.p12 -inkey my-fqdn.key -in my-fqdn-production.crt -certfile "Acmecert_+O=Let's+Encrypt,+CN=R3,+C=US.crt"
Disable remote access and it will stop using the *.plex.direct address. As long as your domain is filled in to the “Custom Server access URLs” setting, everything will use that address, including remote access.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
