client_has_debt
HTTP 402 Account has an overdue invoice
What happened
The project is still running, but the owner of the project has an invoice past its due date. What stays allowed until it is paid depends on the product. A server project accepts only these changes: deleting (servers, disks, network interfaces, backups, public IP addresses, private networks, SSH keys, your own ISO and server images, router access rules and port forwards, WireGuard and OpenVPN devices), detaching a router from a network, ejecting an ISO image, adding and removing server tags, with an account key also deleting an empty project, changing its labels and issuing or revoking its keys, and switching off - automatic backups of the project or of a server (any body with enabled: false, schedule fields included) and a router's WireGuard or OpenVPN tunnel. Every other change is refused with this code: creating anything, renaming, resizing a server or a disk, changing a network interface, attaching a router, inserting an ISO image, power actions (switching a server off included), reinstalling, resetting the password or adding SSH keys, taking or restoring a backup, the server firewall, and router settings other than the removals and switch-offs above. Reads always work, all but one in object storage (below). An object storage project refuses much less: only reserving storage, and - while the project has no reserved storage yet - creating a bucket, an access key or a service account. Deleting and renaming keep working; in a project that has reserved storage, so do creating (buckets, access keys, service accounts) and showing the secret of an access key. The one read it refuses is the access keys of a project with no reserved storage (and showing their secret), the same as the client area.
What to do
Pay the overdue invoice, then repeat the same request with the same idempotency key. For a server project service_suspended refuses exactly the same changes: the two codes tell what state the project is in, not how much is blocked. Here the project and its servers keep running; there the project is suspended and the platform has asked its running servers to power off. For object storage the two differ: a suspended object storage project refuses every change except renaming it.
Retrying
Change the state this refers to, then repeat the same request with the same idempotency key.
How it arrives
{
"type": "https://docs.fiberax.com/errors/client_has_debt",
"title": "Account has an overdue invoice",
"status": 402,
"code": "client_has_debt",
"request_id": "a277dcd1ca652c65"
}
Branch your code on code, never on the wording of title.