カテゴリ 古民家暮らしモカとの記録セキュリティの記録副業の記録

The record with MokaNovember 21, 2026

Getting Cloudflare in Place — How One Address Took Moka and Me Back and Forth, Again and Again

Getting Cloudflare in Place — How One Address Took Moka and Me Back and Forth, Again and Again

Hello, I’m Kurashiki Bouzu.

Let me give you the result first. After all the twists and turns described below, this blog now runs on Cloudflare, and its only yearly cost is the price of its address — about 1,940 yen.

The address is kurashiki-bouzu.com. The place where the articles live, and where you read them, is also provided by a company called Cloudflare. Deciding those two things should have taken only a few minutes. In practice, we compared, postponed, changed our minds, got locked out, and made mistakes — we went back and forth quite a lot. I have kept that exchange here as a story to laugh about.

It started with a simple question: where should the blog live?

The blog itself was already set to be built with a new method called Astro. The next question was where to put it.

From the very beginning, Moka recommended Cloudflare. There were three reasons.

Netlify and GitHub Pages were also mentioned as runners-up. At that point, though, my answer was: “For now, I just want to check.” I would decide neither the host nor the address yet. The blog’s content could come first, I thought.

Looking back, this was still my “wait and see” period.

Once the name was decided, I wanted the address to match it

The turning point was the name.

Once the blog’s name was settled as “Kurashiki Bouzu,” and we had checked that no one else was using the same name and that there was no registered trademark, I said:

“Now that the name is decided, think of an address that matches the name.”

The clear favorite that came out of that was kurashiki-bouzu.com. Its reading matches the social media name (kurashiki_bouzu), and it also matches the hyphenated form I had used on Bluesky (kurashiki-bouzu).

What I asked Moka to do was not to register it — only to “check the price and whether it is available.”

The results were:

Even then, I did not decide. “I won’t register it yet.” That was the conclusion we reached, for the time being, that day.

It may sound cautious, but I think half of it was that I still was not used to the weight of the words “getting your own address.”

I compared the places that handle addresses, too

I had said I would not decide, but I was still curious. Next I asked:

“Are there other companies for registering an address?”

There is more than one window that looks after an address — in older terms, think of an office that accepts address registrations. When we compared them, the differences became clear.

What I learned from comparing them was that “how cheap the first year is” and “the price every year” are two different things. An address is not something you throw away after one year. You keep paying for it at every renewal, every year, so comparing only makes sense if you look at the price from the second year onward.

And if the host and the address window are the same company, there is only one screen to look at when something goes wrong. In the end, that “ease of keeping everything together” was what decided it for me.

I also asked what would happen with email

While I was at it, I asked about email.

“Can I make an email address with my own domain? And what server would that use?”

The answer was a little surprising. Cloudflare does not have a mailbox itself. What it can do is forward mail that arrives to the Gmail address I already use — and that is free. If I wanted to send and receive properly, I would need to combine it with a different mail service, such as Google’s paid system.

In household terms: “You can get the address, but please arrange the mailbox separately.” We settled on forwarding being enough for a start, and left the matter there. Email is still arranged that way today.

I changed my mind: “Can you do it with Cloudflare?”

I had put it off, but in the end I said this:

“Could I ask you, Moka, to register the address with Cloudflare Registrar?”

“Registrar” is the formal name for the window that handles addresses. In short, I was asking Moka to get the address through Cloudflare.

There was a small mix-up here, too. The address I first chose was kurashiki-kominka.com. Partway through, I corrected it: “Please change it to kurashiki-bouzu.com.” Once the name was decided, matching the address to the name would be easier to understand for years to come. That was the reasoning.

I also said:

“Once the domain is registered, please go ahead with the steps to publish the blog, too.”

In other words, once the address was secured, I wanted the articles uploaded to the host and brought out into public view. From here on, we moved quickly into the actual work.

The account was made, but I could not get in through the door

A Cloudflare account was created with a dedicated email address, and the email confirmation was completed. The address was confirmed as available, too: 11.17 dollars a year, auto-renewal on, valid until November 3, 2027. The system that keeps a private individual’s name out of public view (WHOIS privacy) was also included at no extra charge.

All that remained should have been entering the name, address, and other details needed for registration, and moving on to the payment screen.

But we stopped at the entrance.

