Skip to main content
This page details some common issues users might encounter when using conda with Anaconda Platform (Cloud) and their respective workarounds. For Anaconda installation or technical support options, visit our support offerings page. If you are experiencing issues with conda, see the Troubleshooting page for workarounds to common issues.

​
Receiving a 403 Forbidden error from an Anaconda channel

Cause
A 403 Forbidden error occurs when you attempt to access a resource you don’t have permissions for—such as a channel, package, or API endpoint.

The 403 error you are receiving may look like the following:
AnacondaAuthError: Received authentication error (403) when accessing <CHANNEL_URL>. If your token is invalid or expired, please re-install with anaconda token install.
This error is likely because your token is invalid or expired, but can also be because Anaconda is blocking your access because of a potential terms of service violation.
Solution
Run anaconda token install to issue and set a new token for yourself, then try again.

If the 403 Forbidden error persists, ensure you are not blocked by a Terms of Service violation by consulting our Terms of Service error page.

If you believe you have been blocked in error, please open a support ticket.

​
Receiving a 429 error from conda

Cause
A 429 error message occurs when you need to register your conda client.
Solution
To clear the error and restore your connection, register your conda client.

​
Environment creation failing due to strict policy filter

Cause
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 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 channel’s strict policy filter.
Solution
If you’re an organization member, you can request that your organization’s administrator add package exceptions to your channel’s 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:
conda create --name <ENV_NAME> --channel <CHANNEL> --channel quarantine python=3.11 --dry-run
Replace <ENV_NAME> with a test environment name (this is not permanent).
Replace <CHANNEL> with your channel name.
For example, if you are trying to test building an environment from the snakes channel, the command would be:
Example command
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 retrieved from the quarantine channel are the packages that need to be considered for exceptions in the policy filter.