Thanks for those reporting this to sonos.
I don’t know exactly how these things work - but plexamp works fine for me, which reinforces the idea that it is a sonos issue…but maybe I’m wrong.
I am also experiencing this problem and it started occurring after I did a Sonos upgrade. I was running Plex 1.24.1 something at the time and upgraded to 1.24.4.5081 today. I’m still experiencing the issue. I also see the double slash at the end of the API request URL path in the console when I run a query in Sonos. Sometimes it is followed by this message:
Request: didn’t get any data from 127.0.0.1:57691: End of file
I am assuming this port 57691 is the Plex Relay Server.
Same problem here, and I can confirm that it started immediately after a Sonos update. I also have the double slash in the API search URL in the Plex console. Hopefully this broken API link is fixed quickly.
Just keeping this updated. Contacted Sonos Support, still no ETA, they are working with Plex to resolve the issue.
Workaround is to search by album, song, or just to browse without searching.
3 Likes
Man, this fix is taking a while.
Latest release notes say that it’s fixed. Can confirm after a quick test.
1 Like
Looks like I’m now not getting any plex search results. Anyone else seeing the same?
Edit: looks to be an issue with one particular artist that plex somehow didn’t pick up. Ignore.
I still have the original issue. I didn’t notice a plex or Sonos app update.
Is there some steps I need to follow to get the new release?
Same here for me. I run Plex 1.24.5.5173 on my Synology NAS and Sonos 13.3 on my devices. So far, no updates are shown as being available. Do you guys run some beta version or are you subscribed to early-bird testing releases?
It is fixed here on PMS Version 1.25.0.5220 and sonos 13.3.2. Thanks
Fixed here too finally.
PMS: 1.24.5.5173
Sonos: 11.2.13 (S1)
Thanks to everyone who helped diagnose this and get it fixed 
I manually upgraded to PMS 1.25.0.5220 (I’m running on a Windows Server if it makes a difference).
My Sonos is version 13.3.2.
Unfortunately I still have the issue.
Did you guys re-link your Plex and Sonos? Trying to see what I’m missing and why I’m still having the issue.
No, didn’t have to relink. (For reference, I’m running Plex as a docker container in Ubuntu.)
I did power cycle a couple of my Sonos boxes for other reasons though - don’t know if that had any effect?
I had to do that the other day too but that was before the fix came out. As far as I know the app is hosted remotely so there’s nothing for us to update.
Restarting Sonos devices or Reauthorization didn’t fix the issue. Fully removing the plex Service from Sonos and re-adding it has solved the issue.
Glad to have it fixed!
Final Note: The double // in the get request: … /library/sections//all? is fixed as well. So that was the root cause.
1 Like
Yeah, finally fixed for me too. As the second person to comment on this thread, way back on September 7th – and as a person who spent 2 hours calling into Sonos support trying to convince them of the problem, all I can say is… About time, hallelujah, and thank you baby jesus. While I wish it had been fixed a little faster, I’m super glad it’s working. Thanks to everyone else that contacted Sonos to get the problem fixed.
appear to be working for me too. Thanks to you all for figuring it out - and convincing Sonos to fix it.
Yeah fixed here too. Also it seems to have fixed another issue I was experiencing but nobody else reported previously. The speed of search under SONOS on PLEX was taking maybe 20 seconds, now back down to a reasonable second or two. Great!!
This error message is back for me. Anyone else experiencing it?
It’s still working for me without errors.
