nnesly

Errors

What each error reason code means and the command that takes you forward.

When nesly refuses a request, the answer carries a reason code. The message says what is wrong; this page says what to run next. The code is the same in the CLI, the MCP server and the console.

ROLLOUT_IN_PROGRESS

A release is already being rolled out to a share of traffic.

Next: nesly rollout promote Promote finishes it; nesly rollout abort stops it.

NO_ROLLOUT

Nothing is being rolled out, so there is nothing to promote or abort.

Next: nesly deploy --percent <1-99> Starts a rollout with that share of traffic.

ROLLOUT_PERCENT_RANGE

The share of traffic must be 1 to 99; 0 and 100 are abort and promote.

Next: nesly rollout promote Finishes the rollout at 100; nesly rollout abort is 0.

PROMOTE_NEEDS_READY

Only a ready deployment can be promoted.

Next: nesly rollback Brings back an earlier live release.

ROLLBACK_IS_PREVIEW

A preview deployment was never live, so there is nothing to roll back to.

Next: nesly promote <deployment-id> Makes the preview the live release.

NO_SOURCE

There is no repository and no upload to build from.

Next: nesly deploy Run it from the project directory: it uploads the directory.

ADDON_MISSING

The project has no addon of the type this needs.

Next: nesly addon add <type> Attaches one; its connection values reach the app as environment variables.

PROJECT_NAME_TAKEN

The target account already has a project with this name.

Next: nesly project rename <project> <new-name> Rename it first, then repeat the move.

NOT_A_MEMBER

You are not a member of the account you named.

Next: nesly account ls Shows the accounts you can work in.

DOMAIN_NOT_DELEGATED

The domain's DNS is not delegated to the platform yet.

Next: nesly domain delegate <domain> Prints the nameservers to set at your registrar.

SPEND_CAP_REACHED

This month's usage charge reached the account's monthly spend cap.

Next: nesly usage budget set --spend-cap <usd> Raises the cap; --spend-cap none removes it.

SPEND_CAP_NOT_SET

The included amount is used up and the account has no spend cap, so nothing past it is sold yet.

Next: nesly usage budget set --spend-cap <usd> Sets a cap.

USAGE_BUDGET_HARD_PERCENT

The account's own usage budget stops builds below 100% of the included amount.

Next: nesly usage budget set --build-hard 100 --egress-hard 100 Raises the hard percent.

LIMIT_PACK_AVAILABLE

A count limit was reached that a limit pack raises.

Next: nesly limits pack set <resource> <packs> nesly limits packs shows sizes and prices.

MODEL_NOT_SERVED

No engine serves this AI model in this region yet.

Next: nesly models request <model-id> Asking costs nothing and promises no date; nesly models list shows the catalog.

PLAN_UPGRADE_REQUIRED

The feature is not on the account's plan.

Next: A paid plan has it; change the plan on the billing page of the console.

RESCUED

The platform got you unstuck by itself and the work went through.

Next: Nothing to do; the line quotes a reference if you want to ask what happened.

WAIT_TIMEOUT

The wait ran out of its time limit while the deployment was still moving. The deployment was not cancelled and keeps running on the platform.

Next: nesly wait <deployment-id> Waits again; nesly inspect <deployment-id> shows where it is.

START_CRASHLOOP

The app's process kept exiting: it was restarted 2 times before it answered, so the deployment was failed instead of waiting out the ready timeout.

Next: nesly logs <deployment-id> Shows what the app printed before it exited; fix that, then deploy again.

TEMPORARY_STATIC_ONLY

A deploy without an account is for static sites only; this source is not one.

Next: nesly login Sign in, then nesly deploy builds a container.

TEMPORARY_QUOTA

This address already made the day's deploys without an account.

Next: nesly login An account deploys without that limit.

CLAIM_SIGN_IN

Claiming a temporary project needs a signed-in account.

Next: nesly login Then run the claim again; the token still works.

CLAIM_EXPIRED

The claim window closed: an unclaimed temporary project is deleted after an hour.

Next: nesly deploy --temporary Deploys the site again and prints a new claim token.

PROJECT_NOT_FOUND

No project with this name exists in the account the command works in.

Next: nesly project create <name> Creates it; nesly project list shows the projects there are, and nesly account ls the accounts.

APPROVAL_PENDING

Another action of yours is still waiting for your approval, and one waits at a time.

Next: nesly <the waiting command> --approval <approval-id> Follows that action until it is answered, or answer it on your phone or by e-mail; then repeat this one.

BUILD_CLONE_FAILED

The repository could not be fetched: it was not found, it is private, or the branch does not exist.

Next: nesly diagnose Names which of the three it was and, for a private repository, how to give the platform access.

BUILD_COMPILE_FAILED

The compiler refused the project's own source code.

Next: nesly diagnose Quotes the compiler's line; fix it in the code, then deploy again.

BUILD_DEPENDENCY_INSTALL

Installing the project's dependencies failed.

Next: nesly diagnose Shows the failing package and the command that fixes it.

