Recovering From A Corrupt Template - Persistence

Of the many Blogger Mysteries that confound blog owners and readers, none are more obscure than the many bX codes.

Some problems, reported in Blogger Help Forum: Get Help with an Issue, start so innocently.

As I edited the Template HTML, I saved my changes - and the bX error suddenly appeared.

Each different bX code refers to a different problem, with Blogger in general. Of the bX codes that refer to template corruption, each different bX code may refer to a different template corruption problem.

When a template corruption problem can be reset, the resetting process may involve repeated use of one or more dashboard pages.

Different problems may enable - or prevent - use of a different dashboard page. For problems with multiple causes, you may have to use each different wizard, persistently.

1. The Template Designer page.
2. The Template page.
3. The Template Editor ("Edit HTML") page.
4. If the blog is not operational, you start again.

Unfortunately, some problems may prevent use of all 3 pages. For the problems that permit use of one or more pages, you try each available page, repeatedly, until the blog becomes operational.

To access each page, you may need to bypass the dashboard menu.

The Template Designer page.

The Template Designer is used for one task - "Remove customizations".

The Template Designer.



"Remove customizations" may be the simplest reset that you may try - when possible. Some customizations, when removed, may enable subsequent use of the Template page, or the Template Editor.

The Template page.

The Template main page is used for two tasks.

1. Backup / Restore the existing template.
2. Get a new template.

The Template main page.



Some problems, when reset using the Template main page, may enable subsequent use of the Template Designer, or the Template Editor.

The Template Editor ("Edit HTML") page.

The Template Editor ("Edit HTML") is used for two tasks, as an alternate to the Template main page. Also, it may be used to reset any "rgba" colour combination problems.

1. Backup / Restore the existing template.
2. Get a new template.

For template corruption problems that prevent use of the Template main page, the Template Editor - combined with a second blog, where a clean template is developed and tested - can be used.

The Template Editor (aka "Edit HTML").



Some problems, when reset using the Template Editor, may enable subsequent use of the Template Designer, or the Template main page.

If the blog is not operational, you start again.

If you get a new bX code, you repeat the above sequence. Some problems, with multiple causes, may require repeated retries.

In extreme cases, you may end up creating a new blog at the URL.

---

Some #Blogger template problems, which lead to a bX code display, may have multiple causes - and all causes may require solution, to make an affected blog operational. With some causes preventing solution of others, a repetitious use of the various dashboard pages may be required - to solve some template corruption problems.

Some bX Codes Caused By Zero Alpha ("rgba") Value

We're seeing a few reports of bX codes, that are not solved by simply resetting the template - and do not involve the mysterious "500 Internal Server Error".

In some cases, the blog owner may see a bX code when trying to use "Configure Blog Posts", or another Layout gadget wizard. If the blog itself can be viewed, and Template HTML Editor is usable, the bX error may come from use of a "0" Alpha color setting.

Blogger Engineering is aware of the problem, and has suggested that a fix is being developed. While we await the necessary fix, we may need to work around the problem.

The suggestion by Blogger Engineering is that we use a "Transparent" option, instead of "0" alpha value.

It seems that this issue is triggered by color variables with a value that has zero alpha, e.g. 'rgba(0, 0, 0, 0)'.

Some gadgets, and template sections, have the "transparent" selection in their color setup. Not all have this option, however. Some template CSS rules are not so easily edited.

The problem here is the "rgba" 4th value of "0" - ie, the "alpha" "0" value. The simplest solution is to change the "0" to a non zero value - without changing the "rgb" values.

The simplest solution, to get "Configure Blog Posts" or any other affected gadget usable, may be to use Template Editor, and change the values, directly. Look at every CSS rule, that has an "rgba" setting - and look for a 4th value of "0".

• For "rgba(0, 0, 0, 0)" - Change to "rgba(0, 0, 0, .1)".
• For "rgba(255, 255, 0, 0)" - Change to "rgba(255, 255, 0, .1)".
• For "rgba(255, 255, 255, 0)" - Change to "rgba(255, 255, 255, .1)".

A transparency setting of ".1" should be visually close to "0" - and should get the blog in question back online and updatable. And after Blogger Engineering fixes their gadget / template editor code, to accept the "0" value - and if the ".1" creates a noticeably unacceptable condition - this can be corrected, when necessary.

