Triode Spotifiy - no sound!

[meltsheep]

I can't get it to play in that the track plays but there is no sound. BBC player works fine, and does everything else in SB.

I am seeing this in the logs

[09:10:06.563] main:470 req: status.json res: (null) par: login prot: HTTP/1.0 auth: (null)
[09:10:09.178] log_message:65 log: 09:10:09.178 E [c:/spotify/libspotify/client/core/proxy_resolver_win32.cpp:223] WinHttpGetProxyForUrl failed

[09:10:09.179] log_message:65 log: 09:10:09.179 I [ap:1388] Connecting to AP A3.spotify.com:4070

[09:10:14.224] log_message:65 log: 09:10:14.224 E [ap:1324] AP Socket Error: Undefined Error 0x4E20 (20000)

[09:10:14.224] log_message:65 log: 09:10:14.224 E [ap:3396] Connection error: 117

[09:10:14.224] log_message:65 log: 09:10:14.224 I [ap:1388] Connecting to AP A2.spotify.com:80

[09:10:14.261] log_message:65 log: 09:10:14.261 I [ap:938] Connected to AP: 78.31.8.17:80

[09:10:15.571] logged_in:45 logged in

-- snip ---

[09:12:26.772] check_player:223 player address mismatch 195.149.35.28 192.168.2.5
[09:12:26.772] main:643 unable to play on this player: -5


Everything else looks roughly ok.

Do I need to do something funky with open router ports ?

[Triode]

-- snip ---

[09:12:26.772] check_player:223 player address mismatch 195.149.35.28 192.168.2.5
[09:12:26.772] main:643 unable to play on this player: -5


Everything else looks roughly ok.

Do I need to do something funky with open router ports ?

Definately won't work if it says this - what is your setup - this looks like the player connects from a different address to that which is claimed by the server?

[meltsheep]

There is something odd going on with IPs. In the 1st error message it looked like the player was registerd at my WAN/ADSL external IP address.

Does it pick this up from mysqueezebox.com?

I've got a squeezebox touch on 192.168.2.5

I've got squeezebos server on 192.168.2.3 (and spotify installed here)

However on 192.168.2.3 machine I'm running open VPN to 213.229.x.X

So I am seeing now

[11-03-26 10:16:19.7251] Slim::Networking::IO::Select::__ANON__ (146) Error: Select task failed calling Slim::Networking::Async::_async_connect: illegal file descriptor or filehandle (either no attached file descriptor or illegal value): at /<C:\PROGRA~2\SQUEEZ~1\server\SQUEEZ~3.EXE>Slim/Networking/IO/Select.pm line 149.
; fh=Slim::Networking::Async::Socket::HTTP=GLOB(0xb4 3c81c)
[11-03-26 10:16:30.5096] Slim::Formats::XML::gotErrorViaHTTP (341) Error: getting http://213.229.x.x:9001/playlists.json
Connect timed out: Bad file descriptor

Squeezebox seems to think there's a player available at the VPN endpoint public IP. I've not idea how it worked that out...

So I think I need to stop SB from attempting to use external addresses and stick to my internal network, but where is the setting for that ?

[meltsheep]

And lo, when i get shot of mysqueezebox.com synchonising players all is well.

I'm curious as to what mysqueezebox.com attempts to do ?!

[Cornholio]

Probably not the solution you want, but I was having the same problem. A re-install of SBS and the plugin solved the problem.

[SuperQ]

Argh, I'm having this issue as well. This seems to be related to the fact that my squeezebox server and NAT router have separate public IPs. But my server also has a connection to the local network. I suppose I could come up with some firewall rules to route the spotify IP block out through the NAT's IP.

[SuperQ]

Argh, I'm having this issue as well. This seems to be related to the fact that my squeezebox server and NAT router have separate public IPs. But my server also has a connection to the local network. I suppose I could come up with some firewall rules to route the spotify IP block out through the NAT's IP.

Well, I tried this hack:

ip route add 193.182.8.0/21 via 192.168.19.1

193.182.8.0/21 is spotify's subnet
192.168.19.1 is my NAT router's IP

I still get the address mismatch issue. I guess I have to fully put the SBS behind the NAT router.