Loading Profile...
Valid Feed coming back as "couldn't parse" but was working perfectly before TF went down
My feed was working perfectly until twitterfeed went down. Since then, when I log in, it gives me the "we couldn't parse this feed" but at the same time when I test the feed it comes back as an ok feed (and it was working before). Is there anything I can do, is it a bug you are already working on...?
I’m a bit desperate, lol!
4
people have 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.
-
-
Inappropriate?I have the worst timing in the world signing up for the service in the middle of the migration crisis so I don't know which problems are mine and which are Twitterfeeds - feeds test as valid, but come back now as unable to parse and/or 401 unauthorised (though they had been OAd to start with). Is it me or is it Twitterfeed? I can't find anything in the FAQ that really helps me figure out what to do so I reckon it is problem more the server hiccups and I need to be patient. As others are having similar problems? Thank you for helping. Should I delete them and start over here, or wait until the kinks going on now are sorted? -
Inappropriate?If you have problems with the feed parsing, could you let me know the feed URL and I'll try and take a closer look. This message can occur sometimes for example due to network time outs, if twitterfeed can't fetch the feed sufficiently quickly, but if it persists let me know the feed URL and I'll see if I can dig around a bit more.
Re. the 401 error, this isn't related to the feed, but to twitter authentication when twitterfeed tries to update your status on your behalf. If you're using OAuth, you could try to go back into the feed settings and click the "re-autenticate" link - this should generate new access tokens (just in case the access tokens we have on record are somehow wrong or not working anymore).1 Comment
Add a comment
This solves the problem
-
Hi Mario, my feed is http://feeds.feedburner.com/UglyDoggy appears as valid but still not working... not sure how to move the feeds (and if people using the actual one will still receive it) -
Inappropriate?Thanks, I will re-authenticate. Here are the feed URLs (one is a duplicate, will delete as the other works or not).
http://thepensivequill.am/feeds/comme...
http://feeds.feedburner.com/bigmackers
http://thepensivequill.am/feeds/posts...
Thanks again!!
I’m thankful
-
Inappropriate?These are mine.
http://feeds.feedburner.com/YourDaily
http://feeds.feedburner.com/TomRaysWe...
http://feeds.feedburner.com/LorenzosM...
http://feeds.feedburner.com/Polliwann...
I’m word
1 Comment Add a comment
This solves the problem
-
It looks like there's some weird DNS issue with the feeds.feedburner.com domain. On one server it resolves to 74.125.93.118, and fetching/parsing the feeds works fine, but on a different server (with a different ISP), it resolves to 66.150.96.119 and times out.
The only thing I can think of is that you could try moving the feeds to feedproxy.google.com (probably a good idea anyway, as I don't know how much longer they'll support feedburner.com), and then use these feeds in twitterfeed. -
Inappropriate?I deleted my old feed and re-created it and it's working fine now. -
Inappropriate?Those feeds have already been migrated to Google - will look into feedproxy.google.com however. This feed is now working: http://thepensivequill.am/feeds/comme... - thought I would let you know. If this can be resolved without having to change everything over that would be good. It could also be an timing issue with Google's migration.
Thanks again2 Comments Add a comment
This solves the problem
-
Your issue was the 401, so the twitter authentication rather than the feeds themselves, so I guess you should be ok.
-
Mario - thanks very much - problem appears solved! :-)
-
Inappropriate?Hi Mario, my feed is http://feeds.feedburner.com/UglyDoggy
EMPLOYEE
