Subsonic + Sonos conflicts with Docker on Synoloygy NAS

[achimr]

Problem Description:
I am running Subsonic Premium on a Synology NAS DS2415+

6.0 (build a7857c) – April 30, 2016
Apache Tomcat/7.0.73, java 1.7.0_111, Linux (372.6 MB / 1.03 GB)

It is connected to my Sonos devices and doing quite well.

I tried to also enable Docker on my NAS and everytime the docker application (without any image) is started, Sonos does not see the subsonic server anymore.
- have subsonic run/no docker
- use Sonos Controller and play music - everything okay
- run docker
- Sonos Controller is saying no subsonic available
- stop docker
- Use Sonos Controller and just switch to another song and it is okay again.


I had a look into the subsonic.log files and found the following:

Docker not started:
[2017-03-03 09:04:36,757] INFO SonosService - Found Sonos controllers: [192.168.11.55, 192.168.11.49, 192.168.11.50, 192.168.11.64]
[2017-03-03 09:04:36,757] INFO SonosServiceRegistration - Enabling Sonos music service, using Sonos controller IP 192.168.11.55, SID 242, and Subsonic URL http://169.254.130.54:7070/subsonic/ws/Sonos
[2017-03-03 09:04:36,915] INFO SonosServiceRegistration - Sonos controller returned:successsuccess!

Docker started:
[2017-03-03 09:07:36,915] INFO SonosService - Found Sonos controllers: [192.168.11.55, 192.168.11.49, 192.168.11.50, 192.168.11.64]
[2017-03-03 09:07:36,916] INFO SonosServiceRegistration - Enabling Sonos music service, using Sonos controller IP 192.168.11.55, SID 242, and Subsonic URL http://172.17.0.1:7070/subsoni/ws/Sonos
[2017-03-03 09:07:37,078] INFO SonosServiceRegistration - Sonos controller returned:successsuccess!

Have a look to the subsonic URL

then I checked the Docker IP address:
docker0 Link encap:Ethernet HWaddr 02:42:BF:74:D9:AA
inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0

It looks like as if subsonic picks up the docker ip and treats it as the sonos service registration.

Troubleshooting Steps: Don't run docker ;-(

Anyone any idea how to handle this?

Thx Achim

[mcleanap]

I have this same issue. No resolution as of yet.

Sent from my SM-G930W8 using Tapatalk

[achimr]

I finally found the problem!

The application server that subsonic is relying on is usually configured to listen to all available networkinterfaces.
Subsonics method for figuring out the local ip address can't cope with this.
It just picks an arbitrary one from the list of available ones - most likely the first one in the list returned.

You just have to configure your application server to listen to the network interface only that your sonos devices are connected to.

For tomcat edit the server.xml
on my NAS found here: /volume1/@appstore/Tomcat7/src/conf
and add the line address="ipaddress" to you connector definition.

For the subsonic package that is the file subsonic.sh in the package directory
on my device: /volume1/@appstore/Subsonic
replace SUBSONIC_HOST=0.0.0.0 with your ip adress.

Achim