User talk:Rxls

I usually leave the heading for TL notes, just in case someone adds references later on. Toshiya (talk) 04:40, 23 May 2017 (CEST)

Toshiya if the original translator/editor doesn't make a reference/note there is no chance a simple reader will make one later on. It's pointless and jarring to have a blank part. The best choice is to follow the format that zzhk and Entropy use. If someone makes a note later on then you just remove the comment . Check Unlimited Fafnir for reference.

Shinrei Tantei Yakumo

Hello, thanks for pointing out the issue with the dead links. I replied on the admin contact page too, but As you said, if someone gets Laute's permission, the archived versions could be hosted here (I don't personally know anything about contact via tumblr). What I did in the meantime was remove the external links and bring back some local wiki pages for the project. . --Cthaeh (talk) 02:54, 31 July 2017 (CEST)

Hey, I saw you reversed the changes I made on Blade Dance’s novel illustration pages. I didn’t realize I needed to get approval, which I found out on the Discord. What is the process for that?

new perms

I've noticed you frequently deal with rollebacks and annoying edits, so would you like to move up your permissions to supervisor? It would also allow you to change the protection on pages, if needed. You can reply here or on discord. --RS (talkdiscord) 06:55, 27 August 2021 (CEST)

Hello RS. I wouldn't mind becoming a supervisor. Although I'll avoid making major changes like changing the protection on pages it will be nice being able to block users like Ie who abused the site by repeatedly making unwanted edits/remove content.

Ok, if you're also in the discord server let me know, so I'll give you one there. --RS (talkdiscord) 12:39, 27 August 2021 (CEST)

City Series

Have you tried pinging Mouton, who did those images in the first place? maybe he has some of the later volumes done. You could also try asking js06 what he prefers, since that project has no supervisor listed. --- description: Fix challenge loops, unsupported browser errors, and other solve failures. title: Challenge solve issues image: https://developers.cloudflare.com/cloudflare-challenges/troubleshooting/challenge-solve-issues/og.png?v=9a5beb1cbd8d6267 ---

