Troubleshooting Test Connection Failures
Test Connection prepares native Joomla WebCron, performs service registration/validation, and sends a real WebCron probe; failures can therefore occur at local configuration, public reachability, route/authentication, or Joomla task execution layers.
Read the exact failure before changing anything
| Failure family | First place to investigate |
|---|---|
| Schedule Runner/Scheduler missing | Joomla plugin/component installation and enabled state. |
| DNS/public-IP validation | Public DNS and whether the host resolves to an Internet-routable target. |
| TLS/certificate | Certificate validity, hostname coverage, trust chain, server TLS configuration. |
| HTTP 401 | WebCron key/credential synchronization. |
| HTTP 403 | WAF/server access rule; if QuantaCade and Joomla are same physical server, current service has a narrow same-server fallback only for this case. |
| HTTP 404 / route error | Joomla SEF/base path/native AJAX route. |
| HTTP 2xx with success:false | Joomla was reached; inspect the Scheduled Task/application result. |
Remember the side effect
Test Connection’s public registration probe is a real native WebCron request and may run one eligible due task. If you need only local preparation without a task-execution opportunity, use Check WebCron.
Preserve the failure evidence
Before attempting a repair for Troubleshooting Test Connection Failures, record the HTTP/status message, Scheduler Health, due/lock counts, WebCron state, QuantaCade Contact, and Recent Activity timestamp. For lock/task problems, also capture the owning Scheduled Task title/type and extension log.
That evidence lets you verify the fix and avoids converting a precise 401/403/404/task_failed condition into an ambiguous “it works now” report.
Troubleshoot in order
- Run Check WebCron first and fix any local Joomla prerequisite error.
- Run Test Connection and record the exact DNS/TLS/HTTP/application result.
- Map that result to the correct layer—public DNS/TLS, 401 credential, 403 access control, 404 route, or Joomla task failure.
- Repair only that layer and rerun Test Connection to confirm the same failure signal is gone.
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.