Announce: Spotify Premium Plugin (Beta)

[bobmac]

Tracks load in the Media Server window, run for approx. 10sec., and then re-sets to zero.

I am getting the exact same behavior of Spotify - works fine, loads songs and playlists, thinks it is playing but no music, and at 7 to 10 sec mark stops and goes to the next track. This will jump through all the tracks in the playlist until done. All other services (i.e., Pandora, music library) work fine.

This only started happening recently after either Logitech Media Server or the Spotify plugin was updated, but unsure exactly what or when. Spotify worked flawlessly for months with absolutely no problems - absolutely great plugin and prolonged the life of my Squeezebox Duet despite Logitech's best attempts of forcing me off of it.

The problem seems to start after a day or so. Logitech Media Server is installed on a dedicated Windows Media Center that does not sleep and seldom gets rebooted. The Self Test fails on the Helper App when the problem is happening. Check the Spotify and LMS logs and nothing obvious is in there.

At first I thought it was if another Spotify device was either playing or started to play, but couldn't cause the problem with testing this specific scenario.

I can solve the problem by uninstalling the Spotify plugin and reinstalling it through the LMS web interface.

Next, I will see what happens with restarting LMS, rebooting, etc. to see what might be triggering or fixing the problem. Also will check the log files much more closely.

Logitech Media Server Version: 7.7.2 - r33893 @ Wed Mar 14 05:47:42 PDT 2012
Spotify 2.2.5
Windows 7 64-bit

[Triode]

I am getting the exact same behavior of Spotify - works fine, loads songs and playlists, thinks it is playing but no music, and at 7 to 10 sec mark stops and goes to the next track. This will jump through all the tracks in the playlist until done. All other services (i.e., Pandora, music library) work fine.

This only started happening recently after either Logitech Media Server or the Spotify plugin was updated, but unsure exactly what or when. Spotify worked flawlessly for months with absolutely no problems - absolutely great plugin and prolonged the life of my Squeezebox Duet despite Logitech's best attempts of forcing me off of it.

The problem seems to start after a day or so. Logitech Media Server is installed on a dedicated Windows Media Center that does not sleep and seldom gets rebooted. The Self Test fails on the Helper App when the problem is happening. Check the Spotify and LMS logs and nothing obvious is in there.

At first I thought it was if another Spotify device was either playing or started to play, but couldn't cause the problem with testing this specific scenario.

I can solve the problem by uninstalling the Spotify plugin and reinstalling it through the LMS web interface.

Next, I will see what happens with restarting LMS, rebooting, etc. to see what might be triggering or fixing the problem. Also will check the log files much more closely.

Logitech Media Server Version: 7.7.2 - r33893 @ Wed Mar 14 05:47:42 PDT 2012
Spotify 2.2.5
Windows 7 64-bit

Tracks appearing to play for about 10 seconds but no audio and then skipping to the next are classic signs of a firewall problem. I suspect if you run the self test from the settings page then you find it streams ok to the server but not to the player. Assuming so you need to look at the firewall on the server machine to make sure it allows incoming connections to the spotifyd.exe helper app.

[Triode]

I have been running BBC iPlayer and Spotify 3rd. party applications on my Logitech Squeezebox Duet and Boom for some without problems but the BBC iPlayer has become intermittent and Spotify no longer works at all on either device.

Regarding Spotify the self test fails the final test: Player did not not connect to helper app............. I have checked firewall settings and they seem to be correct.

Tracks load in the Media Server window, run for approx. 10sec., and then re-sets to zero.

Software details are as follows:
Logitech Media Server Version: 7.7.2
Operating System: Windows Vista
Squeezebox Plugin versions:
BBC iPlayer: 1.2.5
Spotify: 2.2.5

Any ideas anyone?

Definitely sounds like a firewall issue - you need to check that it is allowing incoming connections to the helper app.

[dave4jazz]

Definitely sounds like a firewall issue - you need to check that it is allowing incoming connections to the helper app.

I'm using McAfee Security Software supplied with my O2 Broadband. spotifyd.exe and Spotify both have full access and I have opened Port 9005 in McAfee. Does anyone have experience of McAfee/O2 Broadband? I'm no computer guru and need step-by-step instructions. Triode's Spotify app was great when it worked but something changed recently and I can no longer get it to stream to my Duet or Boom.

[bobmac]

Definitely sounds like a firewall issue - you need to check that it is allowing incoming connections to the helper app.

