Why Private and Reserved IP Targets Are Rejected

Private and reserved IP targets are rejected to prevent QCTNH’s public service from becoming an SSRF-style proxy into networks that should not be reachable from the Internet.

Examples of unsuitable targets

• Loopback/localhost addresses.
• RFC1918 private IPv4 ranges used on LANs.
• Link-local or other reserved/special-use address space.
• Private/internal IPv6 ranges or other non-public destinations.

Operational effect

If the registered hostname resolves only to one of these destinations, Test Connection/registration cannot complete. The remedy is not to weaken QCTNH validation; expose the intended Joomla site through a legitimate public canonical URL, or use local/server cron for a private installation.

After DNS changes

If a previously public hostname is repointed during a migration, verify public DNS before running Test Connection. A failed public-IP validation is evidence that the new service target is not yet safely reachable.

Public service assumption

Why Private and Reserved IP Targets Are Rejected assumes QuantaCade can safely reach the Joomla site from the public Internet. Private development environments can still use Joomla Scheduler through local/CLI/server-cron mechanisms, but they are intentionally outside the central Task Nudge wake-up model.

This is a product security constraint, not a licensing restriction; QCTNH remains free.

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.