Understanding the Site Origin Mismatch Warning
The Site Origin Mismatch warning means the Joomla installation currently being viewed does not match the origin QCTNH previously registered, so automatic identity changes have been blocked.
Why QCTNH blocks automatic repair
A database clone carries the original QCTNH identity. Automatically adopting whatever hostname happens to load the clone would let staging/development copies hijack production wake-ups. Instead QCTNH logs an origin_mismatch_ignored event and preserves the existing identity.
Decide whether the mismatch is expected
| Situation | Response |
|---|---|
| Temporary/staging clone | Leave the original production identity protected. If the clone needs its own wake-up service, explicitly Test Connection on the clone and accept that it becomes a distinct installation. |
| Real domain/canonical URL migration | Open the intended new canonical URL and run Test Connection to confirm the origin change and rotate identity. |
| Unexpected mismatch | Check Joomla URL/proxy/HTTPS configuration before changing identity; fix the incorrect URL source first. |
Use Recent Activity as migration evidence
For Understanding the Site Origin Mismatch Warning, QCTNH records useful origin lifecycle events. An unconfirmed different origin can produce origin_mismatch_ignored; an explicit accepted move can produce origin_changed_confirmed, followed by registration/synchronization results.
These events are safer evidence than guessing from a stale Connected badge after a restore or clone.
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.