If configured the Custom server access url will be registered at Plex's pub/sub service and clients will only get this url presented in the future.
The only way to "fully" levarage the QC address is to take care of the TLS certificates yourself and register is as "Custom server access url". Once PlexWeb is loaded in your browser it will query the server list and try the shortest path - if you are within your lan, it will use a generated plex domain name that resolves to your internal ip (it's their trick to align the domain name with the https certificate they create for you) - but this requires to add an exlcusion for "plex.direct" in your your router's DNS-Rebind protection. There is no benefit in not using Plex instead. Unfortunately, i am seeing a lot of Spinng wheel when i try to play a video. Afair the first setup must be done from a local ip, once the server is claimed with your account and remote access is configured, the PMS instance will register itself at Plex's pub/sub service, which is used by clients to know how to contant your PMS instance.Įven if you manage to use a QC address to access Plex, It will "just" load the PlexWeb client stuff from the PMS instance and nothing else. I have plex server (version 1.-1) running on a Linux machine and the Nvidia Shield acting as a client.
0 kommentar(er)
