Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Movies start, but a few times per movie, returns an error: "An error occurred while loading this content". It will allow me to start it again, but it's really frustrating. Internet connection seems solid enough- movies in hd start almost instantly, and nothing else on the network hiccups when it occurs.

Any ideas?

share|improve this question
Have you called Apple support? I'm having a similar issue with my Apple TV (2nd gen) - with a number of podcasts it comes up with this message, but it plays all other content correctly. Really a big pain. I'm just going through the support process at the moment, and they tell me my issue is unknown to them, but perhaps it's more widespread than they think. – Ciaocibai Feb 14 '11 at 9:15

I had this problem with comcast internet. I believe their "speed boost" traffic shaping tricked the Apple TV into thinking I had something like a 22 megabit pipe - so the movies started playing instantly. When the boost expired, the data rate was much reduced and eventually the movie played past the delivery of the content which means my overall download wasn't fast enough to get the whole movie to my set before the movie ended.

When I changed internet providers the issues have been resolved for me. I stumbled on this by realizing I never got this error when taking my Apple TV to a friend's house with "slower" internet. The confusing part was most of the time - comcast was fast enough - but when it wasn't I still got a great initial "boost" but couldn't really watch the rental due to poor bandwidth.

share|improve this answer
I have also seem people saying this because comcast's dns was messing with their settings, and switching to aka Google's DNS worked for their Apple TV. – ConstantineK Apr 18 '11 at 20:42
I can't be sure DNS isn't involved - but generally when DNS is problematic - things are too slow to start or never start instead of degrading mid connection / mid stream. It's possible and a good suggestion when this error happens immediately on the initial play request - just pretty unlikely from the specifics of this question. – bmike Apr 18 '11 at 21:35
Yeah I know, its weird. Thats why I wouldnt even post it in an answer, its too disconnected for me to feel like it has a logical leap – ConstantineK Apr 18 '11 at 21:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.