It's possible that this error, being seen, is part of a larger problem. You may need a persistent solution.

---

Some #Blogger bX codes, being seen in the forums right now, do not appear to involve terminal template corruption, and the mysterious "500 Internal Server Error". Some bX codes can be easily corrected, when they involve a "0 alpha" value (a CSS color rule involving an "rgba" setting).

When the Template Editor is usable, a simple search and replace for "rgba(nn, nn, nn, 0)" to "rgba(nn, nn, nn, .1)" may be sufficient to correct the error.

Recovering From The Corrupt Template / "Error 500"

We're seeing a few reports, this week, in Blogger Help Forum: Get Help with an Issue, about blogs with broken templates.

I tried to log on to my blog, and it shows up an error message. I've done it several times on different browsers, but no change: the error code is bX-uukqqu.

It appears that the "bX-uukqqu" is from the owner attempting dashboard access. Trying to view the same blog, I see the ubiquitous "bX-v2vqfh".

Both codes reference blogs which show up, in an HTTP trace, with the monolithic message "500 Internal Server Error" - and tells us that this is one more blog with a broken template.

If you, the owner of a blog with a broken template, can access the Template dashboard page, you may be able to recover the template.

Some blog owners report that adding a Template Backup / Restore has helped to resolve their own bX code / "Error 500".

1. Backup the template ("Download full template").
2. Get a clean Blogger standard template.
3. Restore the template ("Upload" the template that you just downloaded).

If you're lucky, your version of the "bX-uukqqu" (dashboard) / "bX-v2vqfh" (public) can be resolved, by a quick template download then upload.



You may need direct access to the Template page, bypassing the dashboard menu - though if you can view the blog, the "Design" navbar link will provide you that ability. If you can't access the Template page at all, you may be able to clear some bX codes, by using the Template Editor aka "Edit HTML".

If any of this works, your blog will be back in service. If not, you will at least have a backup copy of the template.

If the template is still broken, you now have three choices.

1. Leave the blog as it is now, broken - until Blogger Engineering finishes diagnosing and fixing the actual cause of the template corruption.
2. Get a fresh new template. When Blogger Engineering finishes diagnosing and fixing the actual cause of the template corruption, you can try restoring the template copy that you just backed up.
3. Try a persistent solution.

And whether this works - or not - or even if you can't use it, right now, you can have a template backup. And one day, this backup may be useful.

---

A few Blogger blog owners, reporting bX codes when trying to access their dashboards, have found that accessing the Template page directly, then doing a quick back / restore, may clear the bX codes. This suggests that Blogger Engineering is beginning to test solutions to the ubiquitous "Error 500" broken template problem, that have been afflicting blog owners for some time.

---

Use Of Internet Explorer V11 Causes bX-w7tr63 Error

We have numerous blog owners report that they cannot access their Blogger dashboards.

Every time I login to Blogger, I get

We're sorry, but we were unable to complete your request.
When reporting this error to Blogger Support or on the Blogger Help Group, please:
Describe what you were doing when you got this error.
Provide the following error code.

bX-w7tr63

What should I do?

The only answer here is to reply

Don't use Internet Explorer V11.

In Blogger Help: Compatible browser and operating systems, we notice, quite conspicuously, the absence of Internet Explorer 11, from the table.

Blogger works with the following browsers and operating systems:

The most current version of Internet Explorer listed is V10, with the annotation

* For best results, turn off Compatibility View.

If you have a computer with Internet Explorer V11, you're going to need a third party browser - Chrome or Firefox. Otherwise - sorry - you won't be able to use Blogger.

Apparently, IE V11 contains too many internal changes, for Blogger Engineering to update the dashboard utilities, so IE V11 will be reliably usable - Compatibility View enabled, or disabled. Blogger has simply decided to not support IE V11, until they can properly update.

Like the predecessors, "bX-rjv21c" and "bX-sf96g4", this bX code can be cleared only by action of the blog owner - who must use a different browser, to access the Blogger dashboard.

Not All bX Error Codes Are Temporary

Everybody who has owned or read a Blogger blog, for more than a week, surely knows about the infamous bX codes - and has probably asked how to fix one.

Some people have fixed one - but immediately, seen another. Others have seen theirs go away, then later discovered that the blog is broken.