I am sure it is not a firewall problem. I can fix it by (1) uninstalling the Spotify plugin - LMS restarts and (2) reinstalling the Spotify plugin - LMS restarts. No other changes to the system and it works fine for 2-72 hours. I just can't figure out what is causing the problem as no obvious errors appear in the logs and there doesn't appear to be any changes other changes on the system. I am awaiting for it to happen again to figure what might be the cause, maybe my media center is unexpectedly rebooting, another Spotify client is playing (i.e., mobile), etc.

[Albert]

Sorry, been away on business but I see there has been recent conversation about a 117 connection error. My log file on page 409 contains that error as well. The thing is that Spotify with my DNS-320 worked fine with no special incoming firewall settings and allow all outbound by default before the upgrade to 7.7.1 and 2.2.5 plugin. I've tested it setting the DNS-320 as my DMZ host allowing all ports connection to that device and still no luck, and as the log shows, it flat plain refuses to keep a persistent password set so it never logs in.

This is getting me really frustrated now (network engineer for 15 years at risk of embarrassing self if this is something really simple to fix ). Does the fun_plug image have a built in firewall I am not aware of? I can't think of anything else to do with this implementation.

Spotify works perfectly fine from any other device on my LAN, be it a Windows PC, Tablet, Phone etc. Which tells me the firewall on my router isn't blocking the ports needed.

[Mnyb]

Sorry, been away on business but I see there has been recent conversation about a 117 connection error. My log file on page 409 contains that error as well. The thing is that Spotify with my DNS-320 worked fine with no special incoming firewall settings and allow all outbound by default before the upgrade to 7.7.1 and 2.2.5 plugin. I've tested it setting the DNS-320 as my DMZ host allowing all ports connection to that device and still no luck, and as the log shows, it flat plain refuses to keep a persistent password set so it never logs in.

This is getting me really frustrated now (network engineer for 15 years at risk of embarrassing self if this is something really simple to fix ). Does the fun_plug image have a built in firewall I am not aware of? I can't think of anything else to do with this implementation.

AFaik the Linux kernel comes with an inbuilt firewall, then there is a whole zoo of tools to configure it with like iptables etc .
I assume there could be scripts in the startup setting rules besides the NAS GUI.

Using a home made firewall.local file to set rules myself in my old server, it had a buggy GUI that did not create the rules the right way .

To be sure you can probably use ssh and iptables to look at what rules really are used .

If your a network engineer you probably understands the output better than me

[Albert]

AFaik the Linux kernel comes with an inbuilt firewall, then there is a whole zoo of tools to configure it with like iptables etc .
I assume there could be scripts in the startup setting rules besides the NAS GUI.

Using a home made firewall.local file to set rules myself in my old server, it had a buggy GUI that did not create the rules the right way .

To be sure you can probably use ssh and iptables to look at what rules really are used .

If your a network engineer you probably understands the output better than me

I'm no Linux specialist unfortunately, and besides I don't think the DNS NAS has any firewall enabled by default although I could be wrong. I will mention again, on this exact device, withe the same firmware it has today, Spotify worked great with the previous plugin version. I may resort to downgrading if I can find a howto.

[Triode]

Sorry, been away on business but I see there has been recent conversation about a 117 connection error. My log file on page 409 contains that error as well. The thing is that Spotify with my DNS-320 worked fine with no special incoming firewall settings and allow all outbound by default before the upgrade to 7.7.1 and 2.2.5 plugin. I've tested it setting the DNS-320 as my DMZ host allowing all ports connection to that device and still no luck, and as the log shows, it flat plain refuses to keep a persistent password set so it never logs in.

This is getting me really frustrated now (network engineer for 15 years at risk of embarrassing self if this is something really simple to fix ). Does the fun_plug image have a built in firewall I am not aware of? I can't think of anything else to do with this implementation.

Spotify works perfectly fine from any other device on my LAN, be it a Windows PC, Tablet, Phone etc. Which tells me the firewall on my router isn't blocking the ports needed.

NB - the desktop spotify client uses totally different method to playback - so this is not proving that your firewall is working ok for the plugin. If you want to test from another device, point your browser on the other device at the helper app on the server and prove you can fetch the status page: http://<server address>:<port number>/status.json where port number is usually 9005 if you have not changed it. When you do this, you should get some text back and there should be an entry in the helper app log.

[Albert]

Well I'll be damned, I removed and re-added the plugin and it's logged on now. This time however I never checked the box to upgrade to 2.2.5.

What seems to be happening for me is I select your plugin from the 3rd Party Plugins section, and apply, then restart. After a restart it shows the plugin update available at the very top of the web settings page and I always went right on ahead and checked the box and applied and restarted. Doing that oh 10+ times it never logged in. Now I decided not to bother with the last part and it's logged in now, all tests passed.

Thanks for your help Triode.