[GH-ISSUE #1158] Cloudflare Turnstile errors on with the code 600010 #5134

Closed
opened 2026-04-16 00:33:18 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @silasadair2000 on GitHub (Mar 13, 2025).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/1158

bug description

Waiting for the Cloudflare Turnstile to check if I'm not a robot goes on forever. Checking the console says "Request for the Private Access Token challenge" with "error code from turnstile: 600010" after that.

reproduction steps

  1. Go on cobalt
  2. Wait for Cloudflare Turnstile
  3. Check console after waiting too long
  4. See the console messages Request for the Private Access Token challenge with error code from turnstile: 600010 after that.

screenshots

Image

links

none

platform information

Ungoogled Chromium 133.0.6943.141 on Windows 10 Version 22H2

additional context

Firefox goes through the Cloudflare Turnstile normally.

Originally created by @silasadair2000 on GitHub (Mar 13, 2025). Original GitHub issue: https://github.com/imputnet/cobalt/issues/1158 ### bug description Waiting for the Cloudflare Turnstile to check if I'm not a robot goes on forever. Checking the console says "Request for the Private Access Token challenge" with "error code from turnstile: 600010" after that. ### reproduction steps 1. Go on cobalt 2. Wait for Cloudflare Turnstile 3. Check console after waiting too long 4. See the console messages `Request for the Private Access Token challenge` with `error code from turnstile: 600010` after that. ### screenshots ![Image](https://github.com/user-attachments/assets/753e3a17-d983-4d65-80d1-0dc36583b961) ### links ```shell none ``` ### platform information Ungoogled Chromium 133.0.6943.141 on Windows 10 Version 22H2 ### additional context Firefox goes through the Cloudflare Turnstile normally.
GiteaMirror added the bug label 2026-04-16 00:33:18 -05:00
Author
Owner

@dumbmoron commented on GitHub (Mar 13, 2025):

this is a problem with ungoogled chromium (caused in part by me, sorry). if you update to the latest version (134.x.x) it should resolve itself

<!-- gh-comment-id:2722486910 --> @dumbmoron commented on GitHub (Mar 13, 2025): this is a problem with ungoogled chromium (caused in part by me, sorry). if you update to the latest version (134.x.x) it should resolve itself
Author
Owner

@silasadair2000 commented on GitHub (Mar 13, 2025):

Updated and works like a charm. Thanks.

<!-- gh-comment-id:2722504344 --> @silasadair2000 commented on GitHub (Mar 13, 2025): Updated and works like a charm. Thanks.
Sign in to join this conversation.