Troubleshooting
This page details some common issues and their respective workarounds. For Anaconda installation or technical support options, visit our support offerings page.
You can search this page for information using your browser’s search function: Ctrl+F (Windows)/Cmd+F (Mac).
Conda: Channel is unavailable/missing or package itself is missing
After you have configured your .condarc on either the Pro (legacy) or Business tier, in some cases you may be unable to install packages.
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
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.
A 403 errors is a generic Forbidden error issued by a web server in the event the client is forbidden from accessing a resource.
The 403 error you are receiving may look like the following:
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
.condarcfile. - A firewall or other security device or system is preventing user access.
- Access is blocked due to a potential terms of service violation.
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
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.
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 --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#ssl-warnings
InsecureRequestWarning,
Environment creation failing due to policy filter
Implementing strict policy filters with no exceptions can cause essential package dependencies to be filtered out of your repository. Without these packages, commands like conda create --name <ENV_NAME> python=3.11 will fail.
If you are attempting to create a new environment, but your build is failing due to package conflicts or unavailable packages, it’s likely due to your IT team’s strict policy filter. You can request that package exceptions can be added to a policy filter, but you’ll need to know which packages are causing problems first.
To perform this test, you’ll need a channel that has no policy filter applied to it. Create the channel in your organization and name it quarantine. Once created, add it to your .condarc file. For help adding a channel to your .condarc file, see Channels.
With your quarantine channel created and added to your .condarc file, you can run the following command:
# Replace <ENV_NAME> with a test environment name (this is not permanent)
# Replace <CHANNEL> with your channel name
conda create --name <ENV_NAME> --channel <CHANNEL> --channel quarantine python=3.11 --dry-run
If you have your channel alias set in your .condarc, you can use just the channel name with the --channel argument. If you do not, you can use the full channel URL with the --channel argument. You can copy the channel URL from your Channels page. For more information on setting your channel alias, see Using the .condarc conda config file.
For example, if you are trying to test building an environment from the snakes channel, the command would be:
conda create --name test_environment --channel snakes --channel quarantine python=3.11 --dry-run
The ordering of snakes and quarantine is essential. Conda will attempt to solve the environment in the order the channels are listed, so quarantine must be listed last.
Example command return:
## Package Plan ##
environment location: /Users/<USER>/opt/anaconda3/envs/test_env
added / updated specs:
- python=3.11
The following packages will be downloaded:
package | build
---------------------------|-----------------
bzip2-1.0.8 | h80987f9_5 129 KB snakes
ca-certificates-2023.12.12 | hca03da5_0 127 KB snakes
libffi-3.4.4 | hca03da5_0 120 KB snakes
ncurses-6.4 | h313beb8_0 884 KB quarantine
openssl-3.0.13 | h1a28f6b_0 5.0 MB quarantine
pip-23.3.1 | py311hca03da5_0 3.3 MB quarantine
python-3.11.8 | hb885b13_0 15.5 MB snakes
readline-8.2 | h1a28f6b_0 353 KB snakes
setuptools-68.2.2 | py311hca03da5_0 1.2 MB snakes
sqlite-3.41.2 | h80987f9_0 1.1 MB quarantine
tk-8.6.12 | hb8d0fd4_0 2.9 MB snakes
tzdata-2024a | h04d1e81_0 116 KB snakes
wheel-0.41.2 | py311hca03da5_0 142 KB quarantine
xz-5.4.6 | h80987f9_0 372 KB snakes
zlib-1.2.13 | h5a0b063_0 82 KB quarantine
------------------------------------------------------------
Total: 31.4 MB
The following NEW packages will be INSTALLED:
bzip2 snakes/osx-arm64::bzip2-1.0.8-h80987f9_5
ca-certificates snakes/osx-arm64::ca-certificates-2023.12.12-hca03da5_0
libffi snakes/osx-arm64::libffi-3.4.4-hca03da5_0
ncurses quarantine/osx-arm64::ncurses-6.4-h313beb8_0
openssl quarantine/osx-arm64::openssl-3.0.13-h1a28f6b_0
pip quarantine/osx-arm64::pip-23.3.1-py311hca03da5_0
python snakes/osx-arm64::python-3.11.8-hb885b13_0
readline snakes/osx-arm64::readline-8.2-h1a28f6b_0
setuptools snakes/osx-arm64::setuptools-68.2.2-py311hca03da5_0
sqlite quarantine/osx-arm64::sqlite-3.41.2-h80987f9_0
tk snakes/osx-arm64::tk-8.6.12-hb8d0fd4_0
tzdata snakes/noarch::tzdata-2024a-h04d1e81_0
wheel quarantine/osx-arm64::wheel-0.41.2-py311hca03da5_0
xz snakes/osx-arm64::xz-5.4.6-h80987f9_0
zlib quarantine/osx-arm64::zlib-1.2.13-h5a0b063_0
DryRunExit: Dry run. Exiting.
Packages that were retrieved from the quarantine channel are the packages that need to be considered for exceptions in the policy filter.
Receiving a 403 error from hosted conda-forge
If you have established a connection to the Anaconda-hosted conda-forge channel and have started receiving 403 errors when you were not receiving them initially, it is likely that you have recently reissued yourself a token. This issue stems from this newly issued token not having the permissions that were provided to the previous token.
Your 403 error might look like this:
Loading channels: failed
UnavailableInvalidChannel: HTTP 403 FORBIDDEN for channel conda-forge <https://repo.anaconda.cloud/repo/conda-forge>
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.
To provide permissions for the conda-forge channel to your newly issued token, navigate to your organization’s Token Access page and click Sync token.
Was this page helpful?