BUILD_DOCKERFILE_INVALID

The project's Dockerfile could not be built as written.

Next: nesly diagnose Names the line the build stopped at.

BUILD_NO_START_COMMAND

The build finished but nothing tells the platform how to start the app.

Next: nesly diagnose Names the start command to set.

BUILD_OOM

The build was stopped because it ran out of memory.

Next: nesly diagnose Names the step that was running and the limit.

BUILD_OTHER

The build failed for a reason the platform could not tell more about.

Next: nesly diagnose Shows the build's own last lines.

BUILD_OUTPUT_NOT_STATIC

The build's output is not a static site, and the project is not set up to run as an app either.

Next: nesly diagnose Names what to set so the platform knows which it is.

BUILD_PROJECT_UNRECOGNISED

The platform could not tell what kind of project this directory holds.

Next: nesly diagnose Names the files it looked for.

BUILD_SCRIPT_FAILED

One of the project's own build scripts exited with an error.

Next: nesly diagnose Quotes the script's output; run it yourself to reproduce.

BUILD_SCRIPT_SILENT

A build script exited with an error and printed nothing the platform could read.

Next: nesly diagnose Tells you to run that script yourself to see its error.

BUILD_TIMEOUT

The build was stopped because it ran longer than the time limit.

Next: nesly diagnose Names the step that was running and the limit.

BUILD_TRANSIENT

The build failed because something it downloads from was unavailable for a moment.

Next: nesly diagnose Deploy again; if it repeats, the diagnosis names what was unreachable.

BUILD_UNSUPPORTED_FRAMEWORK

The project uses a framework or version the platform cannot build as it is.

Next: nesly diagnose Names what is supported and the change to make.

DEPENDENCY_MISSING

The app needs a package or module that is not installed.

Next: nesly diagnose Names the missing dependency and where to declare it.

IMAGE_PULL

The image could not be pulled when the app was started.

Next: nesly diagnose Shows the image reference that failed.

OUTPUT_MISSING

The build finished but the output directory the project names is not there.

Next: nesly diagnose Names the directory the build did write and the value to set.

PORT_MISMATCH

The app did not answer on the port the platform gave it.

Next: nesly diagnose Tells the app to listen on the port in the PORT variable.

RELEASE_COMMAND_FAILED

The project's release command (a migration, for example) exited with an error, so the new version did not go live.

Next: nesly diagnose Shows the command's output; the previous release still serves.

REQUIREMENT_UNMET

The project needs something it has not been given: a service, a variable or a file the platform checked for before building.

Next: nesly diagnose Names what is missing and the command that adds it.

ROLLOUT_NOT_READY

The app started but never answered, so the deployment was failed.

Next: nesly diagnose Shows what the app printed and which ports were tried.

ROLLOUT_OTHER

The new version could not be put into service for a reason the platform could not tell more about.

Next: nesly diagnose Shows the last lines of the app's output.

SCAN_REFUSED

The security scan found a vulnerability the project has not accepted, so the release was held back.

Next: nesly diagnose Lists the finding ids and the commands that accept or inspect them.

SCAN_UNAVAILABLE

The security scan did not finish, so the release was held back; the previous release still serves.

Next: nesly diagnose Deploy again.

START_APP_CRASH

The app crashed while starting.

Next: nesly diagnose Quotes the crash from the app's output.

START_APP_EXIT

The app's process ended on its own right after starting.

Next: nesly diagnose Shows what it printed before it exited.

START_DB_HARDCODED_HOST

The app connects to a database address that only exists on your machine.

Next: nesly diagnose Names the address and the platform's connection variable to read instead.

START_MISSING_ENV

The app needs an environment variable the project does not define.

Next: nesly diagnose Names the variable and the command that sets it.

START_OTHER

The app failed to start for a reason the platform could not tell more about.

Next: nesly diagnose Shows the last lines of the app's output.

STRANDED_BY_RESTART

The platform restarted while this deployment was being built, so it was stopped.

Next: nesly diagnose Deploy again.

DEPLOY_FAILED

The deployment did not go live; the platform could not name a more specific cause.

Next: nesly diagnose Shows what the platform does know about it; quote the reference to support.

PROJECT_TAKEN_OFFLINE

The platform took this project offline (abuse or a legal order): its addresses answer 403 and a new deploy is refused. The reason is shown with the refusal and on the project in the console.

Next: Appeal it: write to support from the contact page, quoting the project id. A person reads every appeal and either puts the project back or says what has to change; no command lifts it.

BUILD_SECRET_IN_OUTPUT

The build succeeded, but the value of one of this project's own environment variables appears in a file the build published, so anyone who loads the site can read it. This is a warning: nothing was blocked or changed.

Next: nesly env set <KEY>=<new-value> Rotate the value after removing it from the output; to silence a key that is meant to be public, list it in secrets_scan_omit under [build] in the config file.

RESCUE_AWAITING

No rule explains this failure yet; it is recorded and looked at.

Next: nesly diagnose Shows what the platform does know; quote the reference to support.