Some folks see the errors as major problems, others minor annoyances.

it's disheartening to see that the bx error code problems are still existing.

Not everybody realises that the codes are not the problems - they are simply a method to identify the problems. Many Blogger problems cannot be identified easily in language.

Many problems, many "solutions"
There are many known "solutions" for the codes, because there are many different problems, with many different causes. Here, we have 5 examples.

• Some codes are caused by an inconsistency in private data. These codes can generally be cleared by "clearing cache, cookies, and sessions".
• Some codes are caused by over enthusiastic template customisation. These codes can be cleared by getting a new template, or restoring the template from backup, for the blogs that are issuing the code.
• Some codes are caused by bogus custom domain addressing, for the blogs that are issuing the code. These codes can be cleared, only, by correcting the DNS addressing, for the blogs that are issuing the code.
• Some codes are caused by trying to use an unsuitable browser. Right now, Blogger does not support Internet Explorer V11 These codes can be cleared only by using a different browser.
• Some codes are caused by dodgy Blogger code. These codes cannot be solved by blog owners or readers. The bX codes, in many cases, are simply from Blogger Engineering adding "break points" into their code, so they can diagnose a known problem.

Above, we see just 5 examples. There is one rule, which you may want to consider, when diagnosing bX codes.

There are no rules, in diagnosing bX codes.

That is the plain truth.

History
Before they started issuing bX codes, Blogger would simply issue one universal error, that was incredibly annoying, to everybody seeing it.

We apologize for the inconvenience, but we are unable to process your request at this time. Our engineers have been notified of this problem and will work to resolve it.

Replacing that error, with the unique bX codes, was so simple - and elegant. The program, that issues a bX error report, simply takes the address of the failure point in the Blogger code library, where an unacceptable condition has occurred, and hashes the address into a 6 character alphanumeric code. And there is the bX code. Yes, that simple.

Blogger keeps a database listing of bX codes that are currently active, and a running count for each code. When a given code becomes more noticeable than others, an engineer simply uses the 6 character code to locate the failure point in the Blogger code library, and diagnoses the cause of the error. Fixing the code will vary, depending upon the cause of the code.

A hypothetical example
If you add an extra "<div>" tag in your template code, using the Template Editor, it's possible that the Template Editor code may detect it, and specifically advise you.

Don't add a "<div>" tag there!

In many cases, through, an extra "<div>" tag won't be noticed until you try to save the changes - or even until a reader views the blog under specific conditions. Either of the latter two cases may result in another bX code.

When you report your bX code in Blogger Help Forum: Get Help with an Issue, if other people have reported that same code, it's possible that we might have a known solution, ready for you.

Don't add a "<div>" tag, there!

In many cases, though, you will be advised to

Restore the template from backup - or get a new template from the dashbooard Template wizard.

In either case, though, the advice to get a backup or new template is not a solution - it's a workaround. The proper solution is for you to figure out what you did, that was wrong, and correct what you did.

In some cases, if we see enough of the same code, as we do now with the "bX-w7tr63", currently being reported in Blogger Help Forum: Get Help with an Issue - we may advise you.

Blogger cannot support you, using Internet Explorer, right now.

Internet Explorer V11 has too many internal changes, for Blogger Engineering to update the Blogger dashboard utilities, and remove all known problems. That may be vaguely similar to the problems where we alternately advise.

Restore the template from backup - or get a new template from the dashbooard Template wizard.

In either case, we provide most advice based on feedback from other blog owners.

Reality
Be aware that each bX code may have a different solution. Be wary of advice that simply instructs.

Most bX errors are temporary and will usually go away on their own.
You may read [FAQ] What Are The Mysterious bX Codes? and try clearing your cache and cookies.

Some errors may go away, on their own - but most require somebody to take some action. Not all that many are temporary.

Strange Behaviour By Post Editor #2

Mindful of the volume of complaints seen in the forums today, I'll see if this post can be published.

Having tested in my previous post, it appears that posts can be updated. Now, we'll verify that new posts can be created. (1) Looking good, so far. (2) Test 1 was successful. (3) Test 2 was successful, and the updates show in the published post. And this post is visible in Edit Posts. (4) And test 3 was successful. (5) And so on. Back to work, now.

