config_not_found

{
  "meta": {
    "requestId": "req_3k2j1h0g9f8e7d6c"
  },
  "error": {
    "code": "err:frontline:routing:config_not_found",
    "message": "No deployment found for this hostname. Please check your domain configuration or contact support at support@unkey.com."
  }
}

​

If you’re calling an API hosted on Unkey

​

If you own this API

• A custom domain is still waiting for verification, even if its DNS already points at Unkey.
• The hostname isn’t one of the deployment’s domains, or has a typo.
• The domain was removed, or the deployment it pointed at was deleted.
• The certificate for a custom domain won’t issue.

​

How to fix

1. Check that the hostname is one of the domains listed on the deployment or environment.
2. For a custom domain, check its verification status and the DNS records we asked for, then wait for verification to finish.
3. If the hostname used to work, check whether the domain was removed or its deployment deleted.

​

Related errors

• err:frontline:capacity:deployment_offline: the hostname is routed but the deployment is stopped.
• err:frontline:platform:config_load_failed: the route couldn’t be loaded because of a failure on our side.