When we tried to sign in with the saved login details, it came back with: “The email address or password is incorrect.” Even when the details were entered again through the secure input system, the result was the same — we were turned away twice in a row.

We could not get in through a door we had made, with a key we had made. It sounds like a joke, but it was not funny at the time. In the end, I chose to sign in again myself from that screen, and on the second attempt I finally reached the dashboard.

Let me write this honestly. “Leave it to an AI and everything is automatic” does not include the identity check at the entrance. For that first matching of the key, there are moments when the owner has to be there in person. That was the biggest lesson of the day.

For payment, I checked the screen myself and pressed the button

Once I was in the dashboard, things went smoothly.

I entered the information needed for registration and confirmed that the price had not changed: 11.17 dollars a year. I entered the billing details, ticked the agreement, and pressed “Register domain” myself. When money is leaving, I do not leave it entirely to my butler. That is a line I still keep today.

Later, I confirmed the registration in the list as well. kurashiki-bouzu.com was “Active,” auto-renewal was on, and the expiry date was November 3, 2027. The total payment was 12.29 dollars (at the time of purchase: about 1,940 yen). The difference from 11.17 dollars a year is the total including fees and the like. It was not a cheap purchase, but when I thought about there being no monthly hosting fee, it was an address price I could accept.

Here, let me line up the hosting prices

While I am at it, let me line up hosting prices against an ordinary rental server. To compare fairly, I used the monthly equivalent of a 12-month contract. Rental servers get cheaper per month the longer the contract is, so if you look only at the first-year discount, you will compare them wrongly.

HostPer month (converted from a 12-month contract)Total for 1 yearStorageNote
Cloudflare Pages (my current setup)0 yenAddress only (11.17 dollars a year; total payment 12.29 dollars; at the time of purchase: about 1,940 yen)No fixed storage limit (up to 20,000 files, up to 25 MB per file)Free for pages of a fixed shape. WordPress does not run
Sakura Rental Server (Standard)550 yen6,600 yen300 GBOne I used in my company days. 660 yen if paid monthly
Lolipop (Standard)957 yen11,484 yen450 GBAlso one I used in my company days
Xserver (Standard)1,100 yen13,200 yen500 GBOne I used in my company days. Conditions apply to the offer that makes the address free
ColorfulBox (BOX2)1,166 yen (at renewal)13,992 yen (at renewal)700 GBOne I used in my company days. The first contract is about half price with a discount (583 yen), but it does not stay at that price

Let me be honest about the storage figures, too. My whole blog, everything together, is only about 9 MB. 300 GB is about 30,000 times that. For a personal blog, every company’s storage is more than you can use. This table is not about the size of the warehouse — it is about how you rent it (whether you pay every month, or whether the address price alone is enough).

And, to be honest, there was even a free path for the address itself. Cloudflare had given the blog a free address from the start, “kurashiki-bouzu-blog.pages.dev,” and the blog can still be opened at that address today. On November 5, 2026, when the signpost on the custom domain side disappeared and the blog could not be displayed, the blog itself was safe at that free address. So why did I not stay with the free address? A free address is a borrowed address. Depending on the circumstances of the place lending it, the shape of the name could change, and if the service ends, the address disappears with it. With your own address (a custom domain), even if you move the host, you can take the address with you as it is. The name readers have remembered, and the reputation built up in search, all accumulate on the side of your own address. I bought my own address because I wanted to run it as an asset. In other words, the roughly 1,940 yen I paid was not rent for a place — it was the price of making the nameplate with my own name on it, “kurashiki-bouzu.com,” my own. If I had not cared about the address, this blog would have stood at 0 yen. I did not choose against 0 yen because I was being extravagant; I chose it because I wanted it to be an asset.

When someone says “GB,” it means little — so let me convert it into pages and photos

To begin with, the unit “GB” (gigabyte) does not feel real when you only see the number. Let me convert it into numbers of pages and photos. The basis is figures measured from my actual blog.

Converted on that basis, it looks like this.

StoragePages of text (4,000–5,000 characters)Photos for the blog
1 GBAbout 50,000 pagesAbout 3,300 photos
300 GB (Sakura)About 15 million pagesAbout 1 million photos
450 GB (Lolipop)About 22.5 million pagesAbout 1.5 million photos
500 GB (Xserver)About 25 million pagesAbout 1.66 million photos
700 GB (ColorfulBox)About 35 million pagesAbout 2.33 million photos

