My goal is to use the Plexamp iOS client to play music hosted by my Plex Media Server on a private network.
I created a separate plexamp.mydomain.com URL because my understanding is that the Plexamp API runs on port 32500 rather than the web UI port of 32400.
Is this correct or does the Plexamp client also connect to port 32400?
Then surely you are operating the Plexamp using the touch screen of the iOS device. So there is still no reason to have remote access to the iOS device. All that is needed is a connection between the iOS device and your Plex server.
i.e. the Plex server needs to be remotely accessible
Sorry for the confusion. Maybe the title of this post is confusing? “Plexamp Remote Access” is a reference to the remote access client, not server.
http://plexamp.mydomain.com is not an endpoint to the Plexamp client. Rather it is an endpoint to the Plex Server API listening on port 32500. i.e. the server port dedicated to Plexamp.
i.e. that’s the URL I need the Plexamp iOS client to connect to.
There is no server port dedicated to Plexamp. Plexamp behaves like all regular Plex clients. It talks to port 32400 of the server in a local network, and whichever port has been set in the server configuration for remote networks.
You asked where to find the remote access settings of your server… and that’s where they are. You’ll probably need the Network settings too in order to configure your custom access domain.
All that being said… Otto’s point is still valid. You don’t need to expose your server via a second subdomain dedicated to Plexamp. Plexamp will connect using the regular server remote access configuration (with or without a custom access URL).
To add to the above: you will likely need to use the “Custom server access URLs”
If you have client and server separated into different VLANs or somesuch, you will need to do more custom configuration and routing.
Do also verify that the plex.direct domain is resolving to the local server IP on the client network.
It is likely that your DNS resolver is applying “DNS rebinding protection”, which is a good thing, in general. However, due to how the plex.direct domain is used, you need an exception from this protection. How that is done in common DNS server software is alo covered in the linked article.
The plex.direct domain is both used when using the automatically established remote access (per UPnP), as well as when accessing your own plex server from within the same local network where the Plex server is situated.
It comes automatically with a fitting security certificate for both local and remote access.
If – for remote access – you have defined a custom IP address or domain name for the exposed port of your plex server, it is not used.
If you use a custom domain name, you will have to supply your own, publicly trusted (i.e. not self-signed) security certificate for it and put it into the Plex server “Network” configuration page.
That applies to all kinds of “tunneling” solutions.
