Bugzilla – Bug 13131
Can't connect on Deezer
Last modified: 2009-10-05 16:44:08 UTC
Since a few days, Deezer is unavailable from SqueezeCenter. Radios list can't be fetched, only a "404 not found" message is displayed. May be it's related with deezer v3? It was working fine before. Deezer Smartradios don't work either, nor Artist search. Same problem on SqueezeNetwork, 404 or Connection Timed out when I try to log in my Deezer account. It's not a one-person problem: http://forums.slimdevices.com/showthread.php?t=65981
Grr, nice one Deezer.
Fixed, Deezer changed their API URL (wait a few minutes for changes to be rolled out to SN).
thank you for your celerity http://api.deezer.com (<= smiley inside) seems they have fun to change their url.
is it fixed for the artist search in deezer? Radios now are working well, but I still have a connection timeout to api.deezer.com when searching artists.
What are you searching for? My test suite passes when searching for an artist. Is it possible the search is taking too long and timing out?
seems it takes too long for certain artits or keyword (try "dada", "gaga", "fatals picards", "madonna" etc), but some works ("jackson" etc)
Nothing I can do about that unfortunately.
ok thanks
Andy, would it be possible to have another look at the Deezer thread. Some customers are still reporting problems: http://forums.slimdevices.com/showthread.php?t=65981 Customers are able to play a few tracks, and then it stops. Searching for artists is also problematic. A lot of 500 and 505 errors (time-outs?). Considering your last post, this is not something that can be fixed our end? I.e. It's the Deezer server taking too long to respond.
Same problem here. Deezer artist search works only sometimes. Most of the time the error message "500 Can't connect to api.deezer.com:80 (connect: timeout)" appears (sometimes for the same artist for which the search worked 1 minute before).
This bug has been fixed in the latest release of MySqueezebox.com (formally known as SqueezeNetwork)! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.