Verify BlogSpot And Domain URLs

Whenever dealing with any problem with a blog, you should verify the URLs involved.

Some of the most baffling problems, with blog connectivity, identity, or ownership, can start from simple typographical errors. This possibility will involve both native "blogspot.com" and custom domain URLs.

The Publishing wizard window, in the Blogger dashboard Settings - Basic page, is essential for identifying errors. Whether you paste or type a URL into the registrar's zone editor, the Publishing wizard, or the browser address window, you can make a mistake. Checking the Publishing wizard is as important as examining a Dig log extract - or as viewing an HTTP trace.

Verifying the URLs involved, in the dashboard Publishing wizard, is as important as examining a Dig log extract, or an HTTP trace.

This will be the case, when dealing with various "blogspot.com" connectivity problems, researching a custom domain problem, or a dashboard or ownership problem.

Both screen prints, and text copies, are very useful - and not redundant.

Both a screen print, and a text copy, of the Publishing window (and / or the browser address window) is very useful, when diagnosing connectivity problems - or possibly, researching ownership issues, or similarly vanished blogs. And with a custom domain, similar detail from the registrar zone editor is useful.

A text copy of the contents is needed, to avoid having to re type the URL - and maybe cause a different problem when comparing the URL. And a visual copy of the Publishing wizard is good, to identify the context of any problem.

Let's look at two blogs - and what we need to examine / verify.

My test blog, published as "nitecruzr-test-ssl.blogspot.com".

Here, we see a "blogspot.com" URL, in the browser address window.

http://nitecruzr-test-ssl.blogspot.com

Here, we see the Blogger dashboard Settings - Basic page, for a "blogspot.com" published blog.

The Publishing display, for a "blogspot.com" published blog.



Useful text details, from Publishing, for a "blogspot.com" published blog:

nitecruzr-test-ssl.blogspot.com                                  Edit

If you are requesting assistance with your native Blogger blog, the latter details, in both a screen print and text copy, will be useful.

My blog, published as "blogging.nitecruzr.net".

Here, we see a custom domain URL, in the browser address window.

http://blogging.nitecruzr.net

Here, we see the Blogger dashboard Settings - Basic page. for a custom domain published blog.

The Publishing display, for a custom domain published blog.



Useful text details, for a custom domain published blog:

blogging.nitecruzr.net                                                  Edit
bloggerstatusforreal.blogspot.com                               redirects

With a custom domain published blog, next click on "Edit", and make a second screen print.

The second page of the Publishing display - which only applies to a custom domain published blog.


You maybe have seen this display, similarly formatted, in an infamous "Error 12" or similar display.

The domain root redirection, properly selected.



More essential details, for a custom domain published blog:

Third party domain settings
http://  blogging.nitecruzr.net
  X   Redirect nitecruzr.net to blogging.nitecruzr.net.

If you are requesting assistance with your custom domain published Blogger blog, the latter details, in both a screen print and text copy, will be useful.

A zone editor display, for my domain "nitecruzr.co.uk".


A zone editor display, from GoDaddy. Every registrar will have a different display.


If you purchased the domain using a credit or debit account, the bank statement and / or charge advice will frequently have a description which details the purchase. In some cases, this will include the domain name.

Comparing the URLs in the browser window, and in the Publishing window - and in Dig logs and zone editor displays (for custom domains) - we can identify typographical errors, and other mistakes. Typographical errors can be a cause of various problems, when publishing blogs to custom domains - and to "blogspot.com".

Some problems result from failure to copy and paste, properly. They can be as challenging to diagnose, as failure to observe registrar name server syntax.

Having verified the URLs, in some cases, you will continue with an affinity diagnosis, and with a differential diagnosis. This is all part of my simple 12 link test set.

You, the blog owner, may consider "duplicate" and "redundant" to be synonyms. When we research a blog problem, "duplicate" != "redundant". Many confusing problems have been solved, by comparing combinations of various above details - and by finding inequality, in one or more displays.

---

Diagnosing problems with #Blogger blogs can require careful diagnostics, using details found in dashboard screen prints and detail text copies, in Dig logs, and in HTTP traces. All details must be carefully compared, both visually and using text extracts, to diagnose some problems.

Much of this may seem superficial, to experienced support analysts - yet be obscure to some blog owners.

Custom Domain Publishing - Moving Back To BlogSpot, Using The New GUI, Isn't Obvious

The New Blogger GUI (2011) has been available for just over 6 months - and we see new confusion about using it, daily, in Blogger Help Forum: How Do I?.

How do I cancel my custom domain redirect, in the New GUI?

This is one specific question, that's been asked, recently.

The answer to that specific question is actually right there, in front of us - we just don't see it.

Blogger, like Google, likes to use overlay panels for some displays, such as how you see the picture below - when you click on it.

In the new GUI, if I look at the Blog Address settings for this blog, in Settings - Basic - Publishing, I see

See the "X"?
(Click on the picture, to better see the details.)



"Edit" is a link, that lets me "Edit" my custom domain settings. The "Edit" wizard (which simply pops up in the same display, when I click on "Edit") does not let me change the URL of the blog back to BlogSpot - and this is the start of some confusion.

To remove the custom domain redirect, and re publish the blog to the domain - or publish back to BlogSpot - one must click on the "X" in the top right. With the publishing shown as

blogging.nitecruzr.net                Edit               X
bloggerstatusforreal.blogspot.com     redirects

clicking on the "X" lets me remove the custom domain redirect. Clicking on "Edit" only lets me change specific custom domain settings, such as selecting the "naked domain" redirect option.

When you click on the "X", you will get a verification popup.

Are you sure? This will remove the current custom domain.

And you'll want to hit "Yes".

So, click on the "X" (it's actually in black - I show it in red, above, to make it more obvious), to clear the custom domain redirect and publish back to the original BlogSpot URL. If you don't see the "X", click in the upper right corner of that window - to the right of "Edit" and just left of the window border. Apparently, not all browsers display the "X" properly.

The "Buy a domain for your blog" Wizard Is Broken

Sometimes, you have to tell people something twice, before they will listen to you. This month, the "Buy A Domain" wizard has that problem.

As always, start from Settings - Publishing, and select "Switch to: • Custom Domain". If you were buying "mydomain.net", for "What address would you like your blog to have?" you should simply enter "mydomain", select ".net", then hit "Check Availability". This month, if you do that, you will see

There was an error processing this form. Please try again.

URL should end in a valid domain extension, such as .com or .net.

In this case, you must enter "mydomain.net", then select ".net". The ".net" bit is validated, too. If you enter "mydomain.com", then select ".net", you'll get the same error.

Strange, but true.

>> Top

FTP Publishing - October 2009

This month, we have several reports from bloggers who, for one reason or another, have changed the FTP username and / or password on the domain host server, and then updated the username / password in their Blogger FTP settings. Much to their dismay, when attempting to publish their blog, they find the old username / password being sent to the remote server.

I have verified it's saving my new username in the publishing settings and yes, I'm seeing the error based on the posting status. I get the following ...

FTP login failed (server: ftp.domain.com, username: myoldusername, reason: 530 User myoldusername cannot log in. )

Are you seeing this behaviour, when trying to publish your blog?

• What is the blog URL?
• What is the FTP server setting?
• When did you make the setting change?
• Did you verify the problem, by examining the host server activity logs?

>> Top