Restoring a QCTNH Site to the Same Domain

Restoring a QCTNH site back to the same canonical domain normally preserves its service identity, provided the registered origin and Joomla WebCron key still match the restored/current configuration.

After a same-domain restore

  1. Open Joomla Administrator on the normal canonical URL.
  2. Open QCTNH Dashboard and check Connected, WebCron, Scheduler Health, and Recent Activity.
  3. Run Check WebCron to ensure the Schedule Runner plugin, WebCron-enabled flag, and native key are present.
  4. If the WebCron key changed during the restore or was regenerated, allow QCTNH to synchronize the credential drift.
  5. Use Test Connection only if the service is not connected after local configuration is correct.

Identity expectations

Because the origin is unchanged, QCTNH should not need a migration identity rotation. The registered state also checks a hash of the current WebCron key, so a restored database combined with a different key may require WebCron synchronization before Connected can be trusted.

Check scheduled-task state separately

Restoring the database can also move Joomla Scheduled Task next_execution values and locks backward in time. Review Due Tasks and lock counts after the restore; those scheduler rows are independent of QCTNH service identity.

Preserve clone protection while migrating

The rule behind Restoring a QCTNH Site to the Same Domain is intentionally conservative: a copied database is not permission to move the existing service identity to whatever hostname now serves that copy. Automatic activity preserves the registered origin and records a mismatch instead of rotating credentials.

Only an administrator-triggered Test Connection from the intended final canonical URL may confirm a true move. That explicit step protects the original site while still making legitimate migrations straightforward.

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.