Connect a domain first to turn off the ghaym.app address.

custom-domain-required · 409

The change asks the service to answer on its custom domains only, and none would answer in this environment, so the API made no change.

environmentName names the environment. The check runs when the change is staged and again when it is applied, since a domain can be removed, or its DNS can move, in between.

Besides the members every error carries, this type adds environmentName.

Common causes

  • --reach custom-domain was set for an environment where the service has no live custom domain.
  • The service is private there, and none of its domains still points at Ghaym, so none would answer once it opens.
  • A domain was removed, or its DNS moved, after the change was staged, so applying it was refused.

How to fix the call

  • Add a domain with ghaym cloud domains add <service> <hostname>, verify it with ghaym cloud domains verify <service> <domainId>, then set --reach custom-domain again.
  • Or keep the ghaym.app address open with --reach public.
  • If applying was refused, fix the domain's DNS, then apply the changes again.

Example response

json
{
  "type": "custom-domain-required",
  "title": "Connect a domain first to turn off the ghaym.app address.",
  "detail": "The service has no live custom domain in staging, so it would have no address there",
  "environmentName": "staging",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/environments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/changeset/entries",
  "method": "PUT",
  "instance": "PUT /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/environments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/changeset/entries",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/custom-domain-required"
}