Skip to main content

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

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


Pete said…
Hey, Chuck. Maybe I can clear some things up.

A bX code happens when there's an unexpected error on the Blogger backend. It can be any number of things, but the general pattern is that a bX code comes from an error that's probably rare enough that we don't have code to handle it gracefully. Instead, Blogger barfs, shows the bX code (which is like a fingerprint of the error, so we can look it up), and that's it.

Of course, sometimes situations arise where these very rare errors become common (a bug on our end, or some service we're dependent upon is undergoing maintenance) and are seen by lots of people. It's these cases that we have the blog for, which lets us instantly show a relevant error message on the bX code page, and any workarounds that may exist.

"Clearing cache and cookies" will almost never actually "solve" a bX code problem. The exact same effect would be achieved by just waiting a minute or so and re-trying.

Clearing cache and cookies helps with other problems, though, such as strange browser behavior when logging in, or a page not appearing or behaving correctly.

If you're faced with a bX code, and waiting and retrying doesn't work, my next recommendation would be to try and get more information (does this happen on other blogs? did you recently change your blog's template or settings?) and then see if people are talking about the bX code on the Blogger Help Group. If no one is, start up a new thread.
Chuck said…
Thanks, Pete! That certainly does clarify a few points, and strengthen some others, and make my previous post more relevant.
diajeng any said…
Thanks a bunch, the article really helps
Meso said…
I didn't see any solution you posted. You just wasted my time!
Chuck said…
I didn't see any solution you posted. You just wasted my time!

If you keep asking for a "solution", you are wasting everybody's time! There is no solution, because the codes are not a problem!

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: