Cloudflare on Margrop Blog

You Bought an Overseas VPS and a Domain. Now What? 12 Things That Make a Public IP Worth Owning

Sat, 11 Jul 2026 13:30:00 +0800

The short answer

An overseas VPS by itself is a powered, connected room without a memorable street address. A top-level domain by itself is only a sign. Put the domain on Cloudflare DNS and point carefully chosen records at the VPS, and you finally own the sign, the map, the storefront, and a standards-based public entrance.

The result is much more useful than “a place to host a blog.” It is a small, always-on piece of Internet infrastructure where you control the code and the migration path: websites, APIs, webhooks, status pages, monitoring, controlled file sharing, password management, remote-access relays, automation jobs, and a personal AI gateway can all grow from the same foundation.

A public IP is also a door facing a busy street. Automated scanners may try the handle shortly after the server appears. This guide therefore covers both the useful projects and the services that should never be exposed directly.

After Buying a Domain, Use Cloudflare Tunnel to Turn Home Services into Public HTTPS

Thu, 21 May 2026 11:38:00 +0800

Short version

The previous two posts covered the cheap-domain part and the Cloudflare DNS part: buy a low-cost .xyz domain for personal lab use, then move the domain to Cloudflare for nameservers, DNS, DDNS, email routing, and basic automation. This post continues with the next practical step: use Cloudflare Tunnel to expose an internal web service as a public https:// hostname. The important point is that visitors use standard HTTPS on port 443, while your home router does not need to forward ports 80 or 443 and your origin IP does not need to be exposed.

This article follows these two posts:

“Ten Years for 80 Yuan: Why I Prefer 6-Digit .xyz Domains for Personal Sites”
Original link: https://mp.weixin.qq.com/s/tbefnWGFI0QBFlRVcYjVEw
“Do Not Waste That 80-Yuan Ten-Year Domain: Put It on Cloudflare First”
Original link: https://mp.weixin.qq.com/s/h0o-vtGB_zj1aptaumBztQ

Those posts already covered buying a cheap .xyz domain, moving nameservers to Cloudflare, creating DNS records, using DDNS, and setting up email-related records. This post assumes that your domain is already active on Cloudflare. We will focus on one thing: publishing an internal web service through Cloudflare Tunnel with a clean public HTTPS hostname.

All examples in this article use documentation placeholders such as example.xyz, nas.speedtest.example.xyz, 192.0.2.10, localhost, and <TUNNEL_TOKEN>. No real domain, account, token, zone ID, private network address, or personal information is included.

After Buying an 80-Yuan 10-Year Domain, Hand the Rest to Cloudflare

Wed, 13 May 2026 08:46:06 +0800

The short version

Buying a cheap domain is only the first step. The real value starts when you move authoritative DNS to Cloudflare: DNS records, dynamic DNS, business email verification, mail forwarding, certificate automation, and even Agent-assisted configuration through scoped API Tokens can all live behind one clean control plane. The previous article covered how to buy a low-cost .xyz domain for roughly 80 RMB for 10 years. This one continues from there: how to connect that domain to Cloudflare, the generous infrastructure provider many people jokingly call a public good of the Internet, and how to use it efficiently without leaking secrets.

All screenshots and examples in this article use safe placeholders such as example.xyz, 203.0.113.10, and 2001:db8::10. They do not contain real domains, real IP addresses, Cloudflare account identifiers, Zone IDs, API Tokens, or private network information. Replace the placeholders with your own values when you follow the steps.

Using Cloudflare to Build gh-proxy for GitHub Acceleration

Mon, 10 Jun 2024 15:26:32 +0800

In previous episodes, I’ve experimented with Qinglong Panel. However, when trying to pull GitHub repositories, you may encounter network issues leading to pull failures. Regular GitHub file downloads are also extremely slow. So I used the free Cloudflare to build gh-proxy for GitHub acceleration.

I. Prerequisites

You need to prepare a Cloudflare account and a domain name (optional) in advance. For free domains, you can refer to the previous article ‘免费申请注册eu.org二级域名’

Using Cloudflare Workers to Solve Docker Image Pull Issues

Mon, 10 Jun 2024 14:16:26 +0800

Due to certain reasons, Docker images cannot be pulled normally in China. The method I wrote last year for accelerating image pulls is also no longer functional. Where there’s a will, there’s a way (not really). So I’ve written a new tutorial to solve the Docker image pull issue using Cloudflare Workers.

This article uses Cloudflare Workers to solve the problem of being unable to pull images. I won’t go into too much detail about Cloudflare here, and Cloudflare Workers is also a free service. If you’re not familiar with it, you can check out previous articles like “cloudflare加快github下载”. If you don’t want to follow this guide, you can reply with “jsdc” in the background to get the public service address I’ve set up.