Scrobbler Hard Failure

  • 0
  • 4
  • Question
  • Updated 4 years ago
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: This conversation has been inactive for over 6 months and is now archived.

For over 24 hours now, I have been caching scrobbles on the desktop client. I've checked the log and it says Handshake successful, but then it also says Scrobbler hard failure. Sometimes I'll also get Three hard failures. Invalidating this Scrobbler. I've also gotten Request::onFailurePrivate(int, const QString&) ( 156 ) - L4 a few times. The bottom of the client window will sometimes say Submitting 50 scrobbles... but they just stay in the cache.

I realize the Submissions server is still down, but I am able to scrobble from Spotify at work and sometimes on my phone, so I'm really confused right now. I don't understand what the above error messages mean and I'm not sure if any action is required on my part at this point. I tried Googling it and any documentation I could find was located on your old support forums, for which I now get a 502 Bad Gateway error. Any help on this would be greatly appreciated.
Photo of garynotrashcoug

garynotrashcoug

  • 747 Posts
  • 746 Reply Likes
  • confused

Posted 4 years ago

  • 0
  • 4
Photo of garynotrashcoug

garynotrashcoug

  • 747 Posts
  • 746 Reply Likes
I sent my cache of 175 tracks up the pike. I haven't been able to scrutinize and see if any got dropped, but I think they're all there and I'm currently live scrobbling. Anybody else still having problems? You might try the tip detailed in https://getsatisfaction.com/lastfm/topics/scrobbling-problems 

I still get the "unable to connect to server" message and it's not loading images, metadata, etc for what I'm scrobbling. The log displays messages like this: Failed to extract MBID for: /(filepath)/(filename).mp3
Photo of Erik Qbaliqh

Erik Qbaliqh

  • 42 Posts
  • 110 Reply Likes
The reason is simple.

Last.fm now has its new mistress/favourite concubine: Spotify.com.

Tracks from Spotify.com get preferential treatment.

Submissions from all other sources are "under consideration"  and will be "added in the next few weeks or months."

Look to the forums for evidence! :)

This conversation is no longer open for comments or replies.