How QCTNH Uses Site Origin as Part of Installation Identity

QCTNH treats the site origin as part of installation identity so a copied database cannot silently make a clone impersonate the production site.

What “origin” means

QCTNH derives a canonical site origin from the Joomla site URL: scheme, hostname, any supported base path, and normal/default port behavior. Local identity records store the registered origin together with an installation UUID and a hash of the active Joomla WebCron key.

Why identity includes origin

• A cloned database contains the original installation UUID and encrypted service secret.
• Without origin protection, a staging clone could overwrite the production registration and redirect wake-ups to itself.
• QCTNH therefore refuses automatic origin adoption when the current request origin no longer matches the registered origin.

Intentional moves require confirmation

After a real migration, browse the intended canonical URL and use Dashboard → Test Connection. That explicit action is allowed to rotate installation identity for a genuinely different origin and register the new native WebCron endpoint.

Finish the canonical URL first

Before applying How QCTNH Uses Site Origin as Part of Installation Identity, settle DNS, HTTPS, www/non-www policy, and Joomla base path. QCTNH registers an exact native WebCron endpoint whose scheme/host/path must correspond to the final site origin. Registering during an intermediate redirect state creates avoidable 301/302, TLS, or route failures.

After the public URL is stable, Check WebCron rebuilds the local native route and Test Connection confirms public reachability/identity.

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.