Stuck in Turnstile loop from Hetzner servers — can’t access Cloudflare sites

[user4808]

What is the name of the domain?

ЛУН — Усі новобудови України, квартири в ЖК від забудовників

What is the issue you’re encountering

loop

What are the steps to reproduce the issue?

Hi everyone,

I’m having a really annoying issue when trying to access websites that use Cloudflare’s Turnstile challenge.
From any of my Hetzner Cloud servers, I get stuck in an endless Turnstile loop — the page just keeps refreshing and asking to verify again and again.

What’s happening:
• I can’t open sites like:
• https://lun.ua/
• https://edo-v2.edin.ua/
• Tried from several VMs in Hetzner — all the same.
• Tested in:
• Chrome, Firefox, Edge
• Incognito mode
• With/without extensions
• Clean browsers — same problem every time.

What’s weird:
• Turnstile works fine on the official demo page:

Turnstile ‐ Dummy Login Demo

• If I try from my home connection (not Hetzner) — no problem at all. The same sites open instantly.

My guess:

Cloudflare might be challenging or blocking Hetzner IP ranges too aggressively, even when the traffic is clean and legit.

Is there any way to fix or bypass this?
Happy to provide logs, IPs, whatever helps.

Thanks!

Screenshot of the error

[user4808]

Update: only firefox works!

[konstantin.shatalov]

Same problem here!

[surv]

I am also facing same issue from few days on hetzner server. Need administrator attention on it. My projects are stuck due to it. I have to use vpn to do my work.

[megan.simpkins1]

I was having the same issue in Texas and still here in Virginia. I did all the troubleshooting steps and several websites are doing this.

[dapkpmoer]

The same issue. Edge and Google Chrome get stuck on the same page and refresh infinitely, while Firefox works fine. I’m not sure if it’s a problem with the browser engine since Firefox doesn’t use the Google engine. All browsers are on the latest versions.

[user4808]

Still the problem is being observed. Is there any solution?

[rs19]

Just to confirm, we got the issue aswell - no chance to break the “human verification”-loop.