bigst3ph3n
Level 1 (4 points)
Publishing

Q: "Can’t read your feed. Bad http result code: 504"

I recently rebooted my show. "Ohhhh Indeed" and I am having trouble figuring out some things. I uploaded a brief show on talkshoe.com like i had years back and when you go to the Podcast app, or Itunes. You can download the show as long as your subscribed. But it wont show up in the search.

 

when i go to my podcasts connect page, it says "Can’t read your feed. Bad http result code: 504"

I have no idea what the issue is. my RSS URL is http://recordings.talkshoe.com/rss93020.xml

 

Any ideas? Thank you.

 

 


Posted on Sep 2, 2016 10:01 PM

Close
bigst3ph3n

Q: "Can’t read your feed. Bad http result code: 504"

  • All replies
  • Helpful answers

  • by Roger Wilmut1,Helpful

    Roger Wilmut1 Roger Wilmut1 Sep 5, 2016 9:09 AM in response to bigst3ph3n
    Level 9 (77,712 points)
    iTunes
    Sep 5, 2016 9:09 AM in response to bigst3ph3n

    As you say, the new episode appears when you subscribe in iTunes, though the iTunes Store is not showing it yet. I can access the feed OK in FireFox and Terminal; it validates in FeedValidator but CastFeedValidator can't read the feed even after 3 minutes. It's possible the Store may catch up eventually (it may just be slow because the feed hasn't been updated for four years) but there's no way of knowing about that.

     

    All this points to your server failing to respond to some types of request. When I tried in Podcasts Connect it simply said it couldn't read the feed. You got a 504 error - this is a 'GateWay timeout'. This page says:

     

    'A server (not necessarily a Web server) is acting as a gateway or proxy to fulfil the request by the client (e.g. your Web browser) to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request.

     

    This usually means that the upstream server is down (no response to the gateway/proxy), rather than that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data.

     

    Fixing 504 errors - general

    This problem is entirely due to slow IP communication between back-end computers, possibly including the Web server. Only the people who set up the network at the site which hosts the Web server can fix this problem.'

     

    So your next step is to take it up with the people who are running your server.