Skip to content
EnterraHost
Products
Tools
Hosting Email Support Client Area Find a domain

When Turnstile refuses a MyBB visitor

A captcha that refuses everybody looks exactly like a captcha that works, from the outside. Both render a widget and both send a form. The difference shows up in what Cloudflare answers when the token is checked, and that answer is specific enough to name the cause.

Read the answer, not the page

Open Tools and Maintenance, then Statistics, then Turnstile diagnostics, and run the connection tests. The verification test sends a deliberately invalid token so the response is a message about your configuration rather than about a visitor.

AnswerCauseFix
invalid-input-responseWorking. The token was bad on purpose and was refused.Nothing.
invalid-input-secretThe secret key is wrong.Copy it again. A trailing space or a changed character is the usual cause.
No responseThe server cannot reach challenges.cloudflare.com.Check the outbound firewall and DNS from the server itself.
Widget never rendersThe browser cannot load api.js.A content security policy, an ad blocker or a network block. The diagnostics panel tests this separately from the keys.

The failure that is not the keys

A widget that never appears is a script problem rather than a key problem, and the two are worth telling apart before changing anything. If the keys were wrong the widget would still draw and the login would still fail after it. If the script is blocked, the page has no widget at all, and the visitor sees a login form with nothing in it.

The diagnostics panel tests reachability of api.js from the server, which is a different question from whether the visitor's browser can fetch it. A server that can reach Cloudflare and a visitor who cannot is a proxy, an extension or a policy on their side.

Finding which surface is failing

The statistics page counts impressions, successes and failures per endpoint, so a login problem does not look like a registration problem. A total tells you something is wrong. The per-endpoint table tells you where, which is the difference between an afternoon and an hour.

Failures are also written to the log with the endpoint and the reason, and the last ten are shown on the diagnostics panel. Nothing is written to the visitor's page as an exception, so a refused visitor sees the form rather than a stack trace.

Alerts, if you would rather be told

Turn alerts on and choose the usergroups that should hear about it. The threshold is failures within a window, with a cooldown afterwards, so a sustained burst sends one private message rather than one per failure. It is off by default because a message per event is noise.

Before you change a key

Copy the report from the diagnostics panel first. It contains no secret, it can be pasted into a support message, and it records what the answer was before somebody started fixing it.

Summarize this guide with

You need an account with the assistant you choose. It fetches the guide itself, and you send the prompt, not us.

Every guide in this category is on the Plugins page.

Something here wrong, or out of date? Tell us at editorial@enterrahost.com.