| Error Code | Description | Retry | Troubleshooting |
|---|---|---|---|
110100 |
Invalid sitekey | No | Verify the sitekey in Cloudflare dashboard ↗. |
110110 |
Sitekey not found | No | Check sitekey spelling and dashboard configuration. |
110200 |
Domain not authorized | No | Add current domain in Hostname Management. |
110600 |
Challenge timed out | Yes | The visitor's clock may be wrong, or the challenge took too long. |
110620 |
Interaction timed out | Yes | The visitor did not interact with the widget in time. Reset with turnstile.reset(). |
200100 |
Clock or cache problem | No | The visitor's clock is wrong or the challenge was cached by an intermediary. |
200500 |
Iframe load error | Yes | The Turnstile iframe could not load. Check if challenges.cloudflare.com is blocked. |
300* |
Generic challenge failure | Yes | Bot behavior detected. Refer to troubleshooting. |
400020 |
Invalid sitekey | No | Verify the sitekey in Cloudflare dashboard ↗. |
400070 |
Sitekey disabled | No | The sitekey is disabled. Check the Cloudflare dashboard ↗. |
600* |
Generic challenge failure | Yes | Bot behavior detected. Refer to troubleshooting. |
You can troubleshoot these error codes using the following recommendations:
- Verify your browser compatibility.
- Turnstile supports all major browsers, except Internet Explorer.
- Ensure your browser is up to date. For more information, refer to our Supported browsers.
- Run a test on the compatibility checking tool ↗.
- Disable your browser extensions.
- Some browser extensions, such as ad blockers, may block the scripts Turnstile needs to operate.
- Temporarily disable all extensions and reload the page.
- Enable JavaScript.
- Turnstile requires JavaScript to run. Ensure it is enabled in your browser settings. Refer to your browser's documentation for instructions on enabling JavaScript.
- Try Incognito or Private mode.
- Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.
- Test another browser or device.
- Switch to a different browser or device to see if the issue is specific to your current setup.
- Avoid VPNs or proxies.
- Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.
- Switch to a different network.
- Your current network may have restrictions causing Turnstile challenges to fail. Try switching to another network, such as a mobile hotspot.
:::caution[Error code 401]
Turnstile may occasionally generate a 401 Unauthorized error in your browser console during a security check. This is not typically a problem with your implementation. This error often occurs when the widget attempts to request a Private Access Token that your device or browser does not support yet.
You can generally safely ignore the 401 error, as it is an expected part of Turnstile's underlying Challenge Platform workflow. If the widget is successfully resolving and you are receiving a token, no action is required.