Bugzilla – Bug 13362
Napster tracks won't play
Last modified: 2009-10-05 16:42:56 UTC
Now we are using test.squeezenetwork.com, Napster fails to play anything. Selecting a track/album just results in the error message "Error: Failed to connect for: [track name]".
Does the same thing happen if you use the Player UI? Or is this just with the 'remote control' WEB UI
This is working of me now.
Not fixed for me, Still seeing the exact same problem (free trial 28 days left).
Using either a trial account, or normal account, I am still not seeing this error. Andy: what else should we try here?
So this sounds like a works for me... Dominic: "failed to connect" might be some network issue. Please try with SbS and enable plugin.napster and player.streaming.direct.
I'm sorry i have had to reopen this, but still i can not play any Napster tracks via SBS or SN. None of my players SB3, Boom, Radio and Touch will play tracks. Everything works fine (search etc) up until actually pressing play just returns a 'can't connect for ***********.wma' error . Everything else is fine, such as last.fm, podcasts, radio etc, so i am unsure how it could be a networking issue.
QA should take a look.
Dominic: Please download the latest 7.4 version of SBS, then enable the logs as suggested in comment 5. Reproduce the error, then attach the logs to this bug.
QA is still unable to valid the error as reported.
Tested last night, ready to get you the logs, and it started working again! I have not changed anything (was even using same SBS version) but happy its working now. Maybe it was a issue with Napster's service, maybe regional? (im in the UK). Anyway, consider it resolved. Thanks for you time.
Ok, problems again. It seems i was premature it saying this was fixed. It seems that if i am connected to SBS then Napster works. However, if it's connected to test.SN i still see the problem. Re-open? Or is there something i could try?
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.