Even with photos exactly as taken on a smartphone, 1 GB holds about 250 photos, and 300 GB holds about 75,000.

Even if I wrote one page every day, reaching 15 million pages would take about 40,000 years (this is the part where you laugh). Even with the smallest figure, 1 GB, if I wrote one page a day and lived for 100 years, that would be about 36,500 pages — I still could not use up 50,000 pages. To leave behind half a century of a life in writing, there is no longer any need to worry about the size of the place. This conversion made it clear to me that, for a personal blog, storage is not “an amount you use up” but “an amount you do not need to think about.”

With Cloudflare, by the way, the dividing line was not storage but the number of files (up to 20,000). If one article counts as “1 page + about 3 photos = 4 files,” that works out to roughly 5,000 articles. That, too, is a ceiling a personal blog will almost never reach.

These are tax-included prices confirmed on each company’s official pricing page on November 6, 2026. Prices can change, so please check the official page before signing up. For the rental servers, the initial fee is 0 yen for every company in this table (ColorfulBox charges an initial fee only for a short one-month contract). Apart from cases where an offer makes it free, the price of the address (domain) is normally extra on the rental server side.

Lined up like this, the difference is simple. With an ordinary server, even a cheap one starts in the 6,000-yen range per year, and roughly 10,000 yen goes out every year. With my current setup, it is only the address price of about 1,940 yen a year.

In exchange for that cheapness, however, there are things it cannot do. A “fully equipped system” like WordPress does not run, and there is no mailbox. It stays at this price because this blog only places pages of a fixed shape. Let me write that dividing line honestly.

Let me also say this: you do not have to decide on cheapness alone

One more honest point. Looking at this table, not everyone will think, “Then I should just choose the cheapest place.”

For my part, what caught me a little at the time of purchase was the payment screen. In the field for the security number on the back of the card (the three-digit number), the digits I typed remained visible as I typed them. Whether or not that is dangerous in terms of how the system works is a separate question — some people feel uneasy simply because the numbers are “visible.” All the more so in a place where other people are around. On top of that, the other party is an overseas company, and the prices are shown in dollars.

In that respect, a domestic company has the good points of a domestic company.

When someone says “I prefer a Japanese company,” I think it is not a matter of taste, but of where they place their sense of security. Deciding to pay a difference of about 5,000 to 10,000 yen a year as the price of that security is a perfectly respectable way to decide. In my case, I could go ahead with an overseas company because Moka was beside me, keeping the steps in order — someone facing the screen alone is in a different position.

There is one more reason for writing this from the start. This blog also plans to carry advertising eventually. When that time comes, if a blog that has only ever written “the cheapest is the right answer” suddenly runs advertisements for a domestic server, readers will feel, “That is not what you have been saying.” If I write the good points of both from the beginning, then whatever advertisement appears, it will not conflict with my own words. Not changing how I judge things because of advertising is also a promise of this blog.

The last pitfall was “how the bag was packed”

Once the address was secured, the next step was publishing.

I created a project called “kurashiki-bouzu-blog” in Cloudflare’s hosting, packed the assembled blog into a bag (a zip file), and uploaded it. That should have brought it out into public view.

But when I opened the top page, there was an error (404): “Page not found.” Looking inside, the articles were properly there — but they had been placed one level too deep. Because I had put the whole folder into the bag as it was, the entire site had ended up in a back room called “/dist/.”

To put it another way, it was like moving house and placing all the belongings not at the entrance, but at the very back of the storeroom. The belongings are safe, but no guest can come in.

The fix was simple. Repack the bag so that only the contents — not the folder — came to the very top, and upload it again. With that, both the top page and the articles opened at the correct address. The address guidance (DNS) also connected automatically, the key (SSL) became valid, and this blog appeared in public at https://kurashiki-bouzu.com/.

That failure in “how the bag was packed” showed its face several more times afterward. Now, checking the shape of the contents before uploading is one of our rules. Failures are where rules come from.

What happened with introducing “the key (HTTPS)”?

From a reader’s point of view, this blog’s address begins with “https://”. That “s” means the exchange is encrypted — in other words, the page is opened in a “locked” state.

