Error reference
Last updated 13 October 2026
Every error from the Amelu API carries a stable code. Errors caused by a server-side fault end in a link to the matching section on this page and, in the dashboard, a request id. Quote that request id when you contact support; it points straight at the matching line in the server log.
The response body is JSON with error (the sentence shown), code, status, requestId and, for upstream failures, detail with the full underlying error. The same request id is in the X-Request-ID response header.
MAIL_CLUSTER_UNREACHABLE HTTP 502
The mail cluster could not be reached
The dashboard talked to the Amelu API fine, but the API could not open a connection to the mail cluster that actually stores your domains and mailboxes. The reason in brackets (for example "connection reset by peer" or "connection refused") is the network error as seen from the API.
Nothing was changed. Wait a moment and retry. If it keeps happening for more than a few minutes, check status.ordnary.com and contact support with the request id from the error.
MAIL_CLUSTER_TIMEOUT HTTP 502
The mail cluster did not answer in time
The connection to the mail cluster opened, but no answer came back before the request was cancelled. This usually means the cluster is under load or restarting.
A write (creating a mailbox, changing a password) may or may not have been applied. Reload the page before retrying so you see the current state.
MAIL_CLUSTER_AUTH HTTP 502
The mail cluster rejected the API's credentials
The mail cluster answered 401 or 403 to the Amelu API itself. This is never caused by your account or password; it means the API's own service credentials for the cluster are wrong or were rotated.
This needs an operator. Contact support with the request id.
MAIL_CLUSTER_HTTP_ERROR HTTP 502
The mail cluster returned an HTTP error
The cluster answered with a status other than 200 (for example 500 or 503). The message names the status and the JMAP method that was being called.
Retry once. If it persists, contact support with the request id.
MAIL_CLUSTER_PROTOCOL HTTP 502
The mail cluster sent an unreadable response
The cluster answered 200 but the body was not a valid JMAP response. This typically points at a proxy or a version mismatch between the API and the cluster.
This needs an operator. Contact support with the request id.
MAIL_CLUSTER_REJECTED HTTP 502
The mail cluster refused the change
The cluster understood the request but refused it with a JMAP error. The message names the JMAP method, the error type (such as invalidArguments or forbidden) and the cluster's own description.
Check the values you entered. If they look right, contact support with the request id.
MAIL_CLUSTER_NOT_FOUND HTTP 502
The object no longer exists in the mail cluster
Amelu's records say a domain, mailbox or message exists, but the cluster says it does not. The two can drift when a change was applied on one side only.
Reload the page. If the object is still listed, contact support with the request id so the records can be reconciled.
UPSTREAM_ERROR HTTP 502
An external service failed
A service Amelu depends on, other than the mail cluster, returned an error: for example the transactional email provider when sending an invitation. The message says which action failed.
Retry in a moment. Anything that was already saved stays saved; the message says so when a change was applied but a follow-up step failed.
STRIPE_ERROR HTTP 502
Billing could not be processed
Stripe, which handles Amelu's payments, returned an error. When Stripe gives a specific code the error uses it instead (for example STRIPE_CARD_DECLINED) and names the parameter it refers to.
Check the card or billing details and retry. Nothing was charged.
INTERNAL_ERROR HTTP 500
Something went wrong inside the Amelu API
The API itself failed, most often because its own database could not be read or written. The message says which step failed.
Retry once. If it persists, contact support with the request id; it points straight at the server log line.
SERVICE_UNAVAILABLE HTTP 503
This feature is not configured on this server
An optional integration (billing, password reset emails, Ordnary login) is not set up on the server you are using. On amelu.org these are always on; on a self-hosted install the operator has to configure them.
BAD_REQUEST HTTP 400
The request was not valid
Something in what was sent is missing or malformed. The message says what. These errors do not carry a request id because nothing failed on the server side.
UNAUTHORIZED HTTP 401
Not signed in
The session has expired or the API key is not valid. Sign in again.
FORBIDDEN HTTP 403
No permission
Your role in the organization does not allow this action, or a plan limit was reached. An owner or admin can change roles under Organization.
NOT_FOUND HTTP 404
Not found
The domain, mailbox or other object does not exist, or belongs to a different organization.
CONFLICT HTTP 409
Conflict with the current state
The change clashes with something that already exists, such as a duplicate name, or would leave the organization without an owner.