Cloudflare

My site didn't load from Syria, and curl said it was fine

In August 2026 my site timed out in the browser without a VPN, while curl from the same connection got HTTP 200. The setting behind it was Encrypted Client Hello (ECH) on the Cloudflare zone. I turned it off on 2026-08-20.

How I found out

By accident. I opened the link I’d sent my wife on WhatsApp, and it didn’t load. Then I opened it on the laptop with the VPN off, which I almost never do, and it didn’t load there either. Chrome said ERR_CONNECTION_TIMED_OUT.

My first guess was something in the build. It wasn’t.

I’d been sharing the site with friends for a while, and they liked it. Nobody told me it only opened through a VPN. And I’d been applying to a lot of companies here at the time.

What ECH does to the connection

With ECH on, Cloudflare publishes an ech= value in the site’s HTTPS DNS record. The browser then sends cloudflare-ech.com as the visible hostname and encrypts the real one. A filter that decides by reading the hostname has nothing to read.

The symptom fits a dropped handshake: the TCP connection opens, the TLS hello never gets an answer, and the browser waits until it gives up. A dropped packet has no error to report, which is why I saw a timeout and not a TLS error. My best explanation is that the Syrian gateway drops what it can’t read a hostname from. Nothing I have on file proves it.

Why curl was no help

The system OpenSSL 3.0 doesn’t do ECH. curl sent the real hostname in the clear, got through, and returned 200 at the same moment Chrome was timing out on the same host. A check that only uses curl says the site is fine.

The fix, and what I’m not sure of

ECH off for the zone, then a full browser restart and a DNS flush, because Chrome caches the ECH config and the HTTPS record has its own TTL. After that it loaded on the phone and the laptop without a VPN. pq_keyex went off in the same change, but that server setting doesn’t change what Chrome sends, so it can’t have been the fix.

It’s an old story now, and two things in my memory don’t sit with my notes from that day. I remember my 4G loading the site back then. I’m not sure anymore whether the failure was every Syrian connection or just my Wi-Fi, or whether turning ECH off is really what fixed it. What I do know: since ECH went off, it loads.

I keep a probe for it now, syria-reach.sh. It walks the stack in order: DNS, TCP on 443, a load forced onto each of the site’s IPs, then plain HTTP against HTTPS. The first section that fails is the answer. It has to run with the VPN off, or it proves nothing.