Plexamp for Raspberry Pi no longer connecting to server

Plex Labs
1

I’ve had Plexamp-v2.0.0-rPi-beta.2 running on a Raspberry Pi 3 for a couple weeks, without (many) issues. This week, it stopped working. I can see the player in desktop and mobile Plexamp, but when I try to select it in the cast menu I get the error:

Could not switch to player

If I view the logs during the connect attempt, I see:

journalctl -xfu plexamp

Oct 06 16:47:24 raspberrypi node[547]: warn: DEVICE: No provider for source <guid>
Oct 06 16:47:24 raspberrypi node[547]: debug: DEVICE: Fetching latest provider list from cloud.
Oct 06 16:47:24 raspberrypi node[547]: debug: DEVICE: Fetching latest list from cloud.
Oct 06 16:47:24 raspberrypi node[547]: error: DEVICE: Error loading media providers from plex.tv:  Error: Request failed with status code 406
Oct 06 16:47:25 raspberrypi node[547]: debug: DEVICE: Fetched 15 devices from the cloud.
Oct 06 16:47:25 raspberrypi node[547]: error: DEVICE: Error loading providers or resources, not merging.
Oct 06 16:47:25 raspberrypi node[547]: warn: DEVICE: No provider for source <guid>

Where guid is the identifier specified in the Pi’s server.json as

 "server": {
    "identifier": <guid>,
    "library": "/library/sections/14"
  }

If I check the Plex Web API, the same identifier is shown as the server ID:

http://<plex_server_ip>:32400/servers?X-Plex-Token=<X-Plex-Token>

<MediaContainer size="1">
<Server ... machineIdentifier="<guid>" version="1.24.3.5033-757abe6b4"/>
</MediaContainer>

Why can Plexamp on the PI no longer connect to the server?

EDIT: removed the information about the changed server ID, turned out to be a red herring.

2
3

@OttoKerner Unfortunately, this isn’t an expired certificate issue. If you look at the log output above, I’m getting “No provider for source” instead of “expired certificate”. That said, I did follow the instructions in the thread you linked to remove the invalid certificate, just in case that was compounding the problem (or in case the log error was mis-reporting). Still no joy. Still can not connect to the Pi player.

4

Perhaps related…

I did reinstall Plexamp 1.1 on my Windows desktop just to try to generate an up-to-date server.json file for my Pi, and for whatever reason Plexamp 1.1 is giving me the

NO MUSIC SERVERS

error*. It had worked previously, because that’s how I was able to generate the initial json file.

So for some reason, older Plexamp’s can no longer connect to my PMS.

EDIT: I’ve now installed Plexamp 1.1 on both an additional Windows laptop, and a separate Mac machine, and all give the “NO MUSIC SERVERS” error. I’m thinking the problem is more in the PMS than Plexamp or the Pi.

*error is exactly as described here:

5

Is really no one else experiencing this issue?

1 Like
6

I do - I’m really very unhappy with the situation. Using Plexamp 2.0.2 in docker container on Hifiberry DAC/Hifiberry OS setup. 3 weeks ago - worked like a charm.
Is ther ANY way to fix this? Or is it just me trying to fling to a headless rpi connected to my old stereo?

7

I just ran into this as well. I just re-built my RasPi image and went back through installing Plexamp 1.1 again and the whole server.json shuffle, etc.

I just ran through the X1/X3 certificate fix with no luck. I never got the certificate error in my service logs; only the DEVICE: No provider for source and DEVICE: Error loading media providers from plex.tv: Error: Request failed with status code 406

8

I’m running Plexamp-v2.0.0-rPi-beta.2 on a PI, with a hifiberry DAC as well - it can see the player but not play.

Hope this is some “motivation” to put some resources into the headless raspberry pi + dac image project that just works. Even if this is put behind plex pass paywall, there are a few folks like ourselves where this functionality would basically put us 100% into the plex ecosystem.

1 Like
9

Same here did the cert fix no go.

Made a fresh pi install did the cert fix, downgraded node, made a new server.json file with older windows plexamp got no music servers found on it.

Then I made manually a new server.json file via curl no go. I can select pi plexamp as flingin destination on web, windows plexapp and android plexapp.

The casting button turns orange play button changes to pause button, but timer/song doesn’t start, web console doesn’t show anything playing.

Command line: sudo systemctl status plexamp shows “error loading media providers form plex.tv … request failed error code 406”

Some times sudo systemctl restart and after it status returns all ok but song doesn’t start/timer doesn’t tick even though pi plexamp can be and get’s selected as the destination.

Seems to me that it is not just the cert thing…

10

Like many others I would be 100% in Plex ecosystem if I could just cast to RPI without using something that currently works like tidal connect via volumio. I would rather use just Plexamp than have to use Tidal or Foobar to play off my RPI

is Plexamp V3 for Raspberry Pi a pipe dream? really sad to see majority of info from 2019…

11

I would like to get this working as well. Trying to run plexamp as a headless system on my old pi zero w. Please update plexamp for Raspberry pi

1 Like
12

I gave up, reformatted the SD card, and installed RasPlex instead. It’s a shame, because it’s overkill for an audio-only solution. And I struggled to get it to recognize my DAC hat. And you absolutely have to have a monitor/keyboard connected for the initial set-up. But once it’s running properly, it can run headless and I can control it remotely via PlexAmp or Plex Web.

Big plus: the support community is still active and answers your questions. Oh… and it’s a “labor of love”, too, so despite what Elan says, the two are not mutually exclusive. So there’s that.

1 Like
13

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