This discussion is locked
colognedude
Level 1 (9 points)
Publishing

Q: Podcast Connect Error: Read timed out

Hello everyone,

 

I am quite new to podcasting and just released my first episode. Now I have submitted the podcast to itunes and got the "podcast approved"-message yesterday night. So, my podcast is listed on itunes now and works absolutly fine.

 

But when I check on it at "Podcasts Connect" I receive an error message "The connection to your feed was interrupted due to a connection timeout error. Read timed out".

 

For your understanding: I am using an externaly host (www.podhost.de), which should be implementing all data into the RSS-Feed http://headlock.podspot.de/rss.

 

When I uploaded the information, everything seemed to be fine. Now I'm like caught in the middle between working and not working :-)

 

Is it just a matter of time, because the cast just got approved? Will iTunes check on the RSS-feed on a regular basis and therefore, this error may only be temporarly?

 

Thanks for your help in advance, it's highly appreciated!


Posted on Apr 28, 2016 12:59 AM

Close
colognedude

Q: Podcast Connect Error: Read timed out

  • All replies
  • Helpful answers

  • by Roger Wilmut1,

    Roger Wilmut1 Roger Wilmut1 Apr 28, 2016 1:23 AM in response to colognedude
    Level 9 (78,557 points)
    iTunes
    Apr 28, 2016 1:23 AM in response to colognedude

    I was able to susbcribe and check it in Podcasts Connect and http://castfeedvalidator.com/ without problems. A timeout would be cause by your server being slow to respond, but you may just have hit a temporary glitch which could be anywhere in the internet connection between Apple and your server. As long as it's working in iTunes when subscribing I shouldn't worry about it. Temporary hiccups in internet connections are quite common.

  • by colognedude,

    colognedude colognedude Apr 28, 2016 1:31 AM in response to Roger Wilmut1
    Level 1 (9 points)
    Publishing
    Apr 28, 2016 1:31 AM in response to Roger Wilmut1

    Thank you for the quick answer. I gave my host a mail and asked him about this error-message aswell.

     

    Let's hope, this problem will be resolved automatically.

     

    Cheers!