[Skip to content](#main-content)

> Documentation Index > Fetch the complete documentation index at: https://developers.cloudflare.com/cloudflare-challenges/llms.txt > Use this file to discover all available pages before exploring further.

1. Challenge solve issues

Last updated Sep 8, 2026|Copy as Markdown| [View as Markdown](https://developers.cloudflare.com/cloudflare-challenges/troubleshooting/challenge-solve-issues/index.md)%7C [Agent setup](https://developers.cloudflare.com/agent-setup/)

Note

Challenge Pages are issued through the Cloudflare Challenge Platform, which uses the same underlying technology as Turnstile. The troubleshooting steps on this page apply to both Turnstile widgets and Challenge Pages failures.

1. 1. Challenge loops

You may encounter a challenge loop where the challenge keeps reappearing without being solved. This is in very specific cases where we detect strong bot signals. If you are a legitimate human, you can follow the troubleshooting guide below to resolve the issue or submit a feedback report. Challenge loops can happen for several reasons:

- **Network issues**: Poor or unstable network connections can prevent the challenge from being completed. - **Browser configuration**: Some browser settings or extensions may block the scripts needed to execute the challenge. - **Unsupported browsers**: Using a browser that is not supported by Turnstile. - **JavaScript disabled**: Turnstile relies on JavaScript to function properly. - **Detection errors**: If Turnstile suspects bot-like behavior, you may encounter repeated challenges for verification.

Most challenges are quick to complete and typically take only a few seconds. If it takes longer, ensure your network is stable and follow the [troubleshooting steps](#troubleshooting).

Note

If the issue persists, try switching to a different network or device to rule out any issues with your browser environment.

Ensure your browser is updated to the latest version to maintain compatibility.

1. 1. 401 response on a Private Access Token request

When a Challenge Page loads, the browser may request a [Private Access Token (PAT)](https://developers.cloudflare.com/cloudflare-challenges/reference/private-access-tokens/) from a `/cdn-cgi/challenge-platform/.../pat/...` endpoint. On devices, browsers, or networks that cannot issue a token, this request returns an HTTP `401`.

This response is **expected** and does not mean the visitor was blocked or that the widget failed. Cloudflare falls back to a standard challenge and the visitor proceeds as normal. A `401` on this request — for example, one seen in browser developer tools or a HAR capture — is not, on its own, a sign of a misconfiguration, a false positive, or a block. For more details, refer to [Private Access Tokens](https://developers.cloudflare.com/cloudflare-challenges/reference/private-access-tokens/).

1. 1. Failed subdomain network requests during Turnstile challenges

When looking at browser developer tools or capturing a HAR for Turnstile, it is not uncommon to notice certain requests to specific subdomains failing due to DNS host lookup errors. These subdomains live under the parent domain of `challenges.cloudflare.com` and `dnstest.dev`. The requests to them are part of Turnstile's normal execution. That said, these errors should not be perceived as failure root causes, as they are **non-blocking** to visitors.

Given that these DNS host lookup failures are **expected** and **non-fatal** for Turnstile's execution, avoid surfacing them as fatal execution errors, especially in the case of handler-based integrations of Turnstile such as WebView embeddings. For more fine-grained control, consider dropping network errors originating from requests to the `*.challenges.cloudflare.com` wildcard while preserving error visibility for the `challenges.cloudflare.com` apex.

1. 1. Troubleshooting

Follow the steps below to ensure that your environment is properly configured.

1. 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](https://developers.cloudflare.com/cloudflare-challenges/reference/supported-browsers/).
  - Run a test on the [compatibility checking tool ↗︎](https://debug.challenges.cloudflare.com/).

2. 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.

3. 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.

4. Try Incognito or Private mode.

  - Use your browser's incognito or private mode to rule out issues caused by extensions or cached data.

5. Test another browser or device.

  - Switch to a different browser or device to see if the issue is specific to your current setup.

6. Avoid VPNs or proxies.

  - Some virtual private networks (VPN) or proxies may interfere with Turnstile. Disable them temporarily to test.

7. 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.

1. 1. Collect diagnostic information

If the issue persists, collect the following information before contacting the website administrator or Cloudflare Support:

- A HAR file captured while reproducing the issue. For challenge loops, enable **Preserve log** in your browser's developer tools before reproducing the problem. You may also need to select **Disable cache**. - A browser console log export captured during the same session.

For step-by-step instructions, refer to [Gathering information for troubleshooting sites](https://developers.cloudflare.com/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/).

1. 1. WebView and mobile app implementations

If the challenge fails only inside a native app's WebView, review the required WebView settings in [Mobile implementation](https://developers.cloudflare.com/turnstile/get-started/mobile-implementation/). Common causes include disabled JavaScript, missing DOM storage or cookie support, blocked access to `challenges.cloudflare.com`, and a User Agent that changes during the session.

If none of the above resolves your issue, contact the website administrator with the [error code](https://developers.cloudflare.com/turnstile/troubleshooting/client-side-errors/error-codes/) and Ray ID or submit a [feedback report](https://developers.cloudflare.com/turnstile/troubleshooting/feedback-reports/) through the Turnstile widget by selecting **Submit Feedback**.

Was this helpful?

YesNo

1. 1. On this page

[Docs](https://developers.cloudflare.com/)

```json {"@context":"https://schema.org","@type":"TechArticle","@id":"https://developers.cloudflare.com/cloudflare-challenges/troubleshooting/challenge-solve-issues/#page","headline":"Challenge solve issues","description":"Fix challenge loops, unsupported browser errors, and other solve failures.","url":"https://developers.cloudflare.com/cloudflare-challenges/troubleshooting/challenge-solve-issues/","inLanguage":"en","image":"https://developers.cloudflare.com/cloudflare-challenges/troubleshooting/challenge-solve-issues/og.png?v=9a5beb1cbd8d6267","dateModified":"2026-09-08","publisher":{"@type":"Organization","name":"Cloudflare","description":"One platform for your apps, agents, and workforce. Build, secure, and scale without managing infrastructure","url":"https://www.cloudflare.com/","sameAs":["https://github.com/cloudflare","https://www.linkedin.com/company/cloudflare","https://x.com/cloudflare"],"logo":{"@type":"ImageObject","url":"https://developers.cloudflare.com/logo.svg"},"address":{"@type":"PostalAddress","streetAddress":"101 Townsend St","addressLocality":"San Francisco","addressRegion":"CA","postalCode":"94107","addressCountry":"US"},"contactPoint":[{"@type":"ContactPoint","contactType":"Customer Support","url":"https://support.cloudflare.com/","availableLanguage":["English"]},{"@type":"ContactPoint","contactType":"Sales","url":"https://www.cloudflare.com/contact/","availableLanguage":["English"]}]},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"},"keywords":["Debugging"]} ``` In any case, reverting (and not deleting) keeps the files available, so I'm fine with either choice. --RS (talkdiscord) 00:00, 5 December 2021 (CET)

InoBato & Untuned

Sorry for the late reply, I was out of the city for a few days. Do you have discord? it's way faster to use it if you need to get hold of someone.

Anyways, thanks for InoBato, totally didn't see the license. As for Untuned, it's not possible to host their translations on the wiki without the approval from the translator. But you can link to an external pdf/epub file if you want to go through the effort. --RS (talkdiscord) 18:16, 12 January 2022 (CET)