Turnstile errors 600010 when devtools is open

Website, Application, Performance Turnstile
1

What is the name of the domain?

https://james-mosiers-ultra-awesome-project.webflow.io/vue

What is the error number?

600010

What is the error message?

[Cloudflare Turnstile] Error: 600010.

What is the issue you’re encountering

When Chrome devtools are open and the debugger is disabled, turnstile errors with 600010

What steps have you taken to resolve the issue?

Close devtools or enable the debugger to be hit and Turnstile passes verification.

What are the steps to reproduce the issue?

  1. Enable turnstile on a site
  2. Open Chrome devtools
  3. Disable breakpoints (otherwise Turnstile has a debugger; command that fires automatically)
  4. Reload the site
  5. Turnstile error 600010 occurs

If you close Devtools and reload the site, Turnstile passes.

1 Like
2

Hi @jamesdmosier,

Something in your devtools, such as a plugin or the emulator is triggering that error. Please refer to Error codes | Cloudflare Turnstile docs

4

@bujangnim So if you open up your browser devtools, go to this site in your browser (with no browser extensions/devtool plugins installed) you don’t see the debugger being hit?: title of augst8

This is being widely reported the the debugger line traces back to a script from Cloudflare Turnstile.

1 Like
5

@bujangnim it’s nothing to do with extensions, I have the same error with no extensions.

@jamesdmosier it’s something to do with Webflow’s configuration. Perhaps they haven’t set Cloudflare up correctly or haven’t renewed something. If you disable bot and spam filtering in your form settings you’ll get rid of the bug (it might only be one of those settings actually, try one at a time).

I’ve disabled both for now because I’ve overridden my Webflow form submissions, I’ll probably manually add my own version of Turnstile for bot filtering.

If I were you I’d message Webflow support because it might mean that your bot/spam filtering isn’t working. I’m going to do the same but just to alert them to the issue since I won’t use those features.

6

hello, in case you or others are still on this issue, I went crazy for hours.
This fixed it for me: go in webflow, form settings and turn off “bots are being blocked”.

image
image1354×430 35.4 KB

7

It is not a Webflow issue. Here is an example (built with just HTML and JavaScript) showing the same issue as I originally described: Turnstile Test

  1. Open Chrome (or any browser) devtools
  2. Go to Turnstile Test
  3. Disable breakpoints (otherwise Turnstile has a debugger; command that fires automatically)
  4. Reload the site
  5. Turnstile error 600010 occurs
8

Are you sure you’re using correct site_key and secret_key for your Turnstile Widget?

Is the particular hostname added to the Widget?

In the Console of the Developer Tools (F12) I can see the authroziation 401 error for the Turnstile:

slika

You’ve also got multiple cache systems here, at least by checking the HTTP headers.

May I ask if you’re verifying the returned token on the server-side?

9

Sorry, I might not be explaining myself the best. This Loom shows the issue I am describing (starting at the 0:58 second mark).

What I am really after is just validation that this is indeed expected behavior from Turnstile that a debugger statement being hit on the client side causes a 600010 error. So this is less about getting Turnstile working and more about understanding the internals that if you have your browser devtools open when loading the page then Turnstile fails.

10

Thank you for feedback and video.

May I ask if both hostnames:

  1. Custom domain, example.com and www.example.com
  2. Webflow sub-domain james-mosiers-ultra-awesome-project.webflow.io

Are added as hostnames to your Turnstile widget, since I guess you’d be using (if the setup allows to) CNAME? :thinking:

And does it happen on other webpages (HTML documents) as well or only on one and only?

11

This also happens on https://jamesdmosier.com/turnstile_test.html in which the hostname (jamesdmosier.com) is configured for the Turnstile widget in the Cloudflare settings (and is a completely different setup from the Webflow example). Here’s a Loom of that setup and the resulting issue.

I’ll validate what the setup is on the Webflow side…

12

I can confirm that disabling breakpoints on chrome dev tools causes this error. As mentioned, there seems to be a debugger that fires automatically, which is pretty annoying because it takes you to the Sources tab every time (this is probably an issue on chrome’s side).

13

I’m having this error as well. Have not been able to solve it by disabling breakpoints.