Conda: Channel is unavailable/missing or package itself is missing#

Cause

After you have configured your .condarc on either the Pro (legacy) or Business tier, in some cases you may be unable to install packages. You may receive an error message that the channel or package is unavailable or missing.

Solution

One potential fix for all of these is to run the following command:

conda clean --index-cache

This will clear the “index cache” and force conda to sync metadata from the repo server.

Receiving a 403 error from an Anaconda channel#

Tip

If you are working with the Anaconda-hosted conda-forge and are receiving a 403 error, see Receiving a 403 error from hosted conda-forge instead.

Cause

A 403 error is a generic HTTP error issued by a web server in the event the client is forbidden from accessing a resource. In other words, if you are receiving a 403 error, conda thinks that either the channel doesn’t exist or you do not have permission to use it.

The 403 error you are receiving might look like this:

Collecting package metadata (current_repodata.json): failed

UnavailableInvalidChannel: HTTP 403 FORBIDDEN for channel main <https://repo.anaconda.com/repo/main>

The channel is not accessible or is invalid.

You will need to adjust your conda configuration to proceed.
Use `conda config --show channels` to view your configuration's current state,
and use `conda config --show-sources` to view config file locations.

There are a few possible reasons for receiving this error:

  • You have misconfigured the channels in your .condarc file.

  • A firewall or other security device or system is preventing user access.

  • Access is blocked due to a potential terms of service violation.

Solution

First, double-check your channel configurations and verify that the address has been entered correctly.

If that fails, speak with your IT administrator to ensure your proxy or firewall is not blocking traffic to the repository channels.

If you are sure traffic is not being blocked and your issue persists, open a support ticket.

HTTP 000 CONNECTION FAILED#

Cause

This is generally caused by a proxy misconfiguration, which can be corrected by setting your proxy servers correctly. However, because some businesses do not have an easy method of providing their SSL cert, Anaconda recommends bypassing the SSL verification step if you encounter this error.

Solution

If you receive this error message, first run the following command:

conda config --set ssl_verify false

(Package Security Manager users) If necessary, install conda-token by running the following command:

conda install conda-token --channel https://repo.anaconda.cloud/repo/anaconda-tools --name base

(Package Security Manager users) Ensure the token verification step ignores SSL errors by running the following command:

# Replace <TOKEN> with your token
conda token set --no-ssl-verify <TOKEN>

You may see the following warning, though you can safely ignore it:

/Users/<USERNAME>/Applications/miniconda3/lib/python3.7/site-packages/urllib3/connectionpool.py:1020: InsecureRequestWarning: Unverified HTTPS request is being made to host 'repo.anaconda.cloud'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecureRequestWarning,
On this page