Skip to content
LogoLogo

Troubleshooting

Common issues and how to resolve them.

"you're not signed in"

Cause: Your session has expired or you haven't logged in.

createos login

For CI environments:

createos login --token

"no project linked to this directory"

Cause: No .createos.json file found in the current directory or any parent directory.

createos init

Or specify the project explicitly:

createos deploy --project <your-project-id>

To find your project ID:

createos projects list

"command not found: createos"

Cause: The CLI binary is not in your PATH.

If installed via Homebrew

brew link createos

If installed via curl

The installer places the binary in /usr/local/bin. Verify:

ls -la /usr/local/bin/createos

If missing, reinstall:

curl -sfL https://raw.githubusercontent.com/NodeOps-app/createos-cli/main/install.sh | sh -

Deploy hangs or times out

Cause: Build is taking longer than expected, or there's a network issue.

  1. Check build logs:
createos deployments build-logs
  1. If the deployment is stuck, cancel and retry:
createos deployments cancel
createos deploy
  1. Enable debug mode to see HTTP requests:
createos --debug deploy

Interactive prompts not working

Cause: You're running in a non-TTY environment (CI, pipe, script).

Use explicit flags instead:

# Instead of interactive selection
createos env list --project <id> --environment <id>
 
# Skip confirmations
createos domains delete --project <id> --domain <id> --force

"environment not found"

Cause: The environment ID in .createos.json no longer exists, or you have multiple environments and need to specify one.

# List available environments
createos environments list
 
# Use a specific environment
createos env list --environment <env-id>
 
# Re-link with correct environment
createos init --project <project-id>

Updating the CLI

If you're on an old version and something isn't working:

createos upgrade

Or via Homebrew:

brew upgrade createos

Check your current version:

createos version

Debug mode

For any issue, run the command with --debug to see full HTTP request/response details:

createos --debug status

Tokens are automatically masked in debug output.

Getting help