Changing MyBrand to Google: still getting a 404

[Reid]

I went to change my MyBrand recently after moving my feeds from
Feedburner to Google. I have to contact my host (Bluehost) to create
a CNAME. They changed the CNAME to this:

feeds.areseven.com. 14400 IN CNAME
aresevengmail.feedproxy.ghs.google.com.

But while http://feedproxy.google.com/areseven brings up the feed just
fine, http://feeds.areseven.com/areseven brings up a 404.

It's been 6 days since the CNAME was changed.

Is there something else I need to do on the Feedburner side to get the
MyBrand to recognize the new feed? The MyBrand screen in My Account
reads feeds.areseven.com

Thanks to whoever can help me out with this!

[Tsoots]

I am having this very same problem and would appreciate some help.
Workaround page (http://groups.google.com/group/feedburner/web/known-
issues-workarounds) has a solution that may work for some but in my
case it is not possible to follow the steps since my own domain does
not appear on the Mybrand page. And if I try to add my custom domain
there it'll say the domain is already in use.

[Grant Barrett]

I have the same problem. I had the Feedburner MyBrand working fine.
But now after switching the account to Google, I get a 404 error. I
used the workaround, but it's less than perfect because it redirects
to the old Feedburner domain.

The Google-provided host name that is giving the 404 error:

http://grantbarrettgmail.feedproxy.ghs.google.com/

The host name that should be pointing to it:

http://feeds2.waywordradio.org/

The CNAME is entered correctly, is propagated, and is doing what it is
supposed to.

The only way it is works is to use feeds2.feedburner.com instead of
the first host name above. But that, apparently, is going to go away
soon. I hope this problem is resolved before then.

[Gluek]

Same problem with my feed:

feeds CNAME mrgluekgmail.feedproxy.ghs.google.com.

http://feeds.gluek.info/gluek --> 404!

http://feeds2.feedburner.com/gluek -> OK.

On Jan 13, 10:47 pm, Reid wrote:
> I went to change my MyBrand recently after moving my feeds from
> Feedburner to Google.  I have to contact my host (Bluehost) to create
> a CNAME.  They changed the CNAME to this:
>
> feeds.areseven.com.   14400   IN      CNAME
> aresevengmail.feedproxy.ghs.google.com.
>
> But whilehttp://feedproxy.google.com/aresevenbrings up the feed just

> fine,http://feeds.areseven.com/aresevenbrings up a 404.

[Tsoots (2)]

I am not even able to activate MyBrand with the domain name I used
with the old feedburner.com account. Needless to say all my
subscribers have subscribed to this domain. At the MyBrand page when
activating all I get is 'The domain "feeds.tsoots.fi" you specified is
already in use.'

On 22 tammi, 15:15, Gluek wrote:
> Same problem with my feed:
>
> feeds   CNAME   mrgluekgmail.feedproxy.ghs.google.com.
>
> http://feeds.gluek.info/gluek--> 404!
>

> http://feeds2.feedburner.com/gluek-> OK.

>
> On Jan 13, 10:47 pm, Reid wrote:
>
> > I went to change my MyBrand recently after moving my feeds from
> > Feedburner to Google.  I have to contact my host (Bluehost) to create
> > a CNAME.  They changed the CNAME to this:
>
> > feeds.areseven.com.   14400   IN      CNAME
> > aresevengmail.feedproxy.ghs.google.com.
>
> > But whilehttp://feedproxy.google.com/aresevenbringsup the feed just

> > fine,http://feeds.areseven.com/aresevenbringsup a 404.

[Bkno]

I'm getting 404s too.

On the help pages it says

# Click the remove link next to your current MyBrand domain(s), and
then click Save.
# Re-enter the domain(s) you removed in the previous step and then
click Save.
# Try to view the feed(s) that were showing 404 errors before. They
should now display your content.

Have done this but still get 404s.

Anyone get this working since having to change the Cnames? My
subscriber count is now 1% what it was.

[Scott Johnson]

I'm getting the same result, too. Google apparently has broken
MyBrand with the conversion over to the Google system. So, Google,
what do you have to say for yourselves? Our subscribers are currently
gone. To fix this, we will have to create new sites on our "feeds"
domains with redirects to the new feed location. Should we just drop
feedburner at this point? Or will you fix this problem?

-Scott

> > > > But whilehttp://feedproxy.google.com/aresevenbringsupthefeed just

