Forum Discussion
Amazon Prime Always Errors
Thank you for posting and welcome to the community. I am sorry to hear this. I took the liberty of running remote diagnostics and the equipment is reporting as fully operational as well as ample data left. I do, however, see that all of the devices connected to your network show either poor or fair signal. This will definitely cause severe buffering and time out errors. Moving your Roku stick closer to the modem or using a WIFI extender would help with this. Now due to the fact that your other streaming services work despite the poor signal quality, the amazon app may be more sensitive to poor signal quality on Roku sticks and TV's specifically. Inherent satellite latency combined with weak signal can make streaming app's act strangely but seems to be much more common with the Amazon Roku app, based on anecdotal evidence. If getting an extender from our company or moving the device closer to the modem is not possible, the best I can recommend is downloading Amazon prime videos for offline view through your phone and casting it to your tv or using a device that can display video from USB to HDMI. -Damian
Damian,
I am unable to move the roku device closer to the wifi modem as it sits less than 3 feet from the modem. As for downloading from my phone and casting to the TV, it is not a smart TV so that is not an option.
Based on what you've said, and correct me if I am wrong, is that Hughsnet is not stable enough to handle Amazon Prime?
- maratsade11 months agoDistinguished Professor IV
"Based on what you've said, and correct me if I am wrong, is that Hughsnet is not stable enough to handle Amazon Prime?"
If it were, everyone would experience the same issue, and that's not so. It may be that in your area, or with your configuration, Prime doesn't work as well.
- MarkJFine11 months agoProfessor
HughesNet is stable enough to handle Amazon Prime, as I've watched it myself.
What you're probably experiencing is a corrupted cached DNS entry, not an issue with lag time. Amazon likely uses a different path to it's streaming content than it's menuing application and the images it uses, and that path has been somehow corrupted. I've experienced this myself at times.
To correct this, you may want to:
1. Unpower your modem by removing the cord from the power brick - this will automatically kill any cached DNS entries.2. While the modem is off, similarly remove the power input to your Roku - this will kill any cached entries in the Roku.
3. You may want to optionally unpower or restart anything else connected to the wifi to ensure those devices aren't similarly harboring any cached DNS entries that are corrupt.
4. Re-apply power to the modem and wait a few minutes until the wifi reappears.
5. When the modem is fully operational, restart your Roku (and any other devices).
- MarkJFine10 months agoProfessor
Having said all this, apparently Amazon changed the way it works with ads and there is a possibility that there's an issue with the way it now interacts with video optimization. If you have video optimization always enabled, temporarily snooze it to make the 'oops, it seems a problem occurred. please try later' go away.
Related Content
- 2 years ago
- 4 years ago
- 8 years ago