Plex on Sonos: Unable to Browse Music

I have added Plex as a Music Service to Sonos. When I try to browse Plex through the Sonos app, I receive the error “Unable to browse music”.

I have tried to following, based on the advice in other posts:

  • Rebooted my router
  • Rebooted the NAS, which restarted Plex Music Server
  • Restarted Plex Music Server
  • Removed, re-added, and re-authorized Plex in the Sonos app
  • Confirmed Remote Access. Plex is " Fully accessible outside [my] network"

@chrisc - You resolved this issue for another poster by clearing some old/stale Sonos info with the user’s account. Could that be the case here?

Note: I am able to search, as described here and here.
Plex Media Server.log (115.2 KB)

Plex logs are attached.
Server version: 1.32.0.7192-7000 on Synology NAS 7.1.1-42962
Sonos version: Sonos OS S2, App Version 15.4, Build 73041050

After multiple conversations with Sonos, they believe it’s a Plex problem. Sonos’s system is showing that music library access is being denied. However, Plex results show up in Sonos search and I am able to play Plex items from there.

I can also successfully cast to Sonos via PlexAmp.

@johnclayton @vanstinator Seems you are quite knowledgeable about Plex for Sonos. Any ideas?

I’m having a very similar problem. I can add the Plex account to my Sonos but after doing so I’m unable to browse music.

When you say that you can cast from PlexAmp to Sonos that’s via the Sonos integration and not via something like AirPlay correct?

Does your Sonos account show as linked here? https://plex.tv/users/other-services

I’ve written up my findings for my issue here: Internal Server Error When Linking Sonos

It would be really great if we could get some attention on these issues.

I am having problems with Sonos doing Shuffle All from Plex running on my NAS. I have to try to start shuffle all from Sonus 10-15-20 times before it starts. It never starts when I select shuffle all, I always have to use play after Sonos is in the Shuffle All mode. Once I have Shuffle All selected, I just try play several times, then repeat selecting Shuffle All and then Play until it starts. Once it starts it will play all day. Each time it fails I will see the connection lost message. I will also see the connection lost message when it does start to play. I use Plex instead of Sonas to select tunes because my library is too large for Sonos.

I don’t think Sonos and Plex play well together.

Same here.
Sonos with Plex - “unable to browse music”

Debug logs:

key=%2Flibrary%2Fmetadata%2F3026&ratingKey=3026&playQueueID=1021&playQueueVersion=3&containerKey=%2FplayQueues%2F1021&hasMDE=1&includeFields=thumbBlurHash (14 live) #2433 TLS GZIP 2ms 406 bytes (pipelined: 6)
Sep 03, 2023 15:09:52.008 [139824450689848] Debug — Request: [192.168.0.194:41730 (Subnet)] GET /status/sessions?includeFields=thumbBlurHash (14 live) #2434 TLS GZIP Signed-in Token (philius99) (Android)
Sep 03, 2023 15:09:52.008 [139824450689848] Debug — [Req#2434] [Now] Adding 1 sessions.
Sep 03, 2023 15:09:52.009 [139824523377464] Debug — Completed: [192.168.0.194:41730] 200 GET /status/sessions?includeFields=thumbBlurHash (14 live) #2434 TLS GZIP 0ms 1549 bytes (pipelined: 10)
Sep 03, 2023 15:09:53.638 [139824473836344] Debug — Request: [127.0.0.1:51824 (Loopback)] GET /identity (15 live) #244c Signed-in
Sep 03, 2023 15:09:53.638 [139824523377464] Debug — Completed: [127.0.0.1:51824] 200 GET /identity (15 live) #244c 0ms 398 bytes (pipelined: 1)
Sep 03, 2023 15:09:55.990 [139824523377464] Debug — Request: [3.253.69.199:45355 (WAN)] GET / (16 live) #2477 TLS Signed-in
Sep 03, 2023 15:09:55.990 [139824523377464] Debug — Completed: [3.253.69.199:45355] 401 GET / (16 live) #2477 TLS 0ms 371 bytes
Sep 03, 2023 15:09:56.026 [139824523377464] Debug — Request: [127.0.0.1:56802 (WAN)] GET / (16 live) #240c TLS Signed-in
Sep 03, 2023 15:09:56.026 [139824523377464] Debug — Completed: [127.0.0.1:56802] 401 GET / (16 live) #240c TLS 0ms 371 bytes
Sep 03, 2023 15:09:56.157 [139824473836344] Debug — Request: [3.253.69.199:26232 (WAN)] GET /library/sections (15 live) #247f TLS Signed-in Token (philius99) (Plex for Sonos)
Sep 03, 2023 15:09:56.159 [139824523377464] Debug — Completed: [3.253.69.199:26232] 200 GET /library/sections (15 live) #247f TLS 1ms 1831 bytes
Sep 03, 2023 15:09:56.259 [139824446470968] Debug — Request: [3.253.69.199:20145 (WAN)] GET /hubs/sections/6?count=1&onlyTransient=1 (15 live) #248a TLS Signed-in Token (philius99) (Plex for Sonos)
Sep 03, 2023 15:09:56.260 [139824446470968] Debug — [Req#248a] HubCache: Retrieving ‘1/music.mixes.6/1/hubs/sections/6//count=1&onlyTransient=1’ from the cache.
Sep 03, 2023 15:09:56.260 [139824446470968] Debug — [Req#248a] HubCache: Retrieving ‘1/music.tidal.releases.new.6/1/hubs/sections/6//count=1&onlyTransient=1’ from the cache.
Sep 03, 2023 15:09:56.261 [139824446470968] Debug — [Req#248a] HubCache: Retrieving ‘1/music.stations.6/1/hubs/sections/6//count=1&onlyTransient=1’ from the cache.
Sep 03, 2023 15:09:56.262 [139824523377464] Debug — Completed: [3.253.69.199:20145] 200 GET /hubs/sections/6?count=1&onlyTransient=1 (15 live) #248a TLS 2ms 375 bytes
Sep 03, 2023 15:09:58.763 [139824450689848] Debug — Request: [127.0.0.1:51836 (Loopback)] GET /identity (15 live) #2490 Signed-in
Sep 03, 2023 15:09:58.763 [139824525486904] Debug — Completed: [127.0.0.1:51836] 200 GET /identity (15 live) #2490 0ms 398 bytes (pipelined: 1)
Sep 03, 2023 15:10:03.852 [139824473836344] Debug — Request: [127.0.0.1:54650 (Loopback)] GET /identity (15 live) #249c Signed-in
Sep 03, 2023 15:10:03.852 [139824525486904] Debug — Completed: [127.0.0.1:54650] 200 GET /identity (15 live) #249c 0ms 398 bytes (pipelined: 1)

I have also tried changing my password, reclaiming my server and re-authorizing Sonos all without resolution.
Furthermore, even when casting from Plexamp to Sonos, whicle this does cause Sonos to play the media, the dashboard states nothing is playing which means play counts do not increment - which I rely on for some of my smart playlists.

Seems to be Sonos/Plex integration requires a LOT of attention from Support - I’m not sure of any official way to reach the Plex Support team as a Plex Pass member.

Dont get me wrong, Plex is an amazing product and I’m so grateful for the efforts by the team - which is why it’s so frustrating when things dont work as they should.
I’m happy to test any potential fixes/provide more logs but I think that 401 unauthorized is a big clue as to what’s happening.

I also had the “Unable to browse music” error message. I was able to resolve the problem by navigating to a deeper menu.

In the Sonos app (S1) on IOS.

Reproduce Method 1

  1. Go to “Search” at bottom menu
  2. Search for an artist that has never been browsable in Sonos.
  3. Go to that artist entry for Plex
    Result
    Get “Unable to browse music” error message.

Reproduce Method 2

  1. Go to “Browse” at bottom menu
  2. Go to “Plex”
  3. Go to “By Artist”
    Result
    Get a specific (maybe cached) truncated list of artists such as 100 artists out of 10000

Solution

  1. Go to “Browse” at bottom menu
  2. Go to “Plex”
  3. Go to “Other Sources”
  4. Go to the Plex library and server that is troubling you. Example: “Music on MyCloud”
  5. Go to “By Artist”
    From this menu you can browse all the music without getting the “Unable to browse music”. It also has the added benefit of making the problem resolved for Reproduction Method 1 and Method 2.

Thanks for the reply.
The error appears as soon as I go to Browse > Plex so this unfortunately doesn’t solve my issue
As the logs posted show, Plex server is returning a HTTP 401 (unauthorized) error in response to Sonos trying to connect.

@alepine - Thanks for the reply. Just like @philius99 , the solution does not work for me. The error appears as soon as I go to Browse → Plex. I don’t have the ability to select “Other Sources.”

Just a quick update on my issue - I have raised a separate post on the forum but my 401 error has been resolved without me changing anything on my side but I still have the same issue browsing Plex through Sonos

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