Until I Brought in Cloudflare, Part 2 — The 404 from Packing the Bag Wrong, and the Key (HTTPS)
The result first: the blog stands at https://kurashiki-bouzu.com/ with the key on. I did no special procedure for that key. Because the shop where I bought the address and the place where the blog sits are the same company, the key came in one unbroken flow.
I am Kurashiki Bouzu (kurashiki-bouzu). In Part 1, I wrote about comparing places and buying the address kurashiki-bouzu.com. Part 2 is its continuation: the work of bringing the blog out in public at that address, and the story of the “key (HTTPS).”
The last pitfall was “how the bag was packed”
Once the address was taken, the next thing was publishing.
In Cloudflare’s place, I made a project called “kurashiki-bouzu-blog,” packed the assembled blog into a bag (a zip file), and put it up. With that, it should have come out in public.
But when I opened the top page, an error (404) said, “There is no page.” Looking inside, the articles were properly in there, but the place they sat was one level too deep. Because I had put the whole folder into the bag as it was, the whole site had been placed in a back room called “/dist/.”
To put it in an image: it is like placing all the moving luggage not at the entrance, but at the very back of the storeroom. The luggage is safe, but visitors cannot enter.
The way to fix it was simple. Repack the bag’s contents so that the contents themselves, not the folder, come to the very top, and put it up once more. With that, both the top page and the articles opened at the correct address. The guidance for the address (DNS) also connected automatically, the key (SSL) became valid, and at https://kurashiki-bouzu.com/ this blog came out in public.
That failure of “how the bag was packed” showed its face several times afterwards, too. Now, checking the shape of the contents before putting them up has become our rule. A failure is the origin of a rule.
What became of bringing in the “key (HTTPS)”
For the reader, this blog’s address begins with “https://”. When that “s” is attached, the exchange is encrypted — that is, it opens in a “locked state.”
What is “HTTPS” in the first place? It is easy to understand if you think of the difference between a postcard and a sealed letter.
If the beginning of the address stays “http://”, the exchange is the same as a “postcard.” On the way of delivery, anyone can read the contents. No one writes an important thing like a password or a card number on a postcard and sends it.
When it becomes “https://”, it becomes a “sealed letter.” Even if someone peeks on the way, the contents cannot be read. There is one more important role: this key (certificate) also carries the role of an “identity card” that confirms whether the destination is genuine. Against the trick of leading people to a false address with a similar name, the presence of the key is also a sign.
Lined up, the difference is this.
| HTTP | HTTPS | |
|---|---|---|
| Beginning of the address | http:// | https:// (an “s” at the end) |
| To compare it | A postcard | A sealed letter |
| Can the contents be read on the way? | They can be read | They cannot be read |
| Confirming the destination is genuine | Cannot be done | The key (certificate) becomes the identity card |
| Display in the browser | A warning, “Not protected communication,” appears | The mark of a key appears |
Now is an age when, if you open a place without a key, the browser (the tool for seeing the internet) warns, “This is not protected communication.” For the reader’s peace of mind, too, the key has become indispensable.
Now, if a person prepared this key by themselves, how many steps would it take? Let me line up the old-fashioned flow for when Cloudflare is not used (I checked it in the procedure book of a company that sells certificates).
- Choose the kind of key (certificate) — From free ones to ones costing tens of thousands of yen a year
- At the place (server), make what becomes the “application form” (an encrypted text called a CSR) — This is the first difficult place
- Apply to the certificate company and pay the fee
- Receive the confirmation “Is that address really yours?” — Confirmed by email, or by writing into the address guidance (DNS). For a company certificate there is also an examination of documents, and it can take several days
- When the certificate arrives, attach it to the place — Normally, besides the main key, a part called an “intermediate certificate” is attached together
- Enable the locked way of opening (HTTPS) and check that it opens properly
- Put in a setting to guide readers who came by “http://” to “https://”
- Correct any photos or parts inside the pages that remain in the old “http://”
- The key has an expiry date, so each time the date comes, repeat roughly steps 2 to 7 once more
Roughly 9 steps. Even for someone used to it, half a day’s work, and including waiting time, a matter of several days. And if you forget the expiry, one day it suddenly displays “Not protected” — that fear comes with it.
In my case, using Cloudflare, it became this. To write honestly, I did no special procedure about the key. What could be called the procedure was only the following.
- I bought the address (domain) at Cloudflare’s shop. The guidance for the address (DNS) was under Cloudflare’s management from the start
- I placed the site in the place (Cloudflare Pages) and connected the address I had bought
- Then the guidance for the address went in automatically, and the key (certificate), too, Cloudflare prepared automatically for me. There was no application and no fee, separately
- Even if you open it by “http://”, you are guided automatically to the locked “https://” side (when writing this manuscript, I actually opened it and checked)
- Even when the key’s expiry comes, it is replaced with a new one automatically. I have done no renewal procedure
At the old place, preparing and renewing the key was sometimes paid. This time, thanks to “the shop where I bought the address and the place being the same company,” it was settled with the key in one flow. That is my real feeling.
In closing — bringing it in was not the name of a button
Looking back, the exchanges until I brought in Cloudflare were these.
Compare → Hold off → Compare again → Change my mind and ask → Correct the address → Cannot enter at the entrance → Enter myself → Pay myself → Pack it wrong → Repack it and publish
The work of pressing buttons on the screen itself was only a small part of the whole. Most of it was time spent talking with Moka and deciding “By which price do we compare?”, “How far do we leave it, and where do I do it myself?”, and “If we get it wrong, how do we fix it?”
To those who are about to take an address and make a place of their own: if you are lost over the name of a tool, what to look at is not “the cheapness at the start,” but “the price every year” and “how easy it is to fix when something happens.” And only the first entrance and the payment, check with your own hand. If you hold those 2, the rest of the arrangement can be left to the butler.
Do you already have your own “own address”? On November 3, 2026, I finally had one.
Read together
- Why I graduated from WordPress: Why I graduated from WordPress and built this blog with Astro and an AI butler
- The move that followed: Turning the trouble of publishing into the flow of a river — moving from handing over zip files to the GitHub repository
- Part 1: Until I Bought My Own Address, Part 1 — Going Back and Forth with Moka Many Times over a Single Domain
- Episode 0: In my 50s, living in an old folk house — until I welcomed the AI butler ‘Muse’
- November 18, 2026 ― English draft created (results-first rewrite of the Japanese article, ledger No. 35). Not published; publication is a separate step.(6,169 characters)
