Server Version#: 1.32.3.7089
Player Version#: Unrelated to issue.
Problem:
I had set up the “Custom server access URL” to point to a local domain that I host, given that I have slightly more control over it.
However, during testing and checking of another function I noticed that plex does something quite silly with the URL… It ■■■■■ it up!
If I for example use https://www.plex.test.net, we should automatically assume that since this is HTTPS, this uses port 443… As is normal.
What does plex do? It turns it into https://www.plex.test.net:32400 unless I specifically add :443 to the end of the url. Which now works fine with the proper port set, and errored on my console with connection errors because https isn’t reachable at 32400 at all.
The fix: Make sure these URLs automatically use the right ports based on http/https as the option itself describes. It doesn’t ever state to add a port to it, breaking the function somewhat and throwing errors.
The docs state that, if no port is specified, the port configured in the server’s remote access settings will be used. That’s consistent with the behavior I see on my own server.
There’s a little more to it than that (remote access needs to be enabled for the above to be true; otherwise the port associate with the specified custom URL’s scheme will be used).
I noticed that the logs within the dev panel on chrome/edge both give an error connecting to the URL with the :32400 attachment added to it. Adding :443 fixed it, but that is because as far as I know https will only run on 443 and nothing else, hence why the function doesn’t seem to work entirely as it should.
Could be my own brain being unable to wrap itself around it, or due to the way my proxy is configured… But I’m pretty positive it isn’t completely intended behavior.
