The SDK talks to api.e2b.app instead of Anona
The SDK talks to api.e2b.app instead of Anona
E2B_DOMAIN=compute.anonalabs.com. Recent SDKs ignore E2B_API_URL. Or use anona_compute.Sandbox / @anona-labs/compute-sdk, which default to the Anona domain.404 sandbox not found, but I just created it
404 sandbox not found, but I just created it
- The sandbox may have reached its timeout and been deleted (the default is 300 s from the SDK). Use a longer
timeout,set_timeout, orlifecycle={"on_timeout": "pause"}. - The key may belong to another organization, or be limited to a list of sandbox IDs. Both look exactly like “not found”.
403 your access cannot open this sandbox
403 your access cannot open this sandbox
sandboxes:use (needed for commands, live view and SSH), or your dashboard role is viewer. Create a key with Create and use, or ask an admin for the member role.403 this API key lacks the usage:read scope
403 this API key lacks the usage:read scope
anona-compute usage, the MCP get_usage tool and GET /v1/usage need a key with usage:read (the Read only and Full access presets have it); billing needs billing:read (Full access). Create a new key; existing keys keep their scopes.403 only organization owners and admins ... may change network settings and vault secrets
403 only organization owners and admins ... may change network settings and vault secrets
403 vault secret ... is not bound to ... for this sandbox
403 vault secret ... is not bound to ... for this sandbox
vault:bind scope (a custom key; no preset has it). Or ask an owner to put the rule in the team egress settings, which every sandbox can use. See Bindings and who can make them.400 no vault secret named ... is bound to this sandbox / store it in the credential vault first
400 no vault secret named ... is bound to this sandbox / store it in the credential vault first
${vault.<name>}), then create the sandbox again. Either the dashboard’s Credential vault page, or:403 vault secret ... may not be sent to ...
403 vault secret ... may not be sent to ...
anona-compute vault list and replace it with anona-compute vault allowed-hosts <name> --host api.github.com. A *. entry does not cover the domain itself: *.github.com does not cover github.com.A secret stored before allowed hosts existed has none recorded and cannot be used until you set one.502 on a request that should carry a vault header
502 on a request that should carry a vault header
Authorization header would reach the upstream unauthenticated.The handshake to the host still succeeds, so this looks like the upstream failing rather than the policy. Causes, commonest first:- The secret was deleted, or the binding was revoked (
anona-compute vault listshows neither). - The allowed-hosts list was narrowed and no longer covers this host.
- The organization is suspended for billing or abuse; every resolution is refused while it is.
Certificate error on a host with a vault rule
Certificate error on a host with a vault rule
/etc/ssl/certs/ca-certificates.crt, so curl, Python’s default SSL context and Node work. A client with its own certificate store does not: Python with certifi’s bundle passed explicitly, a Java keystore, or a pinned certificate.Point the client at the system bundle. In Python, drop cafile=certifi.where() or pass /etc/ssl/certs/ca-certificates.crt instead; for Java, import that file into the keystore the client uses. A certificate pinned for that host cannot match, so remove the pin.429 concurrent sandbox limit reached, or concurrent vCPU limit reached
429 concurrent sandbox limit reached, or concurrent vCPU limit reached
anona-compute list, then anona-compute delete), or pause them: paused sandboxes do not count as running. For the vCPU limit, a smaller size also helps: on Free, size: "small" is 1 vCPU, and a sandbox created without a size from base is 2. The error’s limit_name, limit and current say which limit and how much is in use. See limits.403 plan_limit_exceeded
403 plan_limit_exceeded
included_vcpu_hours, included_egress_gb; it resets on the first of the month). limit_name says which. Delete something you no longer need, or upgrade the plan. See limits.400 timeout -1 (no limit) is not available
400 timeout -1 (no limit) is not available
400 volumeMounts / iam / autoPauseMemory=false are not supported
400 volumeMounts / iam / autoPauseMemory=false are not supported
400 on create with network.allow_out
400 on create with network.allow_out
allow_out need public egress off: add deny_out: ["0.0.0.0/0"]. Destinations in private or metadata ranges, and names that resolve into them, are always refused. Wildcard names such as *.example.com are not supported yet: name each host. See Networking.503 with Retry-After on create
503 with Retry-After on create
sandbox_capacity_unavailable, every host is full and another is starting, which takes a few minutes. The CLI waits up to --capacity-wait (10 minutes). The stock E2B SDK retries for about a minute; the Anona SDK extras, from 0.3.0, wait up to 10 minutes (Python, TypeScript). If you call the API yourself, wait Retry-After seconds and retry while the response says Should-Retry: true.409 when opening a sandbox URL
409 when opening a sandbox URL
Sandbox.connect(id) or anona-compute resume <id>.ssh: Permission denied (publickey)
ssh: Permission denied (publickey)
anona-compute ssh <id> again, or refresh the block with anona-compute ssh <id> --print-config.The live view says the token expired or closes at once
The live view says the token expired or closes at once
token-request message with a fresh token (Live view). After revoke_all, mint new tokens.A template build fails with EXPOSE 49983 or an unpinned FROM
A template build fails with EXPOSE 49983 or an unpinned FROM
envd), so a template cannot expose it. Every FROM is pinned by digest at build time; a tag that cannot be resolved fails the build. See Templates.anona-compute keys / limits / push / recover say not available
anona-compute keys / limits / push / recover say not available
Get more detail
anona-compute -v …prints verbose detail on stderr.- Every API error body has
code,messageandrequestId, and oftenerror_code. Include therequestIdwhen you contact support.