← All docs

Resolve connection, licence, rendering, and cache problems.

The connector is listed but tools do not work

Confirm Checknaut Pro is active, then check the site URL, authentication method, plugin activation, the AI assistant screen, client plan eligibility, and host restrictions. Tools that need an active licence, including the Builder Pack and Privacy Pack tools, are withheld until the licence is active. Run the plugin's connection test under Tools › Diagnostics. Reconnect after a plugin update to refresh the tool list.

Some tools are missing

Read the site context. Tools are filtered by the builder, active integrations, licence, permissions, and owner settings. Elementor tools are absent on a Divi site; WooCommerce context needs WooCommerce. A missing feature is not a reason to bypass a lock. Tool names start with checknaut_; an assistant that asks for an old station_ or divi_ name gets an “Unknown tool” error and should refresh its tool list.

Pro says it is unlicensed

Enter the licence at Checknaut → Licensing, and confirm the plan has an available seat. Until then, every free feature keeps working and one notice under the Checknaut header says how to activate or renew. Use your Freemius account for billing or download issues. Do not send the full licence key in a public ticket.

Updating Checknaut Pro

Update Pro from the Plugins screen, like any other plugin. Checknaut does not install its own updates.

An edit saved but visitors see the old page

Check the page as a logged-out visitor. Clear its Divi/WordPress caches using the supported cache control. Host/CDN edge caches may need a separate purge in the host's panel; the connector cannot purge an unconfigured external service. Compare the normal URL with a cache-busted read to identify stale caching.

A module renders blank

Check the owning builder, required module/plugin, schema, token IDs, content paths, presets, and render result. On Divi, attributes nest under their innerContent/advanced/decoration groups and breakpoint values. A string where a module expects an object can be invalid. Use the site's live module schema and authoring guide.

A page returns 403 or 500 after a write

Stop further changes. Compare the stored content with the previous revision and check the plugin's render validation/error. A WAF may refuse a payload; a PHP error may come from a bad value shape or required runtime context. Restore the specific bad change when appropriate and inspect the served page again.

The self-test is still running

Wait or continue the run as instructed. Partial results are not a pass. Some groups require a builder, store, or configured service and should be reported as skipped with their reason. Write-scope self-tests create fixtures; do not run them while an assistant or Visual Builder is editing the site.

A form does not send

Verify the configured recipient, spam protection, success message, SMTP setup, and provider logs. A styled form is not evidence of delivery. Test using your own address and a clearly marked test message; avoid sending unsolicited client email.

Ask for support

Email support@checknaut.com with plugin and builder versions, the affected page, steps to reproduce, and the error without secrets. Redact connector keys, licence keys, API tokens, and customer information.

Need help with your install? Contact support. Related: Getting started.

Reviewed for Checknaut 2.0.0 on 31 October 2026.