The IP list has no effect while the service is private. Undo private first.

ip-allowlist-while-private · 409

The change sets an IP list where the service is private, and a private service has no public address to filter, so the API staged nothing.

environmentName names the environment. The reach that counts is the one staged for it, or the published one when none is staged. Making a service private also drops an IP list change that was waiting.

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

Common causes

  • The service is private in this environment, and ghaym cloud access ips add or ips remove staged a list for it.
  • Private is staged and waiting to be applied, and the list came after it.

How to fix the call

  • Undo private first: stage another reach with ghaym cloud access set <service> --reach public --env <env>, then add the list.
  • Or keep the service private: only the project's services reach it, so it needs no list.
  • Don't retry unchanged: the answer stays the same while the service is private.

Example response

json
{
  "type": "ip-allowlist-while-private",
  "title": "The IP list has no effect while the service is private. Undo private first.",
  "detail": "The service is private in staging, so an IP list would have no effect 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/ip-allowlist-while-private"
}