Troubleshooting HTTP 401 or WebCron Authentication Failures

HTTP 401 from Joomla WebCron usually indicates the request reached the correct route but the WebCron authentication key does not match the current System - Schedule Runner key.

Likely causes

  • Joomla WebCron key was regenerated after QCTNH registered.
  • A database/configuration restore brought back a different Schedule Runner key.
  • The central service still has an older key because synchronization failed.

Repair procedure

  1. Run Check WebCron and confirm WebCron is ready with a non-empty current key.
  2. Save/review Joomla Schedule Runner configuration if it was intentionally changed. The QCTNH system plugin listens for Scheduler configuration saves and attempts synchronization.
  3. Run Test Connection if Connected does not recover.
  4. Verify Recent Activity reports synchronization/registration success and a later wake-up no longer returns 401.

Do not publish the key

Diagnose by state and response code. There is normally no need to paste the raw WebCron key into a forum or screenshot.

Diagnose from the outside in

For Troubleshooting HTTP 401 or WebCron Authentication Failures, 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.