PlexAMP v4.12.4 (headless) impossible to set player advertise URL

Plex Labs
, ,
1

I’ve installed plexamp v4.12.4, it shows up as a player from my phone, but there’s no playback possible. Then i go to the webui of the player, visible through a reverse proxy at, let’s say, https://plexamp.local.network (reverse proxy behind split-horizon DNS), pressing “Play” and no playback still. Going to network tab of developer tools I see that browser is trying to access the private IP (http://172.1.2.3:32500/resources) and not the https://plexamp.local.network/resources, which is available on the network. Shared detailed client/server logs and network setup to support@ and security@.

cc @elan

2

Not saying it’s not right or wrong, but I am curious, why are you trying to connect to a local resource via a reverse proxy? Plexamp is not going to advertise your remote proxy URL (that’s only possible for servers).

Are your phone and Plexamp headless devices on the same network? Or are you using VLANs and splitting the devices onto separate logical networks?

Also, you don’t need to obfuscate RFC-1918 IP addresses; no one can connect to your devices on non-routable addresses.

3

Those are definitely separate /16 networks for the host connected to speakers and phones/laptops. I don’t want to expose more ports on the host other than those already open.

src/index.js seems to have only one place where IP/port are determined, so I don’t see any significant changes required when original sources are available.

I just want my Linux box with speakers connected to play my FLACs. I have originally tried chromecast, but it hardcodes Google DNS servers and forces resolution through them, which doesn’t work with any split-hirizon setups. Then I tried AirPlay receiver within PulseAudio, but I could only get ALSA running. Then I used spotifyd for two years, but it started experiencing port binding issues a lot recently, rendering it unusable and I can’t play audio anymore from my Linux server box with speakers connected :frowning:

I’m limited by the number of power sockets in the cabinet, so I’m exploring all options before throwing in more hardware devices.

4

any updates?..

5

Any updates?

6

Any updates?..

7

What is shown for the “Connection(s)” for your headless Plexamp if you visit this IP address from a browser on your local network:

https://plex.tv/api/resources?includeIPv6=1&includeHttps=1&X-Plex-Token=your_token

(You can find your token by using the information in this article: https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/#toc-0)

Again, you don’t need to redact your local IP addresses, nobody here can access them.

For example, here’s the connection information shown for one of my headless Plexamp clients:

<Connection protocol="http" address="10.10.0.51" port="32500" uri="http://10.10.0.51:32500" local="1"/>

You should see similar in your configuration. You should also have port forwarding configured in your router to forward TCP 32500 from the clients’ network to the headless Plexamp network (and return traffic should be allowed).

I’m sorry if this seems basic, but there’s not enough information about your network topology and configuration to provide more specific guidance.