bashy;574615 Wrote: > Hi Everyone I just recently purchased my SB Boom after finding out the > possibility of playing my Spotify music on it using this plugin. After > a few hours I'm still having issues and I've read the forum before > asking and have tried a few ideas posted here without any luck.. > > I will post my debug Log hopping for some help. thank you. > > Win7 > 7.5.1 > CLI Port 9090 Status running OK > > > [17:15:20.583] log_message:65 log: 00:15:20.583 I [ap:1368] Connecting > to AP A3.spotify.com:4070 > > [17:15:22.014] message_to_user:61 user message: <a > href="https://www.spotify.com/account/share/";>Share Spotify</a> with > friends and family, they'll love it. > [17:15:22.026] logged_in:45 logged in > [17:15:22.026] metadata_updated:69 new meta > [17:15:23.026] process_playlists:782 process playlists > [17:15:23.031] container_loaded:78 playlist container loaded > [17:15:23.031] metadata_updated:69 new meta > [17:15:23.284] metadata_updated:69 new meta > [17:15:23.476] metadata_updated:69 new meta > [17:15:23.663] metadata_updated:69 new meta > [17:15:32.284] main:422 new connection > [17:15:32.285] main:455 req: playlists.json res: > spotify:user:rfarzin:playlist:37FT2NrqNzs8H884i5IfQ4 par: (null) prot: > HTTP/1.0 auth: (null) > [17:15:32.285] process_singleplaylist:841 process single playlist > [17:15:32.285] process_singleplaylist:861 tracks loaded: 16 of 16, > tracks error: 0 > [17:15:32.311] main:422 new connection > [17:15:32.311] main:455 req: stream.flc res: > spotify:track:1uCbb7fkxRUrQAvCQgmSHo par: > player=00%3A04%3A20%3A1f%3A56%3Abd&start=0&sync=1&id=1 prot: > SPOTSTREAM/1.0 auth: (null) > [17:15:32.311] main:543 newstream connection from 192.168.1.106 > [17:15:32.311] main:577 streamid: 0 newid: 1 > [17:15:32.312] check_player:169 cli connection closed unexpectedly > [17:15:32.312] main:599 unable to play on this player: -1 > [17:15:32.756] main:422 new connection > [17:15:32.756] main:455 req: stream.flc res: > spotify:track:1uCbb7fkxRUrQAvCQgmSHo par: > player=00%3A04%3A20%3A1f%3A56%3Abd&start=0&sync=1&id=3 prot: > SPOTSTREAM/1.0 auth: (null) > [17:15:32.756] main:543 newstream connection from 192.168.1.106 > [17:15:32.756] main:577 streamid: 0 newid: 3 > [17:15:32.757] check_player:169 cli connection closed unexpectedly > [17:15:32.757] main:599 unable to play on this player: -1 > [17:15:32.782] main:422 new connection > [17:15:32.782] main:455 req: stream.flc res: > spotify:track:06VeaUmgdJND7Q6RU6569F par: > player=00%3A04%3A20%3A1f%3A56%3Abd&start=0&sync=1&id=4 prot: > SPOTSTREAM/1.0 auth: (null) > [17:15:32.782] main:543 newstream connection from 192.168.1.106 > [17:15:32.782] main:577 streamid: 0 newid: 4 > [17:15:32.783] check_player:169 cli connection closed unexpectedly > [17:15:32.783] main:599 unable to play on this player: -1
Do you have address filtering on on your squeezebox server - this is the normal cause of the cli connection being closed early. Suggest you look at the main server log too. What is happening is that the server has closed the cli connection without returning any response. This means the server does not want to talk to the helper app and is usually due to some of the security settings you may have set on the server. -- Triode ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=79706 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