[Scott Johnson]

Update: From my end, this is truly a problem with the FB->Google
conversion. I removed one domain, deactivated the MyBrand service
(removing the primary domain), and readded/activated. Problem gone!

-Scott

[Reid]

Fantastic! Deactivating and then re-activating MyBrand did the
trick. Thanks for sharing that, Scott.

[Tsoots (2)]

I have nothing to deactivate and if I try to activate with the same
domain name I used with my feedburner.com account I get an error
message telling me 'The domain "feeds.tsoots.fi" you specified is
already in use.'

[MJJames]

Thanks Scott for this tip, solved my feed issue straight away, I was
getting annoyed at having no feed for 2 days!

[Aarononontheweb]

I am also experiencing this issue still - how long did you have to
deactivate your MyBrand for? How long did you have to wait until the
Google feedproxy address stopped spitting up 404 errors?

On Jan 23, 1:30 pm, MJJames wrote:
> Thanks Scott for this tip, solved my feed issue straight away, I was
> getting annoyed at having no feed for 2 days!
>
> On Jan 23, 6:47 pm, Scott Johnson wrote:
>
> > Update:  From my end, this is truly a problem with the FB->Google
> > conversion.  I removed one domain, deactivated theMyBrandservice
> > (removing the primary domain), and readded/activated.  Problem gone!
>
> > -Scott
>
> > On Jan 23, 12:45 pm, Scott Johnson wrote:
>
> > > I'm getting the same result, too.  Google apparently has broken

> > >MyBrandwith the conversion over to the Google system.  So, Google,

> > > what do you have to say for yourselves?  Our subscribers are currently
> > > gone.  To fix this, we will have to create new sites on our "feeds"
> > > domains with redirects to the new feed location.  Should we just drop
> > > feedburner at this point?  Or will you fix this problem?
>
> > > -Scott
>
> > > On Jan 22, 11:26 am, Bkno wrote:
>
> > > > I'm getting 404s too.
>
> > > > On the help pages it says
>

> > > > # Click the remove link next to your currentMyBranddomain(s), and

> > > > then click Save.
> > > > # Re-enter the domain(s) you removed in the previous step and then
> > > > click Save.

> > > > # Try to view the feed(s) that were showing404errors before. They

> > > > should now display your content.
>
> > > > Have done this but still get 404s.
>
> > > > Anyone get this working since having to change the Cnames? My
> > > > subscriber count is now 1% what it was.
>
> > > > On Jan 22, 1:55 pm, Tsoots (2) wrote:
>

> > > > > I am not even able to activateMyBrandwith the domain name I used

> > > > > with the old feedburner.com account. Needless to say all my

> > > > > subscribers have subscribed to this domain. At theMyBrandpage when

> > > > > activating all I get is 'The domain "feeds.tsoots.fi" you specified is
> > > > > already in use.'
>
> > > > > On 22 tammi, 15:15, Gluek wrote:
>
> > > > > > Same problem with my feed:
>
> > > > > > feeds   CNAME   mrgluekgmail.feedproxy.ghs.google.com.
>
> > > > > >http://feeds.gluek.info/gluek-->404!
>
> > > > > >http://feeds2.feedburner.com/gluek-> OK.
>
> > > > > > On Jan 13, 10:47 pm, Reid wrote:
>

> > > > > > > I went to change myMyBrandrecently after moving my feeds from

> > > > > > > Feedburner to Google.  I have to contact my host (Bluehost) to create
> > > > > > > a CNAME.  They changed the CNAME to this:
>
> > > > > > > feeds.areseven.com.   14400   IN      CNAME
> > > > > > > aresevengmail.feedproxy.ghs.google.com.
>
> > > > > > > But whilehttp://feedproxy.google.com/aresevenbringsupthefeedjust
> > > > > > > fine,http://feeds.areseven.com/aresevenbringsupa404.
>
> > > > > > > It's been 6 days since the CNAME was changed.
>
> > > > > > > Is there something else I need to do on the Feedburner side to get the

> > > > > > >MyBrandto recognize the new feed?  TheMyBrandscreen in My Account

[Mark Wilson]

I deactivated and reactivated my MyBrand last night and it seemed to
make the change almost straight away - certainly within the hour.

HTH, Mark

[Mekk]

I am yet another one beaten by this problem.

Deactivating and reactivating indeed helped, almost immediately
(surely no more than one minute)