Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Netflix down on AppleTV2
- Thread starter djrobsd
- Start date
- Sort by reaction score
They were not resolved at 3:58 for me. I did a restore of 4.1.1 and still wasn't working. I am in the middle of scraping my movies in XBMC right now so I can't check, will check when done.
I have had the same Netflix issues with both of my jailbroken ATV2s, both running iOS 4.2 (ATV 4.1). Last night I upgraded one of my ATV2s to iOS 4.3 (ATV 4.2.2) and Netflix worked again on that unit. Netflix worked on that one even after I re-jailbroke with seas0npass.
My jailbroken ATV still running iOS 4.2/ATV 4.1 still has the Netflix error 111 issue. So my guess is that Netflix needs the latest firmware at this point, or is not compatible with the older seas0npass JB.
My jailbroken ATV still running iOS 4.2/ATV 4.1 still has the Netflix error 111 issue. So my guess is that Netflix needs the latest firmware at this point, or is not compatible with the older seas0npass JB.
Whatever the cause, by upgrading to the latest I got Netflix to work. No longer JB, of course, but I don't care.
There are several untethered JBs for 4.2.2. You can update, JB and reinstall XBMC. I did it on Both of my ATV2s and both Netflix and XBMC are working fine on it.
Yes, but big differences in the 2 XBMC versions. 10.0-7 on 4.1.1 just simply works, 10.0-9 on 4.2.2 is a work in progress. This is why I have one apple tv2 on 4.1.1 and one on 4.2.2, as well you now have to have latest software for Netflix to work. This is just my opinion though.
Last edited:
I had this same problem with the code 111 on my jailbroken apple tv running 4.1 all weekend. From what I can tell, it's a handshake issue. I updated to 4.2.2 yesterday and it solved the problem. I re-jailbroke with Seas0npass (they have an untethered jailbreak for 4.2.2; MUCH easier than greenPois0n), re-installed Plex and all is well.
FWIW, 4.2.2 seems to be much more responsive than the older version.
FWIW, 4.2.2 seems to be much more responsive than the older version.
It is available for both Windows and OS X. I did a restore to 4.2.2 using iTunes and then used the OS X version of Seas0npass to jailbreak it again. I had no hiccups at all.
Wirelessly posted (iPhone 3GS: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_3 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8J2 Safari/6533.18.5)
I get this once in a while, though my Internet works just fine. I think it just may be server issues on their end and/or hang ups in the hops between Netflix and the end users.
djrobsd said:
I get this once in a while, though my Internet works just fine. I think it just may be server issues on their end and/or hang ups in the hops between Netflix and the end users.
Doesn't make sense though I can access it on Netflix.com.
Interestingly enough it also didn't work on my iPhone, it crashes when I try to play something.
Wouldn't work on my PS3 because I haven't updated my account since they got hacked and now I'm waiting for my password reset email on PS3...
So tonight.. it's a good old fashioned technology from the 90s called.... a DVD.
Being very new to this stuff I understand very little of what was said on this subject, however, as I'm experiencing a similar connectivity problem with Netflix, I'm hoping you guys can help...
Yesterday I started receiving the message "Netflix not available at this time, try again later"... I've only been using this for a couple of weeks but this is the first problem I've had.
From the info here it appears an upgrade or log out/in is a good first step... Problem is I have no idea how to do either. Can someone give me the "for dummies" step by step?
Thanks
Yesterday I started receiving the message "Netflix not available at this time, try again later"... I've only been using this for a couple of weeks but this is the first problem I've had.
From the info here it appears an upgrade or log out/in is a good first step... Problem is I have no idea how to do either. Can someone give me the "for dummies" step by step?
Thanks
Hello stump54!
This is an old thread and this weekend's Netflix problems are being discussed here: https://forums.macrumors.com/threads/1189383/
However, I made the last post last night and mine's been working so maybe Netflix "fixed" it. However, if you're still having problems just unplug your ATV2 and plug it back in. When Netflix is working that has always solved my connection problems (only twice). If you would, the other thread seems more applicable to what you have going on and post your response there. But that's just my personal opinion and if you get good help here then if it ain't broke...
Email from Netflix on recent issues:
Recently you may have had trouble instantly watching movies or TV episodes due to a technical issue on our end.
We are sorry for the inconvenience this may have caused. If you attempted and were unable to instantly watch TV episodes or movies yesterday, click on this account specific link in the next 7 days to apply your 3% credit to your next billing statement. Credit can only be applied once.
Ready to start watching again? Browse our selection.
Again, we apologize for any inconvenience and thank you for your understanding. If you need further assistance, please call us at 1-866-923-0898.
The Netflix Team
Recently you may have had trouble instantly watching movies or TV episodes due to a technical issue on our end.
We are sorry for the inconvenience this may have caused. If you attempted and were unable to instantly watch TV episodes or movies yesterday, click on this account specific link in the next 7 days to apply your 3% credit to your next billing statement. Credit can only be applied once.
Ready to start watching again? Browse our selection.
Again, we apologize for any inconvenience and thank you for your understanding. If you need further assistance, please call us at 1-866-923-0898.
The Netflix Team
I also received this email. Does this mean they fixed their "technical issue"? I noticed they didn't actually say so...