Subsonic Forum

by **fr0sh** » Fri Apr 13, 2018 4:25 pm

Hi together,

I have subsonic installed on a Raspberry Pi.
My music library is on a Synology NAS.
I went through the install guides and everything seems to work. This means I am able to browse my music (via NFS share) with the subsonic-user on my Raspberry Pi.
Also I enabled the Sonos service via Web GUI.

When I now try to add this service to my Sonos music services no connection can be established...

Unfortunately the Subsonic log shows nothing regarding this. So it seems that Sonos and Subsonic cannot reach each other, BUT the Subsonic service can be seen within Sonos (which is strange then).

What could be a reason for this? (I'd love to listen to my library via Sonos...)
Thanks a lot

by **fr0sh** » Fri Apr 13, 2018 4:32 pm

I think I found something which could be related:
Here is my log (| grep Sonos):

Code: Select all: [2018-04-09 14:14:13,833] INFO SonosService - Found Sonos controllers: [192.168.178.11, 192.168.178.13, 192.168.178.15, 192.168.178.12, 192.168.178.14, 192.168.178.10] [2018-04-09 14:14:13,836] INFO SonosServiceRegistration - Enabling Sonos music service, using Sonos controller IP 192.168.178.11, SID 242, and Subsonic URL http://10.8.0.1:4040/ws/Sonos [2018-04-09 14:14:13,857] WARN SonosService - Failed to enable/disable music service in Sonos controller 192.168.178.11: org.apache.http.client.HttpResponseException: Bad Request [2018-04-09 14:14:13,857] INFO SonosServiceRegistration - Enabling Sonos music service, using Sonos controller IP 192.168.178.13, SID 242, and Subsonic URL http://10.8.0.1:4040/ws/Sonos [2018-04-09 14:14:13,875] WARN SonosService - Failed to enable/disable music service in Sonos controller 192.168.178.13: org.apache.http.client.HttpResponseException: Bad Request [2018-04-09 14:14:13,876] INFO SonosServiceRegistration - Enabling Sonos music service, using Sonos controller IP 192.168.178.15, SID 242, and Subsonic URL http://10.8.0.1:4040/ws/Sonos [2018-04-09 14:14:14,183] INFO SonosServiceRegistration - Sonos controller returned: <HTML><BODY>Success!</BODY></HTML>

As it seems, Subsonic uses the wrong interface (10.8.0.1) which is for VPN.
But it should be listening to 192.168.178.5 (eth0).
How can I change this?

Thanks a lot!

by **fr0sh** » Mon Apr 16, 2018 11:30 am

After digging through the logs and config files, I got it working now.
Let's make it short:

/etc/default/subsonic
SUBSONIC_ARGS="--max-memory=150 --host=192.168.178.5"

The --host was the key to success.

Thanks

Subsonic Forum

Sonos - no connection to Subsonic-service

Sonos - no connection to Subsonic-service

Re: Sonos - no connection to Subsonic-service

Re: Sonos - no connection to Subsonic-service

Who is online