NPR Hourly News Podcast HTTP/1.1 400 BAD REQUEST - Can't Play

[SteveLazer]

Hello fellow SqueezeBox fans! Can anyone tell me why I'm getting this message when trying to play NPR News Now on my PiCorePlayer? I've been playing these podcasts for years, but for several weeks they will not play.



RSS Link: https://feeds.npr.org/500005/podcast.xml

[slartibartfast]

Hello fellow SqueezeBox fans! Can anyone tell me why I'm getting this message when trying to play NPR News Now on my PiCorePlayer? I've been playing these podcasts for years, but for several weeks they will not play.



RSS Link: https://feeds.npr.org/500005/podcast.xml

I see this on a Radio. It plays from the NPR website and it also plays from the Google podcasts app.

Sent from my Pixel 3a using Tapatalk

[bpa]

It plays OK using ffplay.

When trrying t play on a receiver - I get the following log message

[21-01-24 09:49:19.7742] Slim::Formats::RemoteStream::open (105) Can't open socket to [edge2.pod.npr.org:443]: 22: Invalid argument

Looks like a https issue.

[philippe_44]

It plays OK using ffplay.

When trrying t play on a receiver - I get the following log message

[21-01-24 09:49:19.7742] Slim::Formats::RemoteStream::open (105) Can't open socket to [edge2.pod.npr.org:443]: 22: Invalid argument

Looks like a https issue.

Certificate problem or cipher suite issue? Were you able to take a wireshark?

[bpa]

Certificate problem or cipher suite issue? Were you able to take a wireshark?

No just ran a quick test and looked in log.
The quick test was on my test server which has lots of mods - so log entry could be due to a personal mod/test change.
However, on my standard Pi LMS 8.0.1 - no log entry and podcast URL (https://play.podtrac.com/npr-500005/...t=pod&f=500005 ) plays OK.

[SteveLazer]

So it sounds like if I roll back my Win10 LMS to version 8.0.1, the podcast will probably play once again? Or is Pi server very different and not indicative of Win results?

[Paul Webster]

Are you using pCP 7 ?
Which LMS version are you running?

Generally ... more recent is better, especially for https issues.
However, there is always a possibility that something has regressed ... but if it has then it will almost certainly be fixed.
So - moving to the newest and repeating the problem is more likely to get it resolved.

[SteveLazer]

Was running pcp v6, didn't know there was a v7, thanks for letting me know! Still doesn't work after update, but the error message is different:
"Connection is no longer able to work".
LMS 8.1.2

[slartibartfast]

No just ran a quick test and looked in log.
The quick test was on my test server which has lots of mods - so log entry could be due to a personal mod/test change.
However, on my standard Pi LMS 8.0.1 - no log entry and podcast URL (https://play.podtrac.com/npr-500005/...t=pod&f=500005 ) plays OK.

If I try to play that URL by adding it to the queue in Material skin I get 403 forbidden. LMS 8.2 on a Pi (Raspbian)

Sent from my Pixel 3a using Tapatalk

[philippe_44]

In 8.1.x, the HTTP request always has a "Range" header which is, when we start from 0, "Range:0-" (it's a legit request). Now what happens is that the AWS server in that case sends a redirect using a 302 and that redirect fails with a "SSL protocol wrong version" which usually indicates that we are trying to establish a SSL connection where the other party is not SSL. I need to investigate why this redirect behaves strangely, but the problem/solution is around that.

When there is no "Range" request, there is no redirection