>> Forum thread links: bX-*00083

>> Copy this tag: bX-*00083

>> Top

Strange Behaviour By Post Editor

Normally, when I publish a post, I'll re publish repeatedly, to get the right content. For this post, I won't be doing that.

I just spent 1/2 hour updating another post, Another blog is already hosted at this address. I had to copy and paste some changes, from the published copy to Post Editor, when revising other changes. Here's what I did, initially.

1. Start Post Editor.
2. Make changes to an existing post.
3. Publish the changes.
4. Verify the changes in the updated post.
5. Go back to Post Editor to revise the changes.
6. The changes just made are gone.

Other bloggers claim that AutoSave doesn't work either.

Your request could not be processed. Please try again.
Auto Save failed.

And some claim problems with the posting date / time.

when i post the time it is wrong and doesn't change. keeps showing 12.08.

>> (Update 9/20 8:00): Last night, Prashant declared this episode to be over.

Recently, some of our users reported problems with editing, publishing and auto saving posts. We have released a fix which should prevent this from happening.

>> (Update 9/19 12:00): A Blogger Employee has (finally) posted a pinned thread, with a possible workaround.

Clear your browser's cache but do -not- clear your cookies.

In the process of adding this update, I note that my Post Editor shows very old contents for this post. Moving to another computer, I am able to update the current copy of my post. (1) But, to annotate the update, I have to move to yet a third computer. And I must note that the second computer is NOT typically used for composing or editing posts, so having a Post Editor article in cache there is not a possibility. And now, I am out of computers. I suspect that I will have to cease updating this post.

>> If you're still experiencing this problem, try clearing both cache and cookies, and restarting the browser. Or, try using a different browser for your editing.

>> (Update 9/18 13:00): A Blogger Employee is now asking for diagnostic details.

could you tell me the URL of the blogs you're experiencing this problem with, what Operating System (e.g. Windows XP) you're using, what Web browser you're using (e.g. Firefox, Safari, Internet Explorer), and what country you're in.

>> (Update 9/18 8:00): The problem is not 100%, and it's not consistent. I'm able to post here, now. (1) And, having posted and verified the post, I can edit and see my immediately previous change. (2) And I can correct and annotate the previous change, too. (3) And so on. (4) And now we see 4 posts in a 10 minute span of time, and no loss of updates. (5) Looks like I, at least, am back in business. (6) And see my subsequent tests, too.

>> Forum thread links: bX-*00083

>> Copy this tag: bX-*00083

>> Top

bX-e3i9af Error Possibly Not Resolved

Last weekend was a bad time for many owners of blogs published to custom domains, with numerous blogs returning the well known "404 Not Found" error in various flavours. When attempting to repair the problem, the owners were greeted with two error codes - bX-f42977 and bX-e3i9af. My home page blog, Nitecruzr Dot Net was offline for several days with this problem.

During the weekend, Blogger Support developed and pushed a fix which eliminated this problem. The fix was effective in most cases, but possibly not all.

Today, several bloggers have reported that the problem has returned. Analysis of the DNS setups show standard Google Apps style configurations; yet when attempting to publish the blogs back to BlogSpot, or repeat the publish to the custom domain, these bloggers are greeted by the bX-e3i9af error.

>> Top

Nitecruzr Dot Net Is Now Offline

This evening, the Custom Domain problem hit my home blog, Nitecruzr Dot Net. In a routine reload of the page, I was greeted with the dreaded

Server Not Found

Error 404

In attempting to recover the blog, I observed the equally unpopular

Another blog is already hosted at this address.

Having supposedly recycled the domain settings in Google Apps, I then received a final blow.

bX-f42977
Say good night, Chuck.


But do report it to Blogger, so they can diagnose the problem.

>> (Update 8/30 17:00): Nitecruzr Dot Net, in all 3 aliases, is back online.

>> (Update 8/27 15:30): Progress??

bX-e3i9af
Change is good
... or at least not boring.

We've got our top man working on it, round the clock.

>> (Update 8/30 17:00): Nitecruzr Dot Net, in all 3 aliases, is back online.

>> (Update 8/27 9:45): Blogger Support is actively looking at the problem.

>> Top

Custom Domain Repair Procedures Terminating With bX- Codes

This summary is not available. Please click here to view the post.

