This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Handling 302 redirects from Google Music #232
Comments
|
Would there be other |
|
thanks for looking into this! This is everything that is displayed with (this is a failed play) If you need further logging tell what to enable in Advanced -> Logging. |
|
This is a successful play: |
|
So yes it looks like the |
|
The only difference I'm seeing is the host name - which shouldn't hurt. Do you see anything else. This sounds similar to what I've heard from some Pandora users. If only I had a way to reproduce this! Would you know of anyway to see this behaviour with something other than Google Music? |
|
Yeah you're right sorry I saw this I can share you my login details privately if that would help? Just be aware that I listen to a lot of Disney soundtracks due to having a young family. |
|
If those tracks fail to stream, then I don't have to care about them anyway 😁. Yeah, that would be helpful! |
|
Have emailed you the plugin prefs file |
|
Ugh... just tried to install the pre-requisities for the GMusic plugin... and Python fails on the first step already :-( |
|
Is it the |
|
Got "Twin Peaks - Fire Walk With Me" playing. That's a good start 😀. Would you know about some track reliably failing? |
|
Hello Michael, there is no real dependency on the track, it just happens randomly after playing several tracks. Maybe pick an album from "Die drei ???", the streaming tracks are very short and it happens a lot more. I actually tried to fix this bug on the plugin side, but that did not work. The plugin always gets a 200-Response and then afterwards the LMS core, when trying to stream the media, gets the unknown response code. If the response code is unknown it is also persistent for a short period of time, e.g. when a track fails to open the next one will work, but if you are immediately skipping back to the broken track, it will fail again. You need 2-3 skip backs and maybe around 60 seconds, before the track actually plays. Hope that helps a bit....? It is not easy to reproduce this issue. |
|
I'm 128 tracks in to a "Die drei ???" session. No hiccup so far... May I ask you what country you're in, and what ISP you're using? One dev reported similar issues with Pandora, but limited to only some ISPs. |
|
In my case UnityMedia with DualStack (IPv4/IPv6). If you give me the needed debug levels, I can trace the issue for you. |
|
@alcoheca mentioned the required |
|
Ok, another 120 tracks played without any hiccup. There must be a more efficient way to reproduce this... What platforms and operating systems are you running your LMS on? I only tested on macOS so far. Windows isn't an option anyway, is it? |
|
Reproduced it after 22 Songs:
(Repeats three times) Happens on Ubuntu 18.04.01 LTS. |
|
Interesting: The new URL from the 302 redirect features not only a new hostname, but also the new options "&ir=1&rr=12" on the end. Maybe those options are leading to a problem?! |
|
Hi sorry I didn't get any notification of these questions. Please try the Goblin album I mentioned in the plugins issue linked above. |
|
It's not random, it happens on specific tracks. |
|
@michaelherger I'm in the UK. And running LMS on a raspberry pi. |
|
Well, tried again and this time it happend on the eight track - which it did not last week. So maybe there a specific tracks, but it is not consistent. The requests fails 3 times (always 302, then no response after the redirect), the server switches to the next track and if you switch back to the failed track, it works again - because you are getting a new URL on another host. @mherger: Might it be possible to not only retry the failed URL, but to get a new URL from the googlemusic plugin? That would prevent this error I think. But i am not deep enough in the code, to know how to achieve this behavior to try it out. btw: The failing track is this one: |
|
For me even switching back after a successful track doesn't work. The tracks that I am unable to play never work. Pretty strange indeed! |
|
@alcoheca Have you tried it several times to play an non-functional track? |
|
@Bucklew yes I just tried playing that Goblin track 12 times and it still didn't work |
|
@mherger Anything more you need or is it possible to reproduce using that song I mentioned? |
|
@alcoheca Time, I need time :-). I haven't been at my desk for almost two weeks. |
|
Yes I could do with some of that too. Sorry to hassle you! |
|
I'm sorry to say that that Goblin album plays just fine here, too. And no re-direct is involved... What version of IO::Socket::SSL are you using (see Settings/Information in LMS)? I wonder whether the redirect, or the failure thereof, is due to outdated SSL libraries or something. |
|
My informations: Logitech Media Server Version: 7.9.2 - 1548427341 @ Fri Jan 25 16:17:35 CET 2019 |
|
Crap... one more theory down: I'm at 1.966... |
|
Maybe too new? ;) What about my idea to request a new URL from the gmusicapi, instead of trying the failing URL over and over again? |
|
What about my idea to request a new URL from the gmusicapi, instead of trying the failing URL over and over again?
Up to the plugin author. But what tells you that this wouldn't end up in a get failing URL loop?...
|
Because in my experience after 2-3 tries google serves a new URL which works. The Squeezeserver would skip the file after a 60 seconds timeout. |
|
Yeah I'm not sure a 60 second timeout is that helpful. There has to be something at work here. Can't check my lib versions are until later on but will report back. @Bucklew I think we might be having different issues? Like I said, the songs which do not play for me NEVER play, despite numerous requests. |
|
I'll try squeezeboxserver on a different operating system tonight. |
|
@alcoheca Do you get a 302 response and afterwards an empty response? |
|
@Bucklew yes, see my logs and the title of this issue |
|
@alcoheca Then I guess we have a similar issue. The question would be how to resolve it. Some people have zero empty responses, you have zero response every single time, I just got them sometimes. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hello,
I'm trying to diagnose an issue in squeezebox-googlemusic (squeezebox-googlemusic/squeezebox-googlemusic#21) which I think is a problem with LMS core.
Certain tracks never play in LMS, while the url is valid and the song can play in a browser for instance.
Here are two logs the first with a failed request, the second with a successful request. It looks like the track the doesn't work involve a redirect, while the second track which doesn't redirect plays normally.
Not working
Working track
I'm running LMS nightly:
Logitech Media Server Version: 7.9.2 - 1545112045 @ Tue Dec 18 07:17:41 CET 2018.Does anyone have any ideas what might be up with this? We're having a party on the weekend and just realised that my house wide sound system is skipping some of my favourite songs! :-(
The text was updated successfully, but these errors were encountered: