cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to load Amazon, Problem Upstream From Modem

Highlighted
Associate Professor

Re: Unable to load Amazon, Problem Upstream From Modem

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.


* Disclaimer: I am a HughesNet customer and not a HughesNet employee. All of my comments are my own and do not necessarily represent HughesNet in any way.
Highlighted
Sophomore

Re: Unable to load Amazon, Problem Upstream From Modem

After a couple of trouble free days shopping on Amazon, the problem returned.  I followed the same procedure as before and it appears to have resolved the issue, for the time being.  I did a trace to Amazon while connected thru the router, both before and after the fix.

 

Before:

problem_returned_trace_with_router.jpg

 

And After:

problem_returned_trace_with_router_fixed.jpg

 

Unfortunately, I forgot to do a trace without the router prior to the fix, but I did take a trace without the router after.

 

problem_returned_trace_no_router_fixed.jpg

 

Personally, I have no idea what the rest of you might see in these tea leaves.  If the problem persists, I'll continue to remove steps from the solution to narrow it down.

Highlighted
Distinguished Professor IV

Re: Unable to load Amazon, Problem Upstream From Modem

Haven't had the Amazon problem today, myself, but I ran the traceroute just for the heck of it.  Looks a lot different, though I don't know what any of it means.  

 

Capture.PNG


Ryzen 5 3400G | MSI B450M Pro-M2 MAX | 16GB Corsair Vengeance DDR4 3000 | XPG SX8200 Pro 512GB NVMe | Windows 10 Pro
Highlighted
Freshman

Re: Unable to load Amazon, Problem Upstream From Modem

Same here, after a few days of trouble-free Amazon shopping, I'm unable to utilize the service, once more.  It's frustrating having to reboot the modem over and over.  Also, I noticed other web sites having similar problems until I reboot the modem, then they all appear normal again.  I gather it's a technical glitch on the HughesNet end?

Tags (3)
Highlighted
Assistant Professor

Re: Unable to load Amazon, Problem Upstream From Modem

Personally don't care for the HughesNet DNS servers, I use the Google public ones, 8.8.8.8 and 8.8.4.4. No idea if anything to do with the problem but throwing it out here. Have'nt had this kind of problem for a long time since I switched servers.

Highlighted
Associate Professor

Re: Unable to load Amazon, Problem Upstream From Modem

Google's DNS tend to work better, but are sometimes spoofed. Just need to be careful that you don't get re-routed to some sketchy part of the dark web.


* Disclaimer: I am a HughesNet customer and not a HughesNet employee. All of my comments are my own and do not necessarily represent HughesNet in any way.
Highlighted
Assistant Professor

Re: Unable to load Amazon, Problem Upstream From Modem


@MarkJFine wrote:

Google's DNS tend to work better, but are sometimes spoofed. Just need to be careful that you don't get re-routed to some sketchy part of the dark web.


Yep, one good thing about Chrome is it usually opens a new tab when redirected and I kill it immediately. Never visited the true dark web and no wish to. A bit like visiting North Korea IMO, why would one want to.

The "dark" web is called that for a reason.

 

Back to the real issue, I don't have the issues this topic brings up. I've used Google DNS servers for years now, I do remember issues back when I used default HughesNet servers. Sorry HughesNet. Smiley Sad

Highlighted
Sophomore

Re: Unable to load Amazon, Problem Upstream From Modem

Problem reoccured again today.  I didn't bother clearing cookies or cache, I didn't turn off any firewalls, and I didn't turn off any anti-virus.  This time I just reboot the modem, router, and my laptop, all at once and in that order, using the built-in "reboot" buttons in their respective web browser interfaces. That solved the problem, again, for the time being.

Highlighted
Freshman

Re: Unable to load Amazon, Problem Upstream From Modem

@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.

Highlighted
Distinguished Professor IV

Re: Unable to load Amazon, Problem Upstream From Modem


@BirdDog wrote:

Personally don't care for the HughesNet DNS servers, I use the Google public ones, 8.8.8.8 and 8.8.4.4. No idea if anything to do with the problem but throwing it out here. Have'nt had this kind of problem for a long time since I switched servers.


For me, very oddly, and still, the problem doesn't seem to crop up nearly as much when using Hughesnet's DNS.  Normally I use Google's, but on a whim I changed it back to Hughesnet's just to see what would happen, and since doing so I haven't had the problem pop up nearly as much.  Just once or twice since changing, whereas usually it would happen more often than not when going to Amazon.  That's not a joke.  It was awful.    

 

With that said, though, my issue may be a little different than the OP's, or even others that are posting, as when I would have the problem the page wouldn't load at all.  It would give me an error.  This is with a desktop using Windows 10 FCU and Chrome.  But, as to why Hughesnet's DNS seems to work better for me, at least when it comes to Amazon, I'm stumped, as Google's should be the one to work better when going by the general success rate between the two.  

 

Here's what I see when it happens, and again, no joke, it used to happen more often than not.  This problem started for me about four months ago.  But, with that said, I changed back to Hughesnet's DNS around the time of the W10 FCU, so that may have something to do with it, too.  The following is a snapshot from a few weeks ago.  

 

21104286_1645214138830949_701823163_o.png


Ryzen 5 3400G | MSI B450M Pro-M2 MAX | 16GB Corsair Vengeance DDR4 3000 | XPG SX8200 Pro 512GB NVMe | Windows 10 Pro