Cannot Upload Picture - Internal Error

For our third wildfire this month (and today being the 4th of the month yet!), we have a problem with Blogger, and Post Editor. When trying to upload a picture, the blogger sees

This image could not be uploaded due to an internal error.

One blogger reported seeing this error after installing a Pyzam template. From the volume of the posts in the forums, I don't think that's the only defining factor.

Some questions might be relevant, though. Answer as much as you can manage, please.

• Does the blog have a Blogger standard, or third party, template?
• Does the blog have a Classic or Layouts template?
• Are you in Draft (Blue), or Standard (Orange) Blogger, when you see the error?
• Has this blog ever been customised using Draft (Blue) Blogger? If so, what changes were made?
• Are you using Page Elements, or Post Editor, when you are trying to upload?
• What browser (name and version) are you using?
• What operating system (name and version) are you using?
• What security programs or devices (anti-virus, for instance) do you use to protect yourself?

>> (Update 8/4 20:00): Blogger Employee Gatsby reports that they are working on the problem.

>> Forum thread links: bX-*00081

>> Copy this tag: bX-*00081

>> Top

What Is The Solution To The Mysterious bX- Codes?

One of the reasons why Blogger code is so "unstable" (judging from the threads in the help forums) is that, as I wrote long ago, it involves code and data that starts on Blogger computers ("servers"), but is processed from other computers ("owned" by bloggers) which are connected to the Blogger computers over networks that nobody owns or controls.

Some of these factors Blogger can accept responsibility for. Others we (the blog owners, or blog readers) have to accept responsibility for. And still others are the fault of the network owners, and many of those are problems which nobody will accept responsibility for.

And that's the problem with diagnosing the ever common bX- codes. Of late, some bloggers are pumping themselves up, and declaring to the world

Finally the solution to the BX error codes of blogger.com

Don't know who and why it works and why google/ blogger have failed to recognize such simple tricks. But still that doesnt reduce its efficacy..

as if they themselves developed the simple process of clearing cache and cookies.

The frustrating part of this is that, in a very limited number of cases, clearing cache and cookies may produce positive results. But using that procedure as a general solution is so wrong, because it's limited to very specific scenarios. We need to understand the scenarios which generate the codes, before we can truly understand this.

>> Top

So, What Are The Mysterious bX- Codes About?

In the past - not so long ago, and not infrequently - you might be accessing or updating your blog, and you'd see a monolithic error message that made many bloggers want to tear their hair out by the roots.

We apologize for the inconvenience, but we are unable to process your request at this time. Our engineers have been notified of this problem and will work to resolve it.

If you've been blogging for any past amount of time, I'm sure that you remember seeing that. I know that I do.

On January 17, 2007, all of that ended. Blogger replaced that incredibly annoying message with a large series of error codes. Such a simple task, in concept. Each possible failure point in the Blogger codebase was assigned a different bX- code, replacing the old "We apologize for the inconvenience ..." message with a unique failure point code for each different problem encountered.

For all of their simplicity though, many bloggers don't seem to see the forest for the trees.

it's disheartening to see that the bx error code problems are still existing.

Many bloggers seem to associate some major significance to these codes. Some have compiled a list of codes, as if listing enough codes will help them understand the secrets of the universe. Letting somebody "look at my code list" is of special social significance, like showing my family picture album.

There is no special meaning to any code.

Long ago, people who worked with the major computer operating system in the universe ("IBM" mainframe) would maintain a library of reference manuals (yes, paper - and a lot of paper). A large portion of many libraries would be incredibly large glossaries of system termination codes. Each code would have a special significance, such as attempting to enter a date containing an alphabetic character. Seeing a given code for a specific database entry, a database engineer would look up the code in the reference manual, then patch the record in error accordingly, and the problem would be solved.

The bX- codes have no similar significance. They are simply unique codes, which identify each individual point of abnormal termination. There's no secret glossary assigning the cause for any single code, just a pointer to the individual termination point in the Blogger codebase. When enough bloggers report a given code, a Blogger employee simply examines the termination point, and using the diagnostic information hopefully provided by the bloggers problem reports, makes a diagnosis of the problem cause. Rarely, the code will be added to a small database which lists specifically significant codes.