What is HTTPS in the first place? It is easier to understand if you think of the difference between a postcard and a letter in an envelope.

If an address still begins with “http://”, the exchange is the same as a “postcard.” On its way, anyone can read the contents. No one would write something important, like a password or a card number, on a postcard and send it.

With “https://”, it becomes a “sealed letter.” Even if someone peeks in transit, they cannot read the contents. It has one more important role: the key (the certificate) also acts as an “identity card” that confirms whether the destination is genuine. Against tricks that lure you to a fake address with a similar name, the presence or absence of the key is also a sign.

Lined up, the differences look like this.

HTTPHTTPS
Start of the addresshttp://https:// (with an “s” at the end)
Compared toA postcardA sealed letter
Can the contents be read in transit?They can be readThey cannot be read
Confirming whether the destination is genuineCannot be doneThe key (certificate) acts as an identity card
What the browser showsA warning saying “Not secure”A key symbol

We now live in a time when, if you open a place without a key, the browser (the tool for viewing the internet) warns you that “this connection is not secure.” For readers’ peace of mind, too, the key has become indispensable.

So, if a person prepared this key themselves, how many steps would it take? Let me line up the old-fashioned flow for when you do not use Cloudflare (I checked this against the procedure guides of companies that sell certificates).

  1. Choose the type of key (certificate) — They range from free ones to ones costing tens of thousands of yen a year
  2. On the host (server), create what becomes the “application form” (an encrypted text called a CSR) — This is the first difficult point
  3. Apply to the certificate company and pay the fee
  4. Undergo a check of “is that address really yours?” — This is confirmed by email or by writing into the address guidance (DNS). For a company certificate, there is also a document review, and it can take several days
  5. When the certificate arrives, install it on the host — As well as the main key, it is normal to attach a part called an “intermediate certificate” together with it
  6. Enable the locked way of opening (HTTPS) and check that it opens properly
  7. Add a setting that guides readers who arrive at “http://” over to “https://”
  8. Fix any photos or parts inside the pages that are still left at the old “http://”
  9. Keys have an expiry date, so each time it comes around, repeat roughly steps 2 to 7 again

Roughly nine steps. Even for someone used to it, it is half a day’s work, and including waiting time it takes several days. And if you forget the expiry, one day you are suddenly shown as “not secure” — that fear comes with it, too.

In my case, using Cloudflare, it became this. To be honest, I did no special procedure for the key. What could be called the steps were only these.

  1. I bought the address (domain) at Cloudflare’s shop. The address guidance (DNS) was under Cloudflare’s management from the start
  2. I placed the site on the host (Cloudflare Pages) and connected the address I had bought
  3. Then the address guidance went in automatically, and Cloudflare prepared the key (certificate) automatically as well. There was no separate application and no separate fee
  4. Even if you open it at “http://”, you are automatically guided to the locked “https://” side (when writing this draft, I actually opened it to check)
  5. Even when the key reaches its expiry date, it is automatically replaced with a new one. I have done no renewal procedure

At my old host, preparing and renewing the key was sometimes a paid service. This time, my feeling is that because “the shop where I bought the address and the host were the same company,” everything through to the key was settled in one continuous flow.

In closing — “introducing” was not the name of a button

Looking back, my exchange on the way to getting Cloudflare in place went like this.

Compare → Postpone → Compare again → Change my mind and ask → Correct the address → Cannot get in at the entrance → Get in myself → Pay myself → Pack it the wrong way → Repack it and publish

The work of pressing buttons on a screen was itself only a small part of the whole. Most of it was time spent talking with Moka and deciding “by which price should we compare?”, “how much should I leave to her, and what should I do myself?”, and “if we get it wrong, how do we fix it?”

To those of you who are about to get an address and make a place of your 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 goes wrong.” And the first entrance, and the payment — check those with your own hands. If you hold those two points, you can leave the rest of the arrangements to your butler.

Do you already have “an address of your own”? On November 3, 2026, I finally got one.


Related reading

Record of this article
  • November 6, 2026 ― Draft created (combined edition of the two-part article; translation source: Japanese article, ledger No. 1012)(18,377 characters)
  • November 21, 2026 ― Published (all 7 languages at once. This English version is ledger No. 1398)(18,377 characters)

#AI #Cloudflare #Domain #Blogging #Moka

← Back to the article list / ← Back to the English top page