Announcements
The Spotify Stars Program: Celebrating Values Week!

Help Wizard

Step 1

NEXT STEP

Scrobbling to Last.FM does not work behind a proxy

Solved!

Scrobbling to Last.FM does not work behind a proxy

Spotify client on Linux (but it's quite likely that the same problem occurs on Windows and Mac as well) doesn't seem to be able to scrobble to Last.FM when the computer is behind an HTTP proxy, even using the latest Linux release of the client (uploaded on 20th of May to the Arch Linux AUR repository). I have noticed the problem on multiple machines.

 

How to reproduce it:

 

- Set up "Scrobble to Last.FM" from preferences

- Set up the proxy settings always in the preferences

- Start playing some music

 

I get the error "Unable to contact server (Error 301), x tracks queued" and nothing is scrobbled then. It seems that the proxy settings are just ignored by the scrobbling logic.

 

Fabio

Reply

Accepted Solutions
Marked as solution

You might be able to fix the no images using the work around here:
http://community.spotify.com/t5/Help-Desktop-Linux-Mac-and/Pictures-not-showing-loading-in-Discover-...

Peter
Spotify Community Mentor and Troubleshooter

Spotify Last.FM Twitter LinkedIn Meet Peter Rock Star Jam 2014


If this post was helpful, please add kudos below!

View solution in original post

7 Replies

it seems to be working for me:

spotify version: 0.9.4.183.g644e24e0

OS: Ubuntu 12.04.4 LTS (GNU/Linux 3.8.0-39-generic x86_64)

 

my home squid logs say:

 

1401963510.136 27 192.168.155.66 TCP_MISS/200 346 POST http://post2.audioscrobbler.com/protocol_1.2 - DIRECT/195.24.232.208 text/plain
1401963510.216 77 192.168.155.66 TCP_MISS/200 346 POST http://post.audioscrobbler.com/np_1.2 - DIRECT/195.24.233.57 text/plain
1401963690.050 34 192.168.155.66 TCP_MISS/200 346 POST http://post2.audioscrobbler.com/protocol_1.2 - DIRECT/195.24.232.208 text/plain

 

Mine's down too, so if your situation is like mine, it's not the proxy.  In the last week I've used spotify at home, at work, on the ipad, etc. and have no scrobbles since 3 days ago.

The current issue with last.fm is being discussed in this thread.

It's not related with the issue with last.fm - it's a persistent problem that has always occurred to me behind a proxy.

 

The situation, to be more accurate, is the following.

 

If I set proxy to "auto-detect", then last.fm scrobbling won't work - and I get errors like the one shown in the attachment "lastm_error.png".

 

If instead I set the proxy options, and set the HTTPS proxy, then scrobbling works - but the whole "Browse" section becomes nearly invisible, and most of the images in the application stop working - see attachment "browse_error.png".

lastfm_error.png
browse_error.png
Marked as solution

You might be able to fix the no images using the work around here:
http://community.spotify.com/t5/Help-Desktop-Linux-Mac-and/Pictures-not-showing-loading-in-Discover-...

Peter
Spotify Community Mentor and Troubleshooter

Spotify Last.FM Twitter LinkedIn Meet Peter Rock Star Jam 2014


If this post was helpful, please add kudos below!

This made it work 🙂 now both scrobbling and images are working.

Useless to say that this should be changed - the user should probably be allowed to specify the protocol used by the proxy directly in the preferences, instead of going to an unknown configuration file on the filesystem and edit it. This issue would happen to most of the people who use an HTTP proxy.

I'm experiencing a similar issue, 8 years later.

Fedora 35, behind a proxy. Spotify works fine with pictures and everything, but simply does not scrobble.

Since the application is so obfuscated I can't really provide any more information than that -- it just... doesn't scrobble when behind a proxy. Works fine when not behind a proxy which is odd because it seems that accounts are linked at the server end rather than client end now. Any help would be appreciated, cheers.

Suggested posts