Server Version#: 1.32.0.6918
Player Version#: 4.104.2
I have a headless RPi plexamp (version 4.6.2) and a mac. On the mac I have both plexamp (also version 4.6.2) and I am running the plex web client connected to my local PMS server (version above).
My mac plexamp app can connect to, cast to, and control the headless plexamp client reliably and with no problem.
The plex web client also used to be able to do that. I don’t know when it changed because I usually use the mac plexamp app, but a little while ago I was browsing music on the plex web client and tried to play to the headless player but could not connect from the cast icon. I click it to open the panel, it shows me the headless plexamp client, but when I select that client from the dropdown, nothing happens - the cast icon does not turn gold and the web client is still playing to the mac’s audio.
When I look at the console log of the browser, I am seeing some 404 errors when I try to connect to the headless pi. I have tried with two different browsers but I get the same result in each case. Since the plexamp native app on the same mac has no trouble connecting to the headless pi plexamp instance, it doesn’t seem like a network thing.
I tried re-installing plexamp on the pi and re-claiming it, but after doing that I see the same; plexamp app on the mac connects, plex web does not (and 404 errors in the js console).
have seen this too … from what i can tell, headless never sees an incoming request, so if there’s an issue i’d guess it’s on the Plex web client end of things
that being said, I prefer using the Plexamp web user interface (<pi_hostname>:32500) to browse and control headless playback remotely when I’m using a laptop/desktop with a large display and web browser
Agree, I tailed the logs on the pi client and nothing ever got there when I was trying to connect from the web client - which makes sense given the 404 errors in the js console. The problem is somewhere between the web client and the plex.direct server (which I think is redirecting back to my PMS) which is returning the 404.
Somehow the web client is constructing the URL for that call differently than the native plexamp client.
I also mostly prefer the plexamp UI to the web UI with one exception; i think the web client has better UI for building and manipulating ad hoc queues.
This sounds just like what’s happening to me through plex Web when trying to fling videos, also asked a few others who’ve also experienced it, rolling back to 1.30 seemed to fix it for me
I think I’m experiencing the same issue…
For a long time I have been able to select my RPi client running RasPlex as the player either using the web interface or the dedicated windows GUI Version 1.32.0.6973
But now, since a couple of updates ago, the icon goes gold briefly then returns to grey.
I can however use my android phone to control the pi.
Any help in resolving this or how to troubleshoot appreciated.
