Plexamp Headless - "No Servers Found"

Plex Labs
,
1

Hello all -

I’ve been trying to get Plexamp headless up and running, but no matter what I do, when I log into the web UI I can’t get it to see my Plex server. I have been using Plexamp for a while on several other devices - iPhone, iPad, Linux PCs, Macbook, etc. All were able to quickly find the shared music library and connect to it and play music. My Plex server is running in a Docker container on a Proxmox host, all devices are on the same IP range - 192.168.1.x.

I’ve pulled down the Plexamp logs from ~/.cache/Plexamp/log and attached them. There is one point where it looks like it can find my server (it’s called Tupperware):

INFO - DEVICE: Found 5 libraries from Tupperware: Home, Movies, TV Shows, Music, Playlists
INFO - Discovery: Setting 11 hubs from Tupperware.

And there’s also a lot of the below sprinkled in as well, unsure if it’s relevant but it certainly sounds bad:

INFO - Discovery: Are we offline? 10 hubs, network is 2 => offline: false.

I have no firewall set up on the raspberry pi, it’s a fresh install if rPiOS lite, and the only changes I’ve made it installing Node and Plexamp per the installation instructions (I use a username other than pi to be consistent with the rest of the things I ssh into, but I don’t think that should matter aside from adding plexamp as a service in systemd).

For other reference when looking at the logs - ryzenbox is my main desktop (what I’m typing on now and where I have plexamp open in a browser trying to connect) and the raspberry pi is called pifi.

I’ve been searching all over and I’m sort of beating my head against the wall - I’m hoping someone here will know something that will help me set down the right path in troubleshooting. I certainly could have missed something, but I’ve been searching in this forum as well - apologies if this is a duplication, and if so please point me toward the relevant thread.

Thanks in advance!

Plexamp.log (31.2 KB)

2

There is something network-wise broken for you.

Jul 28, 2023 19:56:00.574 [Javascript] WARNING - DEVICE: Server connection https://172-18-0-1.7472b75d6a654ec0b41fafe1eee6c7de.plex.direct:32400 didn't work for Tupperware: HTTP status -28
Jul 28, 2023 19:56:00.575 [Javascript] WARNING - DEVICE: Server connection https://192-168-160-1.7472b75d6a654ec0b41fafe1eee6c7de.plex.direct:32400 didn't work for Tupperware: HTTP status -28
Jul 28, 2023 19:56:00.575 [Javascript] WARNING - DEVICE: Server connection https://192-168-48-1.7472b75d6a654ec0b41fafe1eee6c7de.plex.direct:32400 didn't work for Tupperware: HTTP status -28
Jul 28, 2023 19:56:00.576 [Javascript] WARNING - DEVICE: Server connection https://75-190-205-54.7472b75d6a654ec0b41fafe1eee6c7de.plex.direct:32400 didn't work for Tupperware: HTTP status -28

Those are the three URLs it’s hitting, and all of them are timing out.

Can you hit them via curl on the Pi?

3

I tried all 4 both on the pi (as well as my main computer, I was curious). The first 3 return “could not resolve host” immediately, and the 4th takes 2-3 minutes to time out. Interestingly, the same results happen on my desktop computer - on which Plexamp works.

If I curl the 4th address without the port listed, I get to a page from my router (pfsense) talking about a possible dns rebind attack. The prefix on the 4th address is my WAN IP.

4

Besides other issues, you probably have DNS rebind protection enabled so those URLs won’t resolve.

Plexamp should be manually resolving to IP e.g. 192.168.160.1 but that looks sort of like the gateway and not your server?

5

Thanks - I’ll look into DNS rebind protection. If it’s enabled, it must have been for a long time as I haven’t messed with any of my DNS settings in a long time. I am curious though why it’s only an issue on a single client?

I’m not sure what 192.168.160.1 is, that’s not an address anywhere on my network. I don’t see it in my list of DHCP leases, it’s not an IP range I use, and I can’t ping it.

6

Turned off DNS rebinding protection in pfsense. Plexamp found the music library almost immediately.

Thanks so much for the help!

I guess I’ll never know why other clients had no issues but headless does - does headless connect differently somehow than the apps? (Purely out of curiosity)

7

No, Plexamp should always perform the manual DNS resolution, hence why I suspected something else was going on.

What is the IP of your server? Because 192.168.160.1 and 192.168.48.1 both look like gateways.

I suspect it’s working now to the WAN IP, but logs would show.

8

Plex server is at 192.168.1.7. It’s running via docker, but it’s tied to the host network and is accessible at the same IP using port 32400. The 192.168.41.1 address makes a bit of sense to me, that’s the address range for a docker network I use for a reverse proxy, although plex isn’t a part of that network. The 192.168.160.1 is wholly unknown to me.

Based on the logs it is resolving to 192.168.1.7 I think.

Jul 29, 2023 00:01:56.501 [0xf791b640] DEBUG - Networking: Create request 61: (POST https://192-168-1-7.7472b75d6a654ec0b41fafe1eee6c7de.plex.direct:32400/playQueues?includeLoudnessRamps=1&shuffle=0&uri=server%3A%2F%2F799b452b437e1ede03eadc38f15d362b3dac6d61%2Fcom.plexapp.plugins.library%2Flibrary%2Fmetadata%2F117423%2Fchildren&playlistID=undefined&includeExternalMedia=1&type=audio&commandID=46&paused=false&includeFields=thumbBlurHash&X-Plex-Device-Name=PiFi).
9

Not that you likely care, because it’s working (almost certainly because it’s going via WAN), but you could also try publishing a custom URL via server network preferences to make Plexamp try a specific IP/host.

10

Like this?

Screenshot_20230729_020709
Screenshot_20230729_020709757×135 11.7 KB

11

Yeah, but I’d use HTTSssssss :snake:

12

Noted - adjusting :sweat_smile:

Thanks again for your help and input. Great learning experience on my end.

1 Like
13

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.