Blidget not Updating/Unable to find feed

No changes as far as I know. Thanks for looking into this.

Here's the error that we're getting:

Error getting content: http://www.mn2020hindsight.org/?feed=... Error: Circular redirect to 'http://www.mn2020hindsight.org:80/'

We need to include the port when we ping the link element of your site, and it looks like your site is attempting to redirect to itself without the port when this happens, which results in this error state.

Any advice on how I can change this?

It'd be a setting on your server, so you'd need to get the person that handles those boxes involved. Would you mind sending this their way to see if they can resolve it? Once they do, I should be able to clear our cache again and get things back up and happy as far as your blidget goes.

Got this message from Godaddy. Sending them screenshots now. I took the feed off the blidget for now.

"We have reviewed this issue and tested the RSS feed URL provided (http://www.mn2020hindsight.org/?feed=... ), and is is functioning without error at this time. We are unable to replicate the error you are receiving. If you are still experiencing this issue, please provide steps to replicate on the live site for further review."

Hey there,

Sorry for my lack of clarity in this, but the issue is with your main site, which is linked to in your feed. This below message may help:

Currently, your site redirects to itself when you pass in a port:
http://www.mn2020hindsight.org:80/ returns a 302 message to redirect to http://www.mn2020hindsight.org/

I'm including a screenshot of the 302 occuring in the hopes of it assisting the right person in tracking this down.


We need to pass in the port, so when your hosting provider 302's back to the site, we add the port back (since we need it), which then results in this circular redirect.

I'm here to help as much as you need with this issue. I know these types of issues are always a royal pain!

Dave

Here's the response I got from Godaddy:

"Unfortunately there is no way to specify a port when browsing a site on our shared hosting. If you need this functionality you may need to consider getting a dedicated or virtual dedicated server."

Is there a reason why the feed seems to be working everywhere else except for widgetbox? I even tried creating a feedburner version (feed successfully created), but it wouldn't take. Even when I tried to create a new blidget. Did something go haywire when our host went down for two hours on wednesday? Seems like this problem started after that happened.

Unclear what happened, but something made it work!

Holy cow... here I am trying to craft some sort of work-around for you. Well, I'm so glad to hear that this is resolved and I hope that the process wasn't too painful for you.

Thanks for your patience!

Dave

Oh crud. it's breaking, again... Not sure what's going on here.

Seems to be working (for now) on the feedburner version. http://feeds2.feedburner.com/mn2020hi...

OK, so there were 2 of our nodes that looked like the hit the feedburner feed and got an error (then caching the error). I cleared them and now all nodes look to be showing your feed properly, which would explain why you saw the issue intermittently once you moved over to Feedburner.

Cool. I'll keep it on feedburner for now (May as well use the extra tracking) and keep a close eye on it. Thanks again for the help. I love widgetbox!

Thanks so much! We love you too :p

I have followed all that is written here but still only 2 posts are showing on my blog www.allaboutsolarpower.com. It is quite new, but I have about 6 posts with only 2 showing. I use feedburner and everything I post feeds to shows all the information.

Please help.

Looks like mine, was just a temporary problem -- all four feeds were not found on my widget, but then they came back one by one.