Loading Profile...
Feed not available in blidget but works fine in browser
I'm getting a feed not available error now with the URL http://blogs.amd.com/how-to/tag/direc.... This worked when we created the widget and worked when we went Pro but now it doesn't.
I’m frustrated
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company thinks this is not a problem.
-
Inappropriate?Hey Andy,
Looks like your host is taking it's sweet old time to respond at times. I got response times between 30 seconds and 1+ minute in the browser. Additionally, one of the IP's the DNS sent me to (139.95.253.55) when testing in a terminal failed and it had to try again. So I'd say your site (amd.com) has some issues to work out that are resulting in the feed proxy timing out.
Failed IP message:
Connecting to blogs.amd.com|139.95.253.55|:80... failed: No route to host.
1 person says
this solves the problem
-
Inappropriate?That is so strange. It's working for us but that could be an internal vs. external DNS servers. Thanks.1 Comment Add a comment
This solves the problem
-
Yeah, give it a look. It did work OK on feedvalidator.org as well, but took ~20 seconds or so to load on their site, which will still timeout in the blidget.
