[IanNorris]

I can repro this in Chrome too when I have NextDNS as the DNS through our fiber connection. If I for example switch my phone to 4G it will let me through. I haven't dug into it yet as to why, there's nothing in the NextDNS block logs that looks relevant. But interestingly enabling NextDNS over 4G doesn't break it with the same settings.

I did take the rather unprecedented approach to blocking all DNS traffic to anything but our router (because Android was ignoring my DNS settings and using its own... ), breaking my internal dns resolution. Making DNS queries wonder from JS would be new to me... (I didn't think that was possible).

I'll dig more tonight.

[IanNorris]

So this is interesting. The website that's blocking me is www.internaltemperaturechart.com. I thought there was something wrong with the site until I saw this post.

I can get on gitlab.com and get to their sign in page (which does the Cloudflare check), but it lets me see the login page. I don't have a GitLab account so that's as far as I can go. My own website uses Cloudflare too, so I put the security to "I'm under attack", and tried it. That works too.

I tried in Firefox (with uBlock Origin) and Edge (without). Same results across all three.

From what I can tell, the site that fails only sends and receives to that domain, ruling out a tracking domain I've blocked. It sends out multiple "rays", with what looks like an encrypted payload (and no I'm not reversing the JS, it's heavily obfuscated). There is no response to any of them, the connection is terminated.

On GitLab, which works, one of the rays fails with a 401, but the rest succeed.

Hopefully someone that works at Cloudflare can figure this out for us...