Forum Discussion
Unable to load Amazon, Problem Upstream From Modem
I have bypassed my router with a direct cable connection to the modem, turned off web acceleration, reset the MBX, and have attempted rebooting the modem. The problem is across computers, users, and...
Good morning everyone,
Just got word that Amazon should be working properly now. If you made any workaround changes, please revert back to your original settings and give it a test run.
Thank you,
Amanda
I had the same problem and did everything you stated to no avail. However, the only thing I didn't do was to unplug the modem. So I shut down my laptop, unplugged the modem for several minutes, plugged modem back in, restarted and viola! Amazon dilemma resolved!
Update - After several days of trouble-free shopping on Amazon, the problem reoccured. I'm not technically savvy, but following the OP's advice, rebooting the modem once again (in my case) resolved the issue, at least temporarily. I've also experienced similar scenarios on other secure web sites (i.e. banking), but rebooting the modem always gets me back in. It appears to be problematic on HughesNet's end.
I've unplugged and rebooted the modem multiple times. I've restarted my PC multiple times. Same with the Mac. Still can't use Amazon. Any other suggestions besides sign up with a different ISP or switch from Amazon to brick and mortar?
My Amazon screen looks the same as
Looks like it's not getting the css. That's usually a DNS issue.
DNS's propagate, so if you're rebooting the modem and router while the computer is up and it's DNS is corrupted, you're not doing anything to clear the computer's local DNS.
Either bring everything down simultaneously or flush the computer's DNS cache.
@CORROSIVE
Sorry for the delay. I thought the problem was resolved, reason I haven't been checking out the forum. Unfortunately, it was short-lived. Yes, as HS pointed out, I'm seeing the exact screen image that whysalives's uploaded, garbled text with no images on Amazon. However in my case, rebooting the modem always resolves the issue, at least temporarily, then it reoccurs all over again.
