Podcast issues

This is a re-emergence of two previous issues:

The first issue is with RTE's The History Show, it just wouldn't work, it listed the recent episodes but wouldn't play them, I removed it and tried to re-add it but it can't again with the 403 error, is a problem with both the web player and the Android app.

The second is with The Retro Hour podcast this works fine in the web player but the only way I can play it in the Android app is if I start it in the web player first and then open it in the Android app.

Comments

  • gravelldgravelld Administrator

    Thanks for the heads-up. I think the first issue is because we've recently increased the number of servers we are working from and some of the IPs are not declared. We'll add that.

    The second one - this sounds like a different issue if it's in the app?

  • The last time you said you increased the how long/how many times you asked for the file, maybe the app limit is lower than the web player?

  • gravelldgravelld Administrator

    Gotcha. Turns out in our Subsonic API implementation we weren't allowing the redirects. I'll push the fix and it'll hopefully be deployed asap, but we're still held up on some scaling work.

  • No worries, I have a workaround so it's fine.

  • neasanneasan Member

    Thanks the 403 error is still a problem for the other podcast.

  • gravelldgravelld Administrator

    Sorry, I haven't had time to check this today. I'll check early next week... It's the "Retro Hour podcast" that has the issue, correct?

  • neasanneasan Member

    Sorry, it's The History Show from RTE, Retro Hour is working great now.

  • gravelldgravelld Administrator

    Thanks...

  • gravelldgravelld Administrator

    It looks like reverse DNS lookups for our server are returning incorrect data. This is the first thing to fix. Once that's working I'll retest and then if it still doesn't work I'll get in touch with RTE again.

  • neasanneasan Member

    Thanks

  • gravelldgravelld Administrator

    That hasn't helped, so I've followed up with RTE again (it's actually Cloudflare doing the blocking).

  • neasanneasan Member

    Thanks

Sign In or Register to comment.