Resolving [Domain] can't be routed to a known Qloaked application

This error normally occurs when Qloaked isn't able to reconcile the forwarding host with a CNAME target in its database.

For instance, if http://helpdesk.bluthcompany.com has a CNAME record pointing at secured.acmeapp.com (which then points at the Qloaked app), Qloaked will look up secured.acmeapp.com to determine which application traffic should be routed to.

If secured.acmeapp.com hasn't been listed as a CNAME target on the AcmeApp Qloaked account, the person visiting the page will receive an error saying that "http://helpdesk.bluthcompany.com can't be routed to a known Qloaked application".

Normally this can be fixed by filing a support ticket to check/amend the CNAME target on file for your company.

Very occasionally, it could also be because the Google Cloud DNS (where we host our Kubernetes clusters) will take a short time to pick up DNS changes made for a domain – in which case the problem normally resolves in a minute or two.