err:unkey:limits:custom_domain_limit_exceededExample
What Happened?
You calledcreateDomain for a workspace that has already attached every custom domain its plan permits.
The allowance is counted per workspace, across every project, app, and environment in it. Attaching domains to different environments does not raise it, so a workspace allowed one domain cannot hold one per environment.
How To Fix
- Check how many domains the workspace already holds, and whether any are still in use.
- Remove one you no longer need, from the app’s settings page in the dashboard.
- If they are all still in use, upgrade the plan to raise the allowance.
- Retry the request.
Common Mistakes
- Expecting the allowance to be per environment: A domain in each environment still counts against one workspace-wide allowance.
- Counting only verified domains: A domain still
pendingverification occupies the allowance, so an abandoned setup keeps taking a slot. - Retrying on a schedule: Nothing about the workspace changes between attempts, so a retry loop fails until the plan or the domain list changes.
Related Errors
- err:unkey:data:domain_already_exists - When the name is already attached to this workspace
- err:unkey:authorization:forbidden - When the root key or its workspace is disabled