In some cases, this will lead to solution of a given problem, and the end of that bX- code from further observation. However, just as repairing an aged engine with a few new parts, this may fix one immediate symptom but put additional stress on other parts, causing them to fail. You will see one bX- code become popular for a while, then be replaced by others later. This isn't a random scenario - it's natural.

There isn't a lot to do, when you get a bX- code. In very limited cases, clearing both cache and cookies, and restarting the browser, may help. If not, then the problem is probably in the blog that you're trying to access or update. Diagnose any changes that you recently made - then report the code, using the bX- Code Reporting Form, and let Blogger analyse the problem.

>> Top

Blogger Issuing Diagnostic Codes

In the not so distant past, and not nearly rarely enough, you might be updating, or possibly viewing, your blog, and you'd see a monolithic error message that frequently made many bloggers want to tear their hair out by the roots.

We apologize for the inconvenience, but we are unable to process your request at this time. Our engineers have been notified of this problem and will work to resolve it.

If you've been blogging for any past amount of time, I'm sure that you remember seeing that, more than once.

On January 17, 2007, all of that ended. Blogger replaced that single and incredibly annoying message with an almost infinitely large series of error codes. Very simple, that. Each possible failure point in the Blogger codebase was assigned a different bX- code, essentially replacing the old "We apologize for the inconvenience ..." message with individual failure point codes.

For all of their simplicity though, many bloggers don't seem to see the forest for the trees.

it's disheartening to see that the bx error code problems are still existing.

Many bloggers seem to associate some major significance to these codes. Some even compile a list of codes, as if listing enough codes will help them understand the secrets of the universe. Letting somebody "look at my code list" is of special social significance.

There is no special meaning to any code.

Long ago, people who worked with the major computer operating system in the universe (think "IBM" mainframe) would maintain a library of code manuals. A significant quantity of these manuals would be incredibly large glossaries of system termination codes. Each code would have a special significance, such as attempting to enter a date with an alphabetic character. Seeing a given code for a specific database entry, a database engineer would look up the code in the reference manual, then patch the record in error accordingly, and the problem would be solved.

The bX- codes have no similar significance. They are simply unique codes, which identify each individual point of abnormal termination. There's no secret glossary assigning the cause for any single code, just a pointer to the individual termination point in the Blogger codebase. When enough bloggers report a given code, a Blogger employee simply examines the termination point, and using the diagnostic information hopefully provided by the bloggers problem reports, makes a diagnosis of the problem cause.

In some cases, this will lead to solution of a given problem, and cessation of that bX- code from further observation. However, just as repairing an aged engine with a few new parts, this may fix an immediate symptom but other parts are sure to fail later. You will see one bX- code become popular for a while, then be replaced by others. This isn't a random scenario - it's natural.

Just because one bX- code stops being reported, and another (or a few more) different codes are now reported doesn't necessarily mean that Blogger fixed one problem, and caused another (or a few more). They may have just defined a few more termination points (with additional codes) in an effort to further isolate a problem. Updating your list with a few more codes doesn't mean you are doing anything to help.

Let Blogger maintain the bX- codes, and stop wasting everybody's time with claiming to know what some codes mean, and how to get a special key sequence that lets you bypass the error code screen.

>> Top

The Blog Content Warning May Not Be Voluntary, In All Cases

The "Content Warning" advisory page, appearing ahead of blogs with questionable content, protects the casual blog surfer from viewing content which may be objectionable to some readers. It's presence on any given blog is supposedly the result of voluntary action by a blog owner, who can set "Adult Content?" to "Yes", at his / her discretion.

The presence of the advisory page, supposedly has slight effect upon prospective readers of the blog.

• Prospective readers must read the notice, and decide whether they wish to view possibly gratuitous content, and that after they click through the notice.
• The blog, when listed in a search hit list, will show the text of the content warning, in place of the blog description and post extract.

Recent claims by some readers make it appear that this setting may be, in some cases, not set voluntarily, and that it has additional consequences. The warning page also seems to interfere with the ownership verification process, in Google Webmaster Tools.

>> Forum thread links: bX-*00079

>> Copy this tag: bX-*00079

>> Top

403 Forbidden Woes Continue

During the weekend of May 10 - 11, 2008, many Blogger readers were having trouble viewing our blogs. Instead of seeing The Real Blogger Status (and various other blogs of greater and lesser importance), some unhappy folks were seeing a well known problem

