A Solution to "Another blog is already hosted at this address." error - Something Is Broken

Message from discussion A Solution to "Another blog is already hosted at this address." error

chip poutine

View profile

More options Mar 4 2007, 4:09 pm

From: chip poutine

Date: Sun, 04 Mar 2007 13:09:53 -0800

Local: Sun, Mar 4 2007 4:09 pm

Subject: Re: A Solution to "Another blog is already hosted at this address." error

Forward | Print | View thread | Report this message | Find messages by this author

This is the only strategy that worked for me. Thanks rustdawg for
this post, and to nitecruzr for your informative blog on the subject.

Blogger really needs to put out more complete and less ambiguous
instructions on how to make this work including the potential pit that
so many of us seemed to fall into. All the folks with the error
message stating they couldn't switch back to blogspot hosting wouldn't
trying to be doing that if the process was clear to begin with.

My main beef is under the Publishing tab, where the example provided
for Your Domain is blog.example.com - when for most folks this is
likely going to be www.example.com. I didn't have a 'blog' subdomain,
so simply entered 'example.com' as per the implied direction. Big
Mistake. Enter the monolithic error. Who knew I'd have to sign up
for Google Apps to make it all go away.

Anyway. Its all behind me. Catching up on sleep now. Thanks again.

On Feb 4, 4:46 pm, Rustdawg wrote:

> A solution has been found.....

> A very BIG THANKS to gergely.takacs in this thread (http://
> groups.google.com/group/blogger-help-troubleshoot/browse_thread/thread/
> 289f09679002b73f/4eeef06e4fcd8984?lnk=gst&q=Another+blog+is
> +already&rnum=5&hl=en#4eeef06e4fcd8984)

> The problem stems from Google Apps for Your Domain....here is how I
> fixed the issue of the "Another blog is
> already hosted at this address." error.

> 1. Go to your domain registrar, (I needed reset everything to their
> default settings) and create (or change if already existing) a CNAME
> named "www" and point it to "ghs.google.com"

> 2. Logged into Google Apps for Your Domain or create a new account if
> you do not have one. (I had decided to set up an account AFTER
> originally setting up my custom domain on blogger.com....this
> inadvertently led to all of my problems)

> 3. Once logged in, from the "Dashboard" choose to ONLY add "Domain web
> pages" and click the "Add selected services" button.

> 4. Use the CNAME subdomain that has been giving the message "Another
> blog is already hosted at this address." error in Blogger as the
> address you want to publish to. (In my case "www")

> 5. From here I chose to create a simple "Google Pages" webpage just to
> confirm that my address (http://www.theviralweb.com) was indeed
> working.

> 6. Back on the Dashboard of Google Apps for Your Domain, choose to
> remove the "Domain web pages service"

> 7. Go to your blog on blogger.com and change the custom address to the
> problematic address (In my case "www.theviralweb.com"), blogger should
> now allow it.

> 8. In my case, when I would click the "View Blog" link...blogger now
> took me to the Google Pages page I had just created in Google Apps for
> Your Domain.

> 9. This step my be redundant and actually just require time for the
> DNS to refresh, but I logged back into Google Apps for Your Domain and
> proceeded to add the "Domain web pages service" back, but this time I
> used a different subdomain (not "www" but instead I used "blog"). I
> never bothered to set up a CNAME in my registrar settings as I was
> only attempting to get Google Apps for Your Domain to "let go" of the
> "www" subdomain.

> 10. All of these actions soon caused the "Google 404 not found" page
> to appear for my site address.

> 11. I then proceeded to again remove the "Domain web pages service".

> 12. After only a few moments of waiting for the DNS to catch up, my
> domain (http://www.theviralweb.com) was now working and opening my
> blog.

> I would again like to thank gergely.takacs for his information, and I
> wish I could say that I have repeated all these steps to confirm they
> are correct....but I would rather not loose control of my domain
> again...so this info is provided as-is and I just hope it works for
> everyone who has had this same problem over the past few weeks.

> Rustdawg

Forward