Sonos "Unable to browse music"

Need help? Post your questions here.

Moderator: moderators

Sonos "Unable to browse music"

Postby Richard Costa Rica » Wed Mar 07, 2018 4:48 pm

I recently installed a software update to my Sonos controller and it is no longer working. Since the upgrade, when I select the music service that is setup on Subsonic, I get the message Ünable to browse music". Everything has been working fine since I set up the system several years ago until just now. I reached out to Sonos and was told that they no longer support Subsonic and to talk to Subsonic about the issue. Has anyone else experienced this problem, and is there a fix for it?
Richard Costa Rica
 
Posts: 2
Joined: Wed Mar 07, 2018 4:32 pm

Re: Sonos "Unable to browse music"

Postby lonesomerider » Sun Mar 11, 2018 1:10 pm

I am using Sonos (actually on Version 8.4) and subsonic, too.
I have no issues at all, except some latency due to my large library, especially on starred albums.

but please check http://www.subsonic.org/pages/sonos.jsp.
If you configured subsonic using the page it is my understanding that the protocol has changed and been extended slightly. Maybe a reregistering works for you.

Another solution to try is to reboot all Sonos devices and then the subsonic server. Upgrades sometimes confuse the interconnectivity between the two.
/lonesomerider

Image
lonesomerider
 
Posts: 26
Joined: Fri Oct 20, 2017 9:09 am
Location: Switzerland

Re: Sonos "Unable to browse music"

Postby Richard Costa Rica » Sun Mar 11, 2018 3:23 pm

Thank you very much Lonesomerider! I was so convinced that my problem was Sonos related that I kept reinstalling my Sonos controller without thinking to reinstall Subsonic. As soon as I did the problem was solved.
Richard Costa Rica
 
Posts: 2
Joined: Wed Mar 07, 2018 4:32 pm

Re: Sonos "Unable to browse music"

Postby clarencewashingtonjr » Mon Apr 16, 2018 3:01 pm

How many network interfaces do you have active? I had a similar problem with a desktop computer that had 3 interfaces. 1 wireless, 1 wired, and a virtual interface installed by VirtualBox. Looking through the Subsonic Logs I figured out that Subsonic was binding to the virtual interface which had a weird IP address. I set the priority on the interfaces so that the wired interface was the primary network interface and restarted the computer. Subsonic began to bind to the primary interface and all was well.
clarencewashingtonjr
 
Posts: 2
Joined: Mon Apr 16, 2018 1:56 am


Return to Help

Who is online

Users browsing this forum: No registered users and 12 guests