Troubleshooting TLS and Certificate Errors

TLS/certificate errors prevent the production worker from establishing a trusted HTTPS connection to the registered Joomla WebCron endpoint.

What the worker requires

  • Certificate is within its valid date range.
  • Certificate hostname matches the registered site host.
  • The server presents a usable trust chain to a standard client.
  • TLS negotiation succeeds with peer and host verification enabled.

Typical causes

  • Expired certificate.
  • Wrong-host certificate after a domain migration.
  • Incomplete intermediate chain.
  • Self-signed/private CA certificate not trusted by the public service.
  • Broken reverse proxy/CDN origin/TLS configuration.

Repair and verify

  1. Test the final public HTTPS URL with an independent TLS checker/client.
  2. Fix the certificate or chain; do not disable QCTNH certificate verification.
  3. Ensure redirects are not hiding a different final host.
  4. Run Test Connection again and confirm Connected.

Preserve the failure evidence

Before attempting a repair for Troubleshooting TLS and Certificate Errors, 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.

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.