Enabling Cloudflare's orange cloud on a Minecraft domain feels like it should just work the way it does for a website — and it silently breaks the connection instead, because a game server and a website are not speaking the same kind of traffic at all.
What the proxy actually is
Cloudflare's standard proxy operates at the HTTP/HTTPS layer: it terminates web requests, applies its web application firewall and caching, and forwards them on. That is built specifically to understand HTTP — headers, methods, URLs. Minecraft does not speak HTTP at all; it opens a raw TCP connection (or UDP, for Bedrock) and exchanges its own binary protocol directly. When a Minecraft client tries to connect through a proxied record, the connection arrives at Cloudflare's edge, which has nothing to do with it — it is not a web request, and the proxy has no HTTP layer to hand it off to — so the connection simply fails or times out.
Setting it up so it actually connects
| Setting | Value |
|---|---|
| Proxy status on the game A record | DNS Only (grey cloud) — never proxied |
| Port | An SRV record lets players connect without typing the port, still pointing at the same grey-cloud A record |
| A separate web map or store page on the same domain | Can stay proxied normally — that traffic genuinely is HTTP |
The DNS record for the game subdomain shows grey/DNS-only in the Cloudflare dashboard, and a fresh client — one that has never cached the old failing lookup — connects normally.