Skip to main content

Monkey Raptor V.2: Premium ‘Connection Closed’ Feature!

Hi. 👋

Let's start from this snapshot.

Connection closed
⬆️ Mm.

ERR_CONNECTION_CLOSED happened while transitioning.

But now we're looking at new layout!

The old blog customisation was rather untidy. And it would be quite arduous to refactor the thing.

I wanted to structuralise my customisation, so I thought — Hm. Let's see other themes here.


The Steps

  1. Export the XML from the old (reference) blog. It consists of all posts, comments, pages, etc. But without the customisation, only the content. Here on Blogger, we can do it by accessing:

    Settings ➡️ Manage Blog ➡️ Back up content

    Back up content
  2. Create a new blog from the upper left side of Blogger dashboard. Make a new blog
  3. Then, name the new blog and pick a good theme for it. If you want, you can always get the template from other than what Blogger provides. I picked the one which was already there. This layout is Notable theme, the Antique theme colour variant. Notable theme
  4. Import the XML data from the old blog to the new one.

    Settings ➡️ Manage Blog ➡️ Import content

    Import content
  5. Followed by skimming the thousands lines of HTML and CSS. Then I brought (inserted) the old blog features to the new layout. The JavaScript, meta tags, CSS, and so forth through:

    Theme ➡️ Customize ➡️ Edit HTML

    Edit HTML
  6. I then tested some of the posts, pages, and surely the features brought in to the new layout. All good.
  7. I use custom domain for this blog — from the old theme one, which would be switched to this new theme. So I needed to detach the custom domain (subdomain) from the old blog, and attached that to this. The problem was I did it before I bypassed my Cloudflare proxy.

Thus keep in mind, if we're transitioning our custom domain from old blog to new blog (in same Blogger ecosystem — or not), and we are using Cloudflare proxy, make sure to bypass the proxy through Cloudflare's DNS setting first before attaching the domain to the new blog and activating the HTTPS on Blogger.

Blogger needs direct DNS resolution for SSL verification, Cloudflare's proxy was likely blocking the verification challenge from going through if we forgot to bypass it before attaching the domain.

Failed SSL certificate auto generation

Because of that, I needed to redo the process.

Broken SSL

Downtime

Keep in mind, there will certainly be downtime during the auto-generated SSL certificates process. The operation needs around 5 minutes to 2 hours, give or take, depends on many factors. Mine was under one hour, in order of minutes as I recall. We need to check the notification on the Blogger dashboard to make sure the process goes correctly.


Right then. Cheers. 👋

Comments

Monkey Raptor uses cookies for analytics, advertisements, and functionality. More info on Privacy Policy