RSS feed valid but twitterfeed reports cannot parse
twitterfeed is reporting that it cannot parse some of my RSS feeds however they are valid and when you go into the feed and click "test rss feed" it returns "Feed was parsed successfully" every time.
10
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?This can happen if there are temporary issues like time-outs, network problems etc., but if it persists, let me know the feed URL and I'll try and take a look. If it's a Yahoo! Pipes feed, also see the recent company update, as it looks like they throttle twitterfeed access to their feeds.
-
Inappropriate?Hey Mario,
Thanks for the response... we're seeing the issue with basically all the feeds we have in twitterfeed but without any real feedback information apart from "we couldn't parse the feed" I can't really troubleshoot it.
http://feeds.gizmodo.com.au/GizmodoAu...
http://feeds.lifehacker.com.au/Lifeha...
Could you let me know why they're failing so if it's something on the feed side that needs to be changed I can fix it up? Thanks in advanace!
-
I've taken a closer look, and there's something very strange going on.. re-running the parsing manually from the machine that runs the feed processing, it sometimes works and sometimes doesn't (that's without changing any code anywhere), so it's definitely not an issue with the feed content itself, but there's something else that sometimes stops the feed from being parsed. I'll try and dig a little deeper to see if there's anything I can find that may cause this. -
It appears to be a DNS issue of some sort, I'm getting "Error: 500 Can't connect to feeds.gizmodo.com.au:80 (Bad hostname 'feeds.gizmodo.com.au')" about half the time when making manual requests, while it works the other half of the time.
I'll check with my hosting provider to see if they are aware of any issues. -
It actually looks like it may be a DNS issue with the nameservers of these 2 domains (both gizmodo.com.au and lifehacker.com.au use the same nameservers) - 2 respond with warnings - 1 doesn't respond at all:
alex@alex:~$ dig feeds.gizmodo.com.au @ns1.yourdnshost.net
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
; <<>> DiG 9.5.1-P2 <<>> feeds.gizmodo.com.au @ns1.yourdnshost.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 104
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;feeds.gizmodo.com.au. IN A
;; ANSWER SECTION:
feeds.gizmodo.com.au. 3600 IN CNAME
sitesalluremediacomau.feedproxy.ghs.google.com.
;; Query time: 595 msec
;; SERVER: 202.124.241.10#53(202.124.241.10)
;; WHEN: Fri May 29 11:40:15 2009
;; MSG SIZE rcvd: 98
alex@alex:~$ dig feeds.gizmodo.com.au @ns2.yourdnshost.net
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
; <<>> DiG 9.5.1-P2 <<>> feeds.gizmodo.com.au @ns2.yourdnshost.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 30541
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;feeds.gizmodo.com.au. IN A
;; ANSWER SECTION:
feeds.gizmodo.com.au. 3600 IN CNAME
sitesalluremediacomau.feedproxy.ghs.google.com.
;; Query time: 594 msec
;; SERVER: 202.124.241.100#53(202.124.241.100)
;; WHEN: Fri May 29 11:40:20 2009
;; MSG SIZE rcvd: 98
alex@alex:~$ dig feeds.gizmodo.com.au @ns3.yourdnshost.net
; <<>> DiG 9.5.1-P2 <<>> feeds.gizmodo.com.au @ns3.yourdnshost.net
;; global options: printcmd
;; connection timed out; no servers could be reached -
Inappropriate?Could you please check if Yahoo! Pipes is also having similar DNS issues. Here is my feed from pipes, and I am getting the same parsing error from twitterfeed:
http://pipes.yahoo.com/pipes/pipe.run...
The feed seems to be valid on feedvalidator.
I’m frustrated
-
Intermittent problems with Pipes are more likely related to this: http://getsatisfaction.com/twitterfee... -
Inappropriate?I'm having the same problem with every feed I've tried to enter including Feedburner feeds and the feeds hosted on my own servers. I even tried entering a Squidoo lens feed and still got the cannot parse error.
All the feeds are valid according to feedvalidator.org.
Please help!
I’m frustrated
-
There was a problem with the "test feed" functionality which should now be fixed, not sure if this is related. If it still doesn't work, can you let me know the feed URL(s) which can't be parsed and I'll try and take a look. -
Inappropriate?I am having the same problem. Please keep us updated as to the fix. My feed was confirmed as a good feed in the feed validator but I am still getting a "having problems parsing this feed"..
My feed is : http://homeorganizing.wordpress.com/f... -
This feed seems to be valid and parses ok, but I can't see it in the database. There was a problem with the "test feed" functionality which should now be fixed, not sure if this is related. -
Inappropriate?Hi Mario,
I'll get in touch with the guys who are providing the DNS hosting for our domains and let you know what the outcome is. Thanks for pointing me in the right direction!
kk
-
Inappropriate?Almost the same problem...
We have two feeds, both generated the same way (just different info).. the BOTH validate on every validator we try INCLUDING the one in TwitterFeed, yet on the view page... one is showing that it can't be parsed..
this is the feed that won't parse..
http://www.skagitcounty.net/Emergency... -
This feed now shows "ok", so it's likely a temporary issues. Sometimes requests can time our or take too long for twitterfeed to receive the feed content, resulting in these errors, but these are typically network-related and not permanent. -
Inappropriate?I am attempting to link a RSS feed to my twiitter account using twitterfeed. I get an error message - "We couldn't parse this feed, please check URL and/or feed content are valid"
I can enter the URL into a browser ( Firefox ) and I get the response to Subscribe.
URL - http://groups.google.com/group/cloud-...
Can anyone see anything wrong with this URL and why Twitterfeed can not parse it.
BTW: I have attempted to link the URL multiple times, with the same result.
Thanks
Dave -
The problem is exactly that you need to be signed in to see the feed. When twitterfeed requests this feed URL, it gets redirected to this "you must be signed in" web page, which is obviously not a valid feed, so that's why it complains. Currently twitterfeed only support feeds that don't require authentication I'm afraid. -
Inappropriate?i have the same problem for a while now. my blog is http://biopunk.hu, feed is http://biopunk.hu/feed/
I’m sad
-
Strange - feedvalidator does show an issue, but I don't think that's the reason (http://feedvalidator.org/check.cgi?ur...), although of course it won't hurt to fix it just in case.
Other than that, what I noticed is that the first time I tried to parse the feed it failed, but after that it worked ok. Is it possible that the feed is cached for a time, so when it's fetched the first time after some interval it does some processing (perhaps leading to our request timing out?), but on subsequent fetches it works because it quickly serves a cached page?
This is all just theory, but it seems strange that the only time I managed to reproduce the error was the first time I tried.. -
i disabled the wp-rdfa wordpress plugin, and now the feed is valid, but still no result. the plugin didn't cause any problem for a long time btw, and there are non caching features at all, i don't have that much traffic :)
if i tried parsing the feed a second time, twitterfeed said it' OK, but still: [feed status: feed checked 2009-11-07 22:00:23 : we couldn't parse this feed, please check the URL is valid. we'll keep trying.] -
Hmm... you see, that's the odd thing, the second request works, but the first one never does. So when you test the feed yourself in twitterfeed, the first time it seems to fail, but the second time it works. This does seem to suggest that it returns something else the first time. The problem is that when processing the feed, it will only check it once, so that's probably why it fails.
We're in the process of rolling out a new back-end, so for now I have moved your feed to the new backend in the hope that this will work differently (but will have to wait and see, not sure right now if it makes a difference). -
yes, it does work now! strange, and i have no ide what it might return the first time. -
Inappropriate?Did the feed processing server crash againg? Our feed status: "feed checked 2009-11-07 09:13:46: we couldn't parse this feed, please check the URL is valid." But the RSS-Feed and the URL http://pipes.yahoo.com/pipes/pipe.run... are OK!? What's the problem!?
-
This is almost certainly related to a problem that Yahoo! Pipes seem to have at the moment, see http://getsatisfaction.com/twitterfee...
Loading Profile...



EMPLOYEE
