Bugzilla – Bug 7453
Unable to play tunes in my MP3tunes locker for 12+ hours
Last modified: 2008-12-15 12:16:42 UTC
When I go to my MP3tunes locker, select a play list and/or tune in a play list and hit play I get the following error message: HTTP:/1.0 401 MAXIMU I'm a premium member at MP3tunes, I'm properly signed in on the SN new web site, and my playlists work just fine on the MP3tunes web site. Rob Chelseth
On my MP3tunes account I was just recently forced to change my password, you may need to do the same. Try changing your password on www.mp3tunes.com.
Changed my password on resigned on to my account at MP3 & SN, however the problem persists. About half of my playlists cannot be accesed and trying to results in the error message <HTTP:1.0 401 MAXIMU>, AND one old playlist that I deleted a couple of days ago on the MP3tunes web site STILL shows up on my Squeezebox connecting via Squeezenetwork!
Monday 10AM Argentina [7AM EST in the US] I continue to experience the errors described with this bug with my MP3tunes access on my SB via the SN. Last night around 10PM Argentine time [7PM EST US] I found that tunes from the few MP3tunes playlist I could get to start playing would stop every 30 to 45 seconds and rebuffer before continuing. MY playlist on the SN still shows lists deleted about a week ago on the MP3tunes site. - Rob
Can you not see the full error message?
What is your SN account email address?
Have lost access to all MP3tunes playlists on SN, once in a while the error message scrolls and says something to the effect <HTTP/1.0 401 Maximun number of syncs exc> or something like that. Could this problem be at MP3tunes? Rob Chelseth Buenos Aires March 12
Appears fixed as of 13 Mar 2008 8PM EST US. Rob
Seems like my congratulations were a bit premature. I'm back to getting the same error message that flashes on and off when I try to play a playlist: HTTP:/1.0 401 Max Been doing this now for 24+ hours. Help!!!
This should be fixed in r2951. The problem was track URLs were being cached and they contained expired session IDs.
This bug has been fixed in the latest release of SqueezeNetwork! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.