Troubleshooting

CLI

not logged in; run `vtx login`

The CLI has no token. Run vtx login. If you have signed in before, the file may be missing: see where it is kept.

this directory is not linked; run `vtx link` first

Run the command from the project folder, or run vtx link there. The link is the .vantrex/project.json file in the folder you run the command from.

The sign-in code never gets approved

Open the address in a browser where you are signed in to the dashboard, and check that the code matches the one in the terminal exactly. Codes expire after a short time; run vtx login again for a new one.

A limit was reached

The message names the limit (projects, concurrent builds, deployments per day, deployment size, domains). See Limits.

Builds

The deployment ends in Error

Open the deployment and read the build log from the bottom up; the last error is almost always the cause. Typical ones: a missing dependency in package.json, a build command that fails, or a variable your code needs at build time that is not set.

It builds on my machine but not on Vantrex

• Commit your lockfile. Installs use it, and without one the result can differ.
• Match the Node.js version in project settings to the one you use locally.
• Remember .env files are not uploaded. Add the variables in the dashboard.
• File names are case sensitive on the build machine. Logo.png and logo.png are different files.

Build output not found

Set the Output directory to the folder your build writes, for example dist, or choose the right framework preset. For a monorepo, set the root directory.

The build succeeded but the deployment failed to start

Server apps are started and must answer a request before they go live. The log shows the server's own output. Look for a missing environment variable, a crash on start, or code that listens on a fixed port instead of the one it is given.

$ vtx logs a1b2c3

Serving and domains

I still see the old version

Deployments are immutable, so check that you are looking at the one you expect: vtx ls shows which is on production. A change to an environment variable needs a new deployment. If you use caching for server routes, a cached page can stay for up to a minute; see Caching.

A domain stays on pending

The DNS record has not been found. Check it with:

$ nslookup -type=CNAME www.example.com

The name must match exactly, there should be no leftover records of another type on the same name, and changes can take a few minutes to spread. For a root domain, see Root domains.

A page says paused, no deployment or not found

• Paused: the project is paused in its settings. Resume it.
• No deployment: the project has no ready deployment for that address yet. Deploy, or promote one.
• Not found: no project uses that address. Check the spelling, and that the domain is added to the project.

Each of these pages shows a request ID. Quote it if you contact support.

GitHub

My repositories are not listed

Make sure you signed in with GitHub and installed the app on the account or organization that owns the repository. Only installations you can access are shown. Use Install on the New project page to add another account, or edit the app's repository access on GitHub.

A pull request has no preview

Pull requests from forks are never built. Push the branch to the repository itself, or merge the change and test it after.

Pushes do not deploy

Check the project is still linked to the repository, and that the app is still installed with access to it. The deployments list shows every build that started.

Getting help

Check system status first. If it is all green, write to hello@vantrex.cloud with the deployment ID, the project name and what you expected to happen. For a security problem, use the contact on the Security page.