Changing a Site Between HTTP and HTTPS

Changing a site between HTTP and HTTPS is a meaningful QCTNH origin change because the local identity comparison requires the scheme to match.

Why the scheme matters

The registered native Joomla WebCron endpoint must use the same scheme and host as the site origin. HTTPS also gives the worker authenticated TLS transport; it is strongly recommended for production.

Migration procedure

  1. Complete the HTTP→HTTPS (or HTTPS→HTTP) Joomla/server redirect and canonical-URL change.
  2. Verify the final URL directly and ensure the TLS certificate is valid when using HTTPS.
  3. Open QCTNH Dashboard on the final scheme.
  4. Use Check WebCron to ensure Joomla generates the correct current-scheme WebCron URL.
  5. Use Test Connection to confirm the origin change and register the new endpoint.
  6. Confirm Connected and review Recent Activity.

Avoid redirect-dependent registration

The central worker deliberately does not follow arbitrary redirects. Register the final native WebCron URL itself rather than expecting an old HTTP endpoint to redirect into HTTPS on every wake-up.

What should remain unchanged

During Changing a Site Between HTTP and HTTPS, Joomla Scheduled Task definitions remain owned by Joomla and their extensions. QCTNH identity rotation does not rewrite task recurrence or choose new task IDs. Likewise, a same-domain restore may preserve QCTNH identity while separately changing task next-execution/lock timestamps because those values came from the restored Joomla database.

Review both layers after migration: service identity/connectivity and scheduler queue state.

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.