# Troubleshooting

> Common vpctl errors and resolutions

If a vpctl command fails, rerun the command with `--log-level debug` to view detailed error output. Common issues are listed below.

## "No credentials found for registry"

Run `vpctl configure` to set up your registry credentials. For more information, refer [Install vpctl](/cloud/virtual-private-cloud/vpctl/install.md#configure-registry-credentials).

## "Manifest file not found"

Ensure that `manifest.yaml` exists in the current directory or a parent directory. You can also use `--manifest <path>` to specify the path.

## "Secrets file does not exist"

Run `vpctl secret generate` to create the secrets file. For more information, refer [vpctl secret](/cloud/virtual-private-cloud/vpctl/commands/secret.md).

## "vpctl version X is older than the minimum required version Y"

Your vpctl binary is older than the version required by the release package you pulled. Upgrade vpctl to at least the version shown in the error message. To bypass this check temporarily, use `--skip-version-check`.

## "Failed to pull artifact"

* Verify that your registry credentials are correct.
* Check that the version exists in the registry.
* Ensure that you can access the registry over the network.

## Getting more detail

Append `--log-level debug` to all commands to view a detailed log output.