Troubleshooting a Site Origin Mismatch
An origin mismatch is usually a clone/migration/canonical-URL issue, not a scheduler failure. QCTNH deliberately refuses to auto-adopt the different origin.
Identify why the URL changed
| Cause | Action |
|---|---|
| Intentional new domain/scheme/path | Complete the migration, then run Test Connection from the final canonical URL to rotate identity. |
| Staging/development clone | Do not confirm the new origin unless the clone should have its own service identity. |
| Proxy/HTTPS misconfiguration | Correct Joomla/proxy URL detection first so the site reports its real public origin. |
| www vs non-www only | Normally treated equivalent locally when scheme/path match; inspect redirect/proxy data if a warning still appears. |
Use Recent Activity
An automatic mismatch can produce origin_mismatch_ignored. A successful explicit migration can produce origin_changed_confirmed, followed by registration success.
Confirm recovery at the same layer
After fixing Troubleshooting a Site Origin Mismatch, 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.
Troubleshoot the mismatch
- Identify the currently displayed Joomla URL and the site’s intended canonical origin.
- Decide whether the difference is a real migration, a staging clone, or incorrect proxy/HTTPS URL detection.
- Fix accidental URL/proxy configuration first; do not rotate identity to accommodate a wrong URL.
- For a legitimate final migration, open that final URL and use Test Connection to explicitly confirm the new origin.
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.