Troubleshoot Cloudflare Turnstile verification
Zenoti uses Cloudflare Turnstile to verify that a user is human. In most cases it verifies automatically; occasionally it shows a simple checkbox challenge. This article helps you resolve verification failures.
Disclaimer: Turnstile is a Cloudflare component. Network and browser remediation below may require your IT team; Zenoti is not responsible for the content of external sites.
Key terms
- Turnstile widget: the embedded Cloudflare component that verifies a user.
- api.js: the primary Turnstile JavaScript file that initializes the widget.
- challenges.cloudflare.com: the domain Turnstile uses for secondary challenge/flow requests.
- QUIC: a transport protocol used by modern browsers; relevant when you see
QUIC_NETWORK_IDLE_TIMEOUTerrors.
On this page
- What success looks like
- Failure A: the widget loads but shows an error
- Failure B: the widget does not load
What success looks like
- Automatic (most common): the widget shows "Verifying…" briefly, then "Success!". No action needed.
- Manual: if it cannot verify automatically, you see a Verify you are human checkbox. Click it; the widget then shows "Success!".
Before troubleshooting, make sure JavaScript is enabled, and be ready to test in an Incognito/Private window or have IT allowlist network destinations.
Note: Some issues are transient (brief Turnstile retries). Wait a few seconds for it to self-heal before refreshing.
Failure A: the widget loads but shows an error
The widget area renders but shows Error. It often self-resolves within a few seconds — do not refresh immediately. If it does not resolve and no checkbox appears:
| Likely cause | Why | Resolution |
|---|---|---|
| Browser extensions (most likely) | An extension lets the first script load but blocks secondary challenge requests | Sign in via an Incognito/Private window. If that works, disable all extensions in the normal window and retry. |
| Network/firewall block | The firewall allows api.js but blocks secondary challenge/flow traffic |
Have IT allowlist challenges.cloudflare.com for all protocols (TCP and UDP), then retry. |
| Corrupted browser cache | A broken cached script prevents initialization | Hard refresh (Ctrl+Shift+R). If it still fails, clear the cache and retry. |
Agent checklist: wait a few seconds for auto-recovery; test in Incognito; if Incognito works, disable extensions; if still failing, involve IT to allowlist challenges.cloudflare.com (TCP/UDP); as a last step, hard refresh then clear cache.
Failure B: the widget does not load
The widget area is blank or shows only reserved space.
Diagnose: press F12 to open Developer Tools, check the Console for errors such as net::ERR_QUIC_PROTOCOL_ERROR, net::ERR_CONNECTION_TIMED_OUT, net::ERR_CONNECTION_RESET, or net::ERR_NAME_NOT_RESOLVED, and check the Network tab for failed api.js requests.
| Likely cause | Why | Resolution |
|---|---|---|
| Corporate firewall / VPN block (most likely) | Network security tools block Turnstile subrequests (common with QUIC timeouts) | Have IT allowlist the entire challenges.cloudflare.com domain so all subrequests are permitted. |
| Browser extensions | Ad/script/privacy blockers prevent the widget from loading | Test in an Incognito/Private window. |
Note: If a corporate firewall or VPN blocks Cloudflare challenge traffic, only your IT team can permanently resolve it.