-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Sonos note to README #37
Comments
@quaeler are you saying here in the shell script it needs to be changed to the static IP of the nas? I have the .spk running now on my DS1618+ and it has indexed the media. I have purchased an upgraded subsonic license, but when I go to add the service to Sonos, it fails on the authentication step like you said. Am I understanding this integration correctly in that I need to expose the NAS/Subsonic to the Internet in order for it to authenticate? I don't want to stream from outside my home LAN. I only want to connect my home SONOS system to the NAS on my home LAN. |
Ya - that is the line; this won't expose your Synology to the internet though - that can't be done through the Synology, that can only be done through the router (likely WiFi access point also) which sits between your Synology and the cable / DSL / fiber modem. |
Yea, that did the trick. After ssh in and updating the script and restarting Subsonic, I was able to finally add it to the Sonos. Yea, I don't want to open up anything on my firewall/router into my LAN. That's precisely what I was wanting to avoid, and hoping this integration with the outer website involved subsonic.com, etc. wouldn't require that and happily it does not unless you want to expose a port (which I don't). Thanks for clarifying the problem and the fix! |
Hi, I have the same issue can anyone confirm the location of the shell script to be modified on the synology so I can update the IP address ? Edit: ignore, I found the file to edit /volume1/@appstore/Subsonic thanks for the heads up, spent a while trying to resolve this |
Yep - sorry - i'm on the wrong time zone. For future readers, the file should be at |
I'll take a look at updating the script to detect the local IP address on start up and if it's not sure then fall back to 0.0.0.0, There really needs to be a setting somewhere in subsonic configuration choose from configured IP addresses on the local system and use one of them. That would be a lot more sensible for solving this. |
(First: thank you for this great work; doesn't play m4a's but transcoding the ones that i have is more than worth it.)
Since the start-up script sets the host to
0.0.0.0
, some Subsonic on some Synology NAS (at least my 6.1.6 on my DS620slim) mis-resolve the IP when delivering it to the Sonos speakers as the usual bogus169.254....
IP. This makes adding the service to Sonos impossible as the attempt to verify credentials times out. (Changing the start-up script to feature the local network IP fixes the situation.)Perhaps stick an FYI in the README to help future Sonos-Synology users?
The text was updated successfully, but these errors were encountered: