> ## Documentation Index
> Fetch the complete documentation index at: https://anaconda.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

Troubleshoot

### `AnacondaLoginRequired`

***

<details>
  <summary>Cause</summary>

  The command requires an authenticated session, but no valid login was detected. `anaconda-repo-cli` relies on `anaconda-auth` for authentication, so this error means the auth plugin has no stored credentials for the configured site.
</details>

***

<details>
  <summary>Solution</summary>

  Log in using the `anaconda-auth` CLI:

  ```sh theme={null}
  anaconda login
  ```

  If you have multiple sites configured, specify which one to authenticate against:

  ```sh theme={null}
  anaconda --at <SITE> login
  ```
</details>

Troubleshoot

### `Unauthorized`

***

<details>
  <summary>Cause</summary>

  The server recognized your credentials but denied permission for the requested operation. This can occur when your user account or token does not have the required role or scope to access the target resource, such as a private channel or an admin-only endpoint.
</details>

***

<details>
  <summary>Solution</summary>

  Verify that your token has the required permissions by checking your auth tokens:

  ```sh theme={null}
  anaconda repo auth --list
  ```

  If permissions are insufficient, request access from your organization administrator or create a new token with the appropriate scopes.
</details>

Troubleshoot

### `NotFound`

***

<details>
  <summary>Cause</summary>

  The requested resource does not exist on the server. This typically means the channel name, package name, or artifact identifier in the command does not match any resource on the configured site. It can also occur when targeting the wrong site in a multi-site configuration.
</details>

***

<details>
  <summary>Solution</summary>

  Double-check the resource name in your command. You can list available channels to confirm the name:

  ```sh theme={null}
  anaconda repo channel --list
  ```

  If you have multiple sites configured, make sure you are targeting the correct one with the `--site` flag:

  ```sh theme={null}
  anaconda repo channel --list --site <SITE>
  ```
</details>

Troubleshoot

### `NoDefaultUrl`

***

<details>
  <summary>Cause</summary>

  No repository URL has been configured. `anaconda-repo-cli` needs to know which Package Security Manager (On-prem) instance to connect to, and no `default_site` or site configuration was found in `~/.anaconda/config.toml`.
</details>

***

<details>
  <summary>Solution</summary>

  Add a site configuration using the `anaconda sites add` command:

  ```sh theme={null}
  anaconda sites add https://your-platform-domain.example.com
  ```

  Alternatively, set `default_site` manually in `~/.anaconda/config.toml`. For a full walkthrough, see [Getting started with anaconda-repo-cli](https://anaconda.com/docs/cli-reference/anaconda-repo-cli/getting-started.md).
</details>

Troubleshoot

### `ChannelFrozen`

***

<details>
  <summary>Cause</summary>

  The target channel has been frozen, which prevents any modifications such as uploading, copying, moving, or removing packages. Freezing a channel is an intentional action to protect its contents from changes.
</details>

***

<details>
  <summary>Solution</summary>

  If you need to modify the channel, unfreeze it first:

  ```sh theme={null}
  anaconda repo channel --unfreeze <CHANNEL>
  ```

  If the channel was frozen intentionally and should not be modified, use a different channel for your operation.
</details>

Troubleshoot

### SSL verification error

***

<details>
  <summary>Cause</summary>

  This error often occurs when an organization uses internally generated certificates signed by a private Certificate Authority. Internal CAs aren't included in the standard system trust store, so SSL verification fails when the client cannot validate the server's certificate.
</details>

***

<details>
  <summary>Solution</summary>

  Run the following command to disable SSL certificate check:

  ```sh theme={null}
  conda repo config --set ssl_verify False
  ```

  Verify the above command worked:

  ```sh theme={null}
  conda repo config --show
  ```
</details>