Troubleshooting HTTP 404 or Incorrect WebCron Routes

HTTP 404 or route errors usually mean the registered WebCron URL does not match the Joomla site’s current SEF mode, base path, rewrite configuration, or component/AJAX routing.

Expected route families

  • Non-SEF: /index.php?option=com_ajax&plugin=RunSchedulerWebcron&group=system&format=json.
  • SEF: a Joomla AJAX route such as /component/ajax or /index.php/component/ajax with the scheduler plugin/group/format query values.

Repair

  1. Open the final canonical frontend URL and confirm Joomla routing works.
  2. Run QCTNH Check WebCron; it asks Joomla to generate the route instead of reusing a hand-entered URL.
  3. If Joomla moved into/out of a subdirectory or SEF settings changed, use Test Connection so the new endpoint is registered.
  4. Check rewrite/.htaccess/proxy rules if Joomla-generated component AJAX URLs themselves return 404.

Do not depend on redirects

The QCTNH worker does not follow arbitrary redirects. Register the final route that responds directly.

Confirm recovery at the same layer

After fixing Troubleshooting HTTP 404 or Incorrect WebCron Routes, verify the original failure signal specifically: a 401 should disappear after key synchronization, a 404 after route repair, a TLS error after certificate repair, a stale-lock Attention state after safe task recovery, and a task_failed result only after the owning task succeeds.

Then confirm the broader Dashboard state is coherent rather than treating Connected alone as proof that every Scheduled Task is healthy.

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.