Troubleshooting Turnstile Submission Problems
If a protected form does not complete as expected, start by finding out whether Turnstile rejected the submission or whether another part of the form workflow failed afterward. These are different problems and require different checks.
Step 1 — Check the Turnstile connection
In Nexus Control Center, confirm that the current Cloudflare site key and secret key have been saved and verified. If you recently changed either key or the site's hostname, run the connection test again.
Check that your site can reach Cloudflare and that the correct hostname is allowed for the Cloudflare Turnstile widget.
Step 2 — Confirm the form is actually protected
For Divi Contact Form or Email Optin, check that Turnstile is enabled in that module's Spam Protection settings.
For WordPress and WooCommerce surfaces, check Core Protection. If WooCommerce was installed or reactivated after Nexus, explicitly review and enable the WooCommerce protection setting rather than assuming it switched on automatically.
For supported third-party forms, open the relevant Pro integration section. Check for an eligible, protected status; do not assume an active vendor plugin means its forms are protected.
Step 3 — Test the published page
Test the normal public-facing page, not only the editor or Visual Builder. If the page contains several forms, test them one at a time.
Turnstile may complete automatically without an interactive puzzle. That does not mean verification was skipped.
If Turnstile rejects the submission
A failed challenge may happen because the response is missing, expired, already used, invalid, or does not match the expected site or form action. Nexus is designed to reject a protected submission when verification cannot be completed.
Reload or retry the form normally and obtain a fresh Turnstile response. If the problem persists, check caching, script optimization, competing CAPTCHA tools, and any form-specific compatibility warning.
Do not attempt to bypass Turnstile as a permanent workaround for a protected form.
If Turnstile succeeds but the action still fails
A valid Turnstile response is not a guarantee that the rest of the form action succeeds.
- Contact form email not delivered: check WordPress/Divi mail settings and SMTP delivery.
- Email signup not created: check the list/audience, provider credentials, and vendor plugin logs.
- Checkout fails after verification: check WooCommerce checkout details, payment gateway status, and native order/checkout errors.
- Comment or review not visible: check WordPress moderation and comment settings.
- Login fails after verification: check the account credentials and any separate 2FA step.
A failed email, payment, or subscription can occur after Turnstile has already successfully verified the visitor.
If a form appears under Needs Attention
Open its details and review the reason. Conflicting saved identities, unsupported plugin versions, or native CAPTCHA ownership can prevent Nexus from safely claiming protection.
When contacting support
Send the Nexus edition/version, WordPress/PHP/Divi versions, affected plugin version, form type, admin status, and a description of the result. A screenshot of the relevant status (without private data) can help.
Never send your Cloudflare secret key, raw Turnstile tokens, passwords, customer messages, payment details, or subscriber data.
