Error getting URL: 999 - Unknown

[FredB]

I've tried to transition from my Feedburner account to my Google
account. All of my Feeds transferred correctly except the feed
originally at...

http://feeds.feedburner.com/GoogleBlogSearchthemeTimeRadioHour

The proxy page

http://feedproxy.google.com/GoogleBlogSearchthemeTimeRadioHour

displays a 502 error message and claims the URL is unknown.

The original Feed is a delicious bookmark page at...

http://feeds.delicious.com/v2/rss/fhbals/ttrh

The page URL is http://delicious.com/fhbals/ttrh

I've tried to re-create the Feedburner feed and get an error message
saying that the Feed is unknown. I get the same message if I enter in
the page URL. The Feed is valid according to Feedvalidator. This
worked perfecltly in the "old" Feedburner. How do I fix this issue?

[Franklin Tse [Community Expert]]

Hello,

I will forward your case to the FeedBurner Team for investigation.
Please stay tuned.

[Franklin Tse [Community Expert]]

The Traffic Team is trying to fix the 99 error.

[FredB]

Thank you. I look forward to more info.

[superzed]

I have the same problem after transfering feedburner account to google
account with a delicious feed
(An error occurred connecting to the URL: Error getting URL: 999 -
Unknown


Identify Feed Source
Back to My Feeds
The feed URL you entered is:

http://feeds.delicious.com/v2/rss/nouvelleMARQUE/nouvelle-MARQUE?count=15)

[Mindy]

I have the same error, and I suspect it's because the "feed address"
in the "edit feed details" section remains a http://feeds2.feedburner.com
feed.

[Franklin Tse [Community Expert]]

I am sure that Team is working on the issue. Will ask them for more
info.

[Werner]

I had the same problem and played around.
I used: http://feeds.delicious.com/v2/atom/USER/TAG
instead of the delicious standard feed address http://feeds.delicious.com/v2/rss/USER/TAG
i other words i changed "rss" to "atom"
and this works fine. Do not aks me why.

On Jan 14, 4:24 pm, FredB wrote:
> I've tried to transition from my Feedburner account to my Google
> account.  All of my Feeds transferred correctly except the feed
> originally at...
>
> http://feeds.feedburner.com/GoogleBlogSearchthemeTimeRadioHour
>
> The proxy page
>
> http://feedproxy.google.com/GoogleBlogSearchthemeTimeRadioHour
>
> displays a 502 error message and claims the URL is unknown.
>
> The original Feed is a delicious bookmark page at...
>
> http://feeds.delicious.com/v2/rss/fhbals/ttrh
>

> The page URL ishttp://delicious.com/fhbals/ttrh

[Werner]

If a little man like me can make this work, why a powerful corporation
like Google is not able to answer such simple questions ?

"He pumped your gas and he cleaned your glass
And one cold rainy night he fixed your flat
The new stores came where you do it yourself
You buy a lotto ticket and food off the shelf
Forget about the little man
Forget about that little man" (Alan Jackson)

[Simon L.]

Changing "rss" to "atom" worked for me, too.

[FeedBurner Admin]

We have been trying to contact the right people at Yahoo to solve this
problem, but it has not been resolved as of yet. You may wish to do
the same.

[Rogi]

Changing rss to atom does _not_ work for me (I'm using Yahoo Pipes).

My feed:

http://pipes.yahoo.com/pipes/pipe.run?_id=qgMnJH1M3BG6EL4ro_NLYQ&_render=rss

Feedburner/Google says 'Error getting URL: 999 - Unknown' which,
clearly, is wrong.

[Mindy]

The change from rss to atom in the delicious feed worked for me.
Thanks!

[Werner]

@Rogi, i never said that this is a fix for Yahoo Pipes.
I described this for Delicious feeds only.

On Jan 26, 12:17 pm, Rogi wrote:
> Changing rss to atom does _not_ work for me (I'm using Yahoo Pipes).
>
> My feed:
>

> http://pipes.yahoo.com/pipes/pipe.run?_id=qgMnJH1M3BG6EL4ro_NLYQ&_ren...

>
> Feedburner/Google says 'Error getting URL: 999 - Unknown' which,
> clearly, is wrong.
>
> On Jan 26, 5:12 am, FeedBurner Admin wrote:
>
>
>
> > We have been trying to contact the right people at Yahoo to solve this
> > problem, but it has not been resolved as of yet.  You may wish to do

> > the same.- Hide quoted text -
>
> - Show quoted text -

[FredB]

Worked for me (currently at least) too, Werner, thanks.

Interestingly, I had created a workaround using Yahoo Pipes (that is,
ported in the delicious feed into the pipe, than used the pipe feed in
Feedburner), which originally worked and stopped working over the
weekend with the damnable 999 error. So I tried the change rss to
atom fix on the delicious feed and it's now working.

I think it's a little disingenous to be using the excuse "We have been
trying to contact the right people at Yahoo to solve this problem..."
as it's obvious that the problem is on Feedburner/Google's end and has
something to do with the migration. Why doesn't Google simply revert
us back to the "old" Feedburner, and go build a sandbox where they can
work out these problems without impacting their users.

[Rogi]

Thanks Werner,

I did realise that but was hoping that a Google person would pick up
on it.

No luck though.

Think I'll abandon Feedburner and go direct to Pipes.

[CBL]

I call this a regression, ie. the worst kind of bug. All my feeds a
screewed up, got a lot from yahoo pipes. This regression is Google's,
not yahoo's. Please fix it asap.

> > Changing "rss" to "atom" worked for me, too.- Hide quoted text -

[Werner]

I researched a bit on the Yahoo Pipe problem although i am not relying
on Pipes myself.

1. There are no problems with using Yahoo Pipes in Google Reader.

2. There are no problems with using Yahoo Pipes with the Google Feeds
API, e.g. feedControl.addFeed(...)

3. There are however problems in the (undocumented) Google Reader
"API", e.g.
http://www.google.com/reader/atom/feed/http://feeds.delicious.com/v2/rss/?count=15
is working perfect, whereas
http://www.google.com/reader/atom/feed/http://pipes.yahoo.com/pipes/pipe.run?_id=qgMnJH1M3BG6EL4ro_NLYQ&_render=rss
DOES NOT WORK

I always thought they are running all this RSS stuff on a common feed
fetching infrastructure and the
reason for the recent feedburner changes was the migration to this
common Google "ecosystem".

Btw, what is the role/responsability of a Google Forum "Community
Expert" ?

> > - Show quoted text -- Hide quoted text -

[TLWH]

Yahoo Pipes have added the IP's Google mention in http://feedburnerstatus.blogspot.com/

They said it would be a few hours or even days before it propagates.

I do see the feeds at http://feeds.feedburner jumping back to life
for 2 hours at a time, then they die. http://feeds2.feedburner has
been down 3 days now for pipes.

On Jan 28, 1:28 am, Werner wrote:
> I researched a bit on the Yahoo Pipe problem although i am not relying
> on Pipes myself.
>
> 1. There are no problems with using Yahoo Pipes in Google Reader.
>
> 2. There are no problems with using Yahoo Pipes with the Google Feeds
> API, e.g. feedControl.addFeed(...)
>
> 3. There are however problems in the (undocumented) Google Reader

> "API", e.g.http://www.google.com/reader/atom/feed/http://feeds.delicious.com/v2/...
> is working perfect, whereashttp://www.google.com/reader/atom/feed/http://pipes.yahoo.com/pipes/p...

[Franklin Tse [Community Expert]]

Yahoo! is still blocking the feeds2.feedburner. Nothing can be done by
FeedBurner unfortunately.

[Handride]

What's the timeframe on Yahoo Pipes RSS working at Google. This is
very poor. and multiple topics are talking about it.

[TLWH]

"Yahoo! is still blocking the feeds2.feedburner"

http://discuss.pipes.yahoo.com/Message_Boards_for_Pipes/threadview?m=te&bn=pip-genDiscuss&tid=1987&mid=-1&tof=1&rt=2&frt=2&off=1&p=u_aFs.jAWsR6P9Wnje18586YQ9QWbn7ISJMqEFk-

They've added the required IP addresses

[Werner]

Unfortunately there was too much smoke und no real information.
Google realized much too late that we need a much more open
communication policy,
but fortunately finally understood, e.g. see
http://feedburnerstatus.blogspot.com/2009/01/error-999-when-viewing-or-burning-new.html

If a Community Expert is really blaming some others, e.g. Yahoo for
the problems, then i
expect to hear the complete real story of the root cause after the
issues have been resolved.

I really do not blame anybody for the problems, such a migration is a
complex venture and it may
take some time and collateral complications are to be expected.

But if there are problems, i expect a fast rational explanation not
leaving me in the dark.

On Jan 28, 1:20 pm, TLWH wrote:
> "Yahoo! is still blocking the feeds2.feedburner"
>

> http://discuss.pipes.yahoo.com/Message_Boards_for_Pipes/threadview?m=...

>
> They've added the required IP addresses
>
> On Jan 28, 7:12 pm, Franklin Tse [Community Expert] wrote:
>
>
>
> > Yahoo! is still blocking the feeds2.feedburner. Nothing can be done by

> > FeedBurner unfortunately.- Hide quoted text -

[nathanziarek]

I don't think it is fixed. I've been trying for 40 minutes, with both
RSS and ATOM and repeatedly get the same error. The feeds from
delicious themselves are fine. Since this issue seems to have been
"fixed" on Jan 30, and it is now March, thoughts on what else I could
possibly try?

Thanks!

[Franklin Tse]

It was fixed, but it appears not currently. I have reported the issue
to the Team.