DeployxaDocs Portal
CLI v1.0.4
Errors Glossary & FAQ
Support

Errors glossary and FAQ

Quick answers to common questions. For step-by-step fixes, see Troubleshooting.

Error glossary

ErrorMeaning
❌ [CLI Error] …The API returned an error; the message follows. The CLI exits with code 1.
Session expired or authentication failedHTTP 401: no token, an expired token, or a token without the Bearer prefix.
Rate limit exceededHTTP 429: too many requests in a short time.
Cloud control plane connection failedThe API host could not be resolved or reached.
Project must be linkedNo .deployxa/config.json in the current folder.
Deployment failed!The build or rollout failed; run the deployxa logs command it prints.
PROJECT_NAME_TAKENProject names are unique within an organization.
out of memory / OOMThe process exceeded its memory limit.
framework detection failedChoose the framework manually or add a Dockerfile.
Unknown commandThe command does not exist in your CLI version. Run deployxa help.

Deployment statuses

StatusMeaning
QUEUEDWaiting for a build slot (see concurrent builds per plan).
BUILDINGBuilding the container image.
DEPLOYINGStarting the new release and health-checking it.
SUCCESSLive. The URL serves this release.
FAILEDBuild or rollout failed. Read the log with deployxa logs <id>; roll back if production is affected.

Frequently asked questions

Is there a free plan?

Yes, with no time limit and no credit card: 3 projects, shared CPU with 512 MB RAM, 1 GB storage, custom domains with HTTPS and a free *.deployxa.online address.

Why is my free app slow on the first request?

Free apps go idle after 20 minutes without requests. The next request wakes the container, which adds a short cold start.

Which frameworks are supported?

Deployxa detects common stacks, including Next.js, React, Vue, Nuxt, SvelteKit, Angular, Astro, Express, NestJS, Laravel, Django, Flask, FastAPI, Go and static sites. Anything else can ship with a Dockerfile.

Do I need Docker installed to deploy?

No. Images are built on Deployxa. Docker is only needed locally for testing a Dockerfile or for deployxa shell on your own server.

Is there a deployxa --prod flag?

No. deployxa deploy deploys the linked project. Preview deployments come from pull requests (Pro and higher) and deployxa promote moves the latest successful preview to production.

Can I get a shell inside my running app?

On your own server, yes: SSH in and use deployxa shell there. On Deployxa Cloud, use deployxa logs --live, deployxa inspect and deployxa metrics instead.

How do I deploy from CI?

Create a token with deployxa token create, store it as a secret, then run deployxa login --token "$DEPLOYXA_TOKEN" and deployxa deploy <projectId> .. See Authentication.

Are SSL certificates included?

Yes. Let's Encrypt certificates are issued, validated and renewed automatically for every custom domain, on every plan.

Does the CLI respect .gitignore or a .deployxaignore file?

No. CLI 1.0.4 uploads the whole folder. Deploy from a clean folder or from Git.

How do I roll back?

deployxa rollback previous, or the rollback button on a deployment in the dashboard. It reuses the earlier build, so it does not rebuild.

Can I connect my own server?

Yes. Connect any Linux server reachable over SSH and Deployxa installs Docker and Nginx on it. See VPS & your own servers.

Where are my CLI credentials stored?

In ~/.deployxa/auth.json, encrypted with a key derived from your machine's hostname and user. deployxa logout deletes it.

Can AI agents manage my projects?

Yes, through the Deployxa MCP server, with the same permissions as your account.

Is there an SLA?

Business includes an SLA. Enterprise adds custom SLAs. Other plans do not include an SLA.

What happens if I run out of credits?

The account enters a grace period. If it ends without a top-up, workloads are stopped. Check with deployxa credits; see Billing.