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/Cmd + F).
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: The channel is not accessible or is invalid.
channel name: pkgs/main
channel url: https://repo.anaconda.com/pkgs/main
error code: 403
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 several reasons a 403 error could be received:
There are a few possible reasons for receiving this error:
The user has misconfigured their channels in their configuration (for example, the secure location where the token is stored was accidentally deleted (most common)
A firewall or other security device or system is preventing user access (second most common)
We are blocking their access because of a potential terms of service violation (third most common)
First, run the following to undo your configuration:
conda config --remove-key default_channels
When conda is first installed, the default channels it uses to install packages are
https://repo.anaconda.com/r(as well as
https://repo.anaconda.com/msys2for Windows operating systems).
If your other channels require a token, install or upgrade the
conda-tokentool by running the following command:
conda install --freeze-installed conda-token
Lastly, re-apply the token and configuration settings:
# Replace <TOKEN> with your token conda token set <TOKEN>
If this doesn’t resolve the issue, Anaconda recommends consulting our Terms of Service error page.
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
(Anaconda Business users) If necessary, install
conda-token by running the following command:
conda install conda-token -n base
(Anaconda Business 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/<USER_NAME>/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