Plexamp playback on Sonos pauses after about 13 seconds; can't reauthenticate from Sonos to Plex

Server Version#: 1.27.0.5889 (linux / docker)
Player Version#: plexamp-appimage 4.2.2-1
Sonos: S2 version 14.8.1

At some point yesterday, my plex / sonos integration stopped working correctly. When I cast albums from Plexamp to the sonos, everything seems to work fine at first, but then playback seems to automatically pause after about 13 seconds or so. I can then unpause it, but then it pauses itself again about 13 seconds later.

Trying to reauthenticate to Plex in the Sonos app I got a message about checking my network connection (which is fine).

I didn’t see anything obviously relevant in my server logs, though there was this http error where my server got a 403 on the below URL:

2022-06-09 13:51:28,457 (1524ee346b38) :  ERROR (networking:196) - Error opening URL 'http://resources-cdn.plexapp.com/hashes.json'

This happened before and then fixed itself, so I imagine it’s a problem on the Plex side.

Maybe posting over in the Testing > Plex Labs section might get you an answer (Plex Labs - Plex Forum)

I saw this line in the last Plexamp release notes and wondering if it’s somehow related

  • Default player to listening on port 32500.

@elan if you have a chance could you offer your thoughts on this topic? Thanks

It would be easier if you posted some Plexamp logs. Last ones I looked at showed a cloud error with our Sonos service.

I am getting this issue with both Plexamp as well as the Plex app on iOS. I also experienced issues using the Sonos app > Plex. I have not checked casting to Sonos with the Android app but expect there will also be an issue. Leads me to suspect that @elan is correct and it may be a Plex side server issue with Sonos service. Thanks.

Thanks for taking a look. Attached are my Plexamp logs from MacOS. I also get the same behavior when using Plexamp for Android and Plexamp for Linux (on Manjaro).

I haven’t really looked at my Plexamp logs before. There is one line Jun 11, 2022 17:34:56.046 [Javascript] INFO - Player: State transition paused -> stopped for source RINCON_542A1BF3724E01400:273377789 ID undefined. that stands out, but no obvious errors.

Also captured in this log is some of the weird bahvior that seems to occur after playback stops, when Plexamp sort of bounces back and forth between the library view and the player view.

Plexamp.log (86.5 KB)

For what its worth I am also experiencing sporadic bounce between player and library view - happening at random

I am seeing the same behaviour - plexamp on android & iOS

  • playback pausing after a few seconds. if I resume, it pauses again.
  • when paused the UI bounces between player and library view on its own
  • tried changing remote port to 32500 from 32400, no change
  • able to stream from sonos app using plex library after I reauthenticated
  • able to stream from plex app using sonos. only plexamp app is affected
1 Like

Glad I’m not alone on this. I have the behavior as well on Plex app for Windows and Mac (as well as iOS and Android). I rolled back servers to 1.26.2.5797-5bd057d2b and got the same error all around. The symptom for Plex App on Windows and Mac is that the play bar at bottom disappears and then re-appears randomly every several seconds, but the stream of music continues in (most, but not all) cases.

As of this afternoon plex/plexamp to Sonos seems to be working again

We rebooted a cluster :sweat_smile: Sorry for the trouble.

3 Likes

Heh, believe me, I’ve been there. Thanks for looking at it. Everything seems to be hunky-dory again for me from the Linux Plexamp client.

Is there anything specific we could look for in our Plexamp / Media Server logs that would indicate this problem occurring again in the future?

the plexamp logs had 500 errors from the sonos endpoint.

Not to beat a dead horse, but unless I’m misreading it, I didn’t see any 500 errors in the logs I posted earlier. Every request to sonos.plex.tv seemed to come back with a 200 or 204 response code. (There are some other requests that seem to indicate negative response codes, which I assume is some internal encoding, but they don’t look overtly sonos-related.) Any chance you could point me to the specific lines? Not a big deal if you have better things to do though.

Confirmed working. Thanks for the attention on this.

This has started happening for me again after being fixed for the last week. It’s happening less often, but it has happened twice in the last 10 minutes here.

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