Unable to submit podcast feed - error is Bad http result code 504

Question

emiLyjoQ Author

Level 1

5 points

Unable to submit podcast feed - error is Bad http result code 504

I'm trying to submit my podcast for the first time to iTunes, and am unable to move past the feed submission screen.

I am attempting to submit this feed: http://derbyface.com/feed/podcast

I get an error saying:

We had difficulty reading this feed. Bad http result code 504

My site is hosted at HostGator, I'm hoping it's not an issue with my server. Do you have any ideas for what I could try? Thanks!!

-emiLy

MacBook Pro (13-inch Mid 2012), OS X Yosemite (10.10.4)

Posted on Jul 21, 2015 11:19 PM

Reply

Answer 1

Jul 21, 2015 11:41 PM in response to emiLyjoQ

The feed can be accessed in a browser and can be subscribed to in iTunes (though there is another problem, see below). Error 504 is 'bad gateway' - please see the explanation here: http://www.checkupdown.com/status/E504.html

This could be the result of the server not responding properly to requests specifically from the Store - I don't know whether this is actually the case, but we've seen similar circumstances in the past. You will need to take it up with the people running your server.

However your media file does not work. The URL given is

http://derbyface.com/podcast-download/11/derbyface-0001-2015-wftda-tournament-se eding.mp3/

but this leads to a web page with an embedded player. This won't work - you must provide a direct URL to the actual media file. Test it by entering the URL in Safari or another browser - the file needs to play directly in the browser, not appear in a web page or be forced to download.

Reply

Answer 2

emiLyjoQ Author

Level 1

5 points

Jul 22, 2015 8:15 AM in response to Roger Wilmut1

Thanks for the reply!

I run my server, so if you have any specific ideas about things I could possibly try to fix the 504 error I'd really appreciate any ideas!

I am using Seriously Simple Podcasting plugin for Wordpress to create the feed. When I click the link to the episode above, it does play correctly in the browser with Chrome but you're right, it goes to a web page in Safari. I'll look into that and try to get that fixed!

-emiLy

Reply