TROUBLESHOOTING

Troubleshoot CAPTCHA verification

Check Logical Forms Turnstile credentials, allowed hostnames, challenge placement and blocked scripts when CAPTCHA verification fails.

2 min read · Updated November 19, 2026

Logical Forms uses Cloudflare Turnstile. The widget's appearance and successful server verification are separate checks. Start with the exact error and whether the widget loads, becomes ready, expires or fails only after Submit.

Verify site configuration

  1. Open Logical Forms → Settings → Captcha. Confirm the intended provider, Site key and saved Secret key.
  2. Check that both credentials belong to the intended Turnstile widget and its allowed hostname includes the site's current domain. A staging or mapped domain may differ from the original site.
  3. Save and use the configuration test. Do not expose the Secret key in screenshots or browser code.
  4. Open a fresh saved public form and complete a controlled test. A connection or widget test alone does not prove final submission verification.

Official test credentials are accepted only when WordPress identifies the environment as local or development. Staging or production environment labels do not enable that exception. Use real credentials for the actual public host.

Check form placement

Use one CAPTCHA field on the final page. The field, final page and containing Section must be unconditional. A branch that can skip the challenge is not a valid configuration. CAPTCHA cannot be inside a Repeater.

The widget does not load or complete

Inspect the browser console and network failures for blocked Turnstile scripts, content-policy restrictions or network errors. Compare a fresh private window and the actual embedded page with saved Preview. Browser extensions and script optimization can affect the widget; reproduce a suspected conflict on staging.

The server must also reach the verification service. A host HTTP restriction or timeout can prevent verification even when the browser widget looks complete. Ask the host to inspect the failed outbound verification request without logging the secret or response token.

Expired or invalid attempts

Complete the refreshed widget and retry within a fresh page attempt. Do not copy verification tokens between forms, domains or attempts. The plugin checks the provider result, hostname and form action; changing only the visible checkmark does not satisfy those checks.

Repeated verification failures can exhaust the attempt's bounded verification allowance. Reload a fresh form and investigate the underlying cause instead of bypassing verification or continually resubmitting an old token.

Evidence for support

Record the page URL, form ID, current hostname, timestamp, environment type, visible error and whether failure occurs before or after Submit. Include sanitized console/request errors, plus Core/add-on versions. Never include the Secret key, browser cookies or a live verification token.