403 Forbidden.

Pete Hopkins, the Google Man In The Know, described the cause of the problem - the side effect of a massive Denial Of Service attack against Google, as

Blogger is currently experiencing a high level of automated requests. In order to keep Blogger running smoothly for as many people as possible, we are blocking some IPs.

and continued with

Just because your IP is blocked does not mean that you or your network is making automated requests, you've just gotten caught up in the block.

We are working to remove the incorrect blocks as soon as possible.

Yet as of this evening, it appears that not everybody is back to normal.

It's possible that you, or your readers, who are affected by this problem will be able to get around it by using a proxy server. Though you won't be reading this, if you're affected by the problem. Sorry.

For additional insight into this problem, see Robertos Report: The 403 Block.

>> Forum thread links: bX-*00078

>> Copy this tag: bX-*00078

>> Top

Custom Domain Publishing, And The 404 Error - Chronic Edition

On the surface, the old "404 Not Found" would be one problem - simply your computer saying "Hey! I can't access the other computer!". Those of us who work in computer and network troubleshooting know that there are dozens of possible causes for that one symptom.

We know, for a certainty, that if we persist in believing that there is one problem causing all of the "404 Not Found" errors, that one problem will never be solved. This symptom will be solved only with detail and determination, and lots of diagnostic work.

>> (Update: 5/18): Blogger Support is now suspecting a link between use of Google Apps, and the 404. If you are having this problem, please help us diagnose the problem. Describe your use of the following Blogger / Google applications / wizards, with any possible details (relevant dates would be useful), in setting up or maintaining your domain:

• Blogger "Advanced Settings" wizard.
• Blogger "Buy A Domain For Your Blog" wizard.
• Google Apps.

>> Forum thread links: bX-*00077

>> Copy this tag: bX-*00077

>> Top

UK Broadband Bloggers Report Computer Freezing, When Using Blogger

Bloggers in the UK, using BT as an ISP, report their computer freezing when accessing Blogger wizards.

>> Forum thread links: bX-*00075

>> Copy this tag: bX-*00075

>> Top

Custom Domain Setups Terminating With bX- Codes

During this week, we've seen a number of reports that bloggers, when attempting to setup a custom domain, are observing a variety of bX- codes. Generally in the past, most problems with custom domain setups would report the well known monolithic error

Another blog is already hosted at this address.

or possibly an equally frustrating problem

404 Not Found

recently attractively repackaged as

Blog not found

Sorry, the blog you were looking for does not exist. However, the name (your supposedly non existent blog) is available to register!

My suspicion is that, in an effort to diagnose the causes of the monolithic error messages, Blogger has added additional bX- codes into the custom domain code libraries. Maybe that's the actual reason for the addition of the request for details, with the bX- codes.

Maybe we'll eventually see a reduction in the number of custom domain setup problems in general, as Blogger identifies and resolves various weaknesses in the custom domain product. Or at least, a reduction in the number of problems that can't be solved by proper DNS setup.

In the meantime, if you're seeing a bX- code instead of your blog, and a custom domain is part of your life, you're welcome to report the code with details, and wait for a (silent) resolution. Or, you can try either or both of the workarounds - "Another blog ..." or possibly "404 Not Found". If you try either of the latter solutions, and you see any change, your comments here would be appreciated by a lot of bloggers and Bloggers.

>> Top

Details About bX- Code Circumstances Now Requested By Blogger Support

In an effort to reap benefits from the chronic bX- codes, Blogger Support now asks for the details, related to the circumstances. Just fill in the form, and enjoy the feeling that your pain is not being ignored.

This request for diagnostic details, plus the bX- Codes Glossary blog, should reduce the frustration level ever so slightly, when a bX- code is experienced. Maybe this effort is part of a increased focus on solving some of the ongoing problems, like the pervasive "Another blog ..." error, encountered periodically during custom domain setup.

In order for the form to be useful, we have to use it. As I've stated before, every report about a given problem, no matter how many times experienced, is significant. If you don't report your experience, it may not be resolved as quickly as it could be.

When you get a bX- code, take the time and add an entry to the form, with complete and precise detail about the problem. Like the False Positive Locked Blog, following procedure is the best choice, all around.

>> Top