Troubleshooting Not Connected Status

Not Connected means QCTNH cannot currently treat the local installation as fully registered and synchronized with the wake-up service; diagnose local WebCron readiness, identity, and external registration in that order.

Step 1: read the Dashboard evidence

  • WebCron field: ready or needs attention?
  • Site Origin Mismatch warning present?
  • QuantaCade Contact: never or stale?
  • Recent Activity: registration failed, WebCron not ready, sync failed, or origin mismatch event?

Step 2: verify local Joomla WebCron

  1. Select Check WebCron.
  2. If it fails, fix the missing/disabled Schedule Runner plugin, Scheduler component, or local configuration first.
  3. If it succeeds, confirm WebCron now reports ready.

Step 3: verify registration

  1. If the origin is intentionally current, select Test Connection.
  2. If a mismatch is accidental, fix Joomla/canonical URL/proxy configuration before testing.
  3. Review the exact error. DNS, TLS, public-IP validation, 401/403/404, and service errors need different fixes.

Do not chase license settings

QCTNH 2.0.3 is free and has no entitlement state. Not Connected is an operational condition, not an expired license.

Diagnose from the outside in

For Troubleshooting Not Connected Status, a reliable order is: local Joomla prerequisites → QCTNH WebCron readiness → public DNS/TLS/route → WebCron authentication → Joomla Scheduler/task result. Each layer produces different evidence, so skipping directly to reinstalling QCTNH often obscures the real cause.

Use Check WebCron for the local layer and Test Connection for the full public registration/probe layer. Then use Joomla/extension logs if the request succeeded but the task itself failed.

Community Discussion

Want to compare scheduler workflows, share practical tips, or discuss how you use this QCTNH feature? Visit the QC Task Nudge & Health Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.