How to troubleshoot verification failures
If the verification widget will not appear, will not complete, or repeatedly fails on submit, work through the checks below in order. Almost every report we see is one of the first three.
The widget never appears
The widget loads a small script from challenges.cloudflare.com. If your network blocks that host the widget simply never renders, and the submit button stays disabled.
- Corporate or campus proxies sometimes block Cloudflare's challenge subdomain. Ask your IT team to add
challenges.cloudflare.comto the allow list for your browser. - Privacy or ad-blocker browser extensions sometimes match the script URL. Temporarily disable extensions for the sign-in page and reload.
The widget shows but never completes
Turnstile's interactive challenges rely on standard browser features.
- The widget requires the browser to be capable of running modern web content. If the page reports that script execution is blocked for this site, re-enable it for the sign-in domain and reload.
- Make sure your browser is up to date. Very old browser versions sometimes fail the underlying compatibility checks Turnstile uses.
"Verification failed, please try again"
This inline error appears when the server rejects the token we sent it. The widget remounts automatically and you can try again immediately.
- The most common cause is a token that has already been used. This happens any time a previous submit failed (wrong password, expired reset link, etc.). The remounted widget will give you a fresh token — just complete it and resubmit.
- The second most common cause is a token that expired between rendering and submission. Tokens live for about five minutes; if the page sat open longer than that, the remount has handed you a fresh one.
Repeated failures despite legitimate use
If you've worked through everything above and the widget still rejects you, the request is being flagged at the network layer. Cloudflare scores each request based on IP reputation, request patterns, and similar signals. Shared corporate IP addresses with a poor reputation are a typical cause.
- Try from a different network (for example, a phone hotspot) to confirm whether the network is the problem.
- Contact an administrator. They can reach out through normal support channels with details of the issue and the approximate time it occurred so the platform team can investigate.