> ## 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

export const Comments = ({children}) => {
  return <div class="my-4 px-5 py-4 overflow-hidden rounded-2xl flex gap-3 border border-zinc-500/20 bg-zinc-50/50 dark:border-zinc-500/30 dark:bg-zinc-500/10" data-callout-type="comments">
      <div class="w-4">
        <svg width="14" height="14" viewBox="0 0 640 640" fill="currentColor" xmlns="http://www.w3.org/2000/svg" class="w-5 h-5" aria-label="Comments">
            <path d="M320 112C434.9 112 528 205.1 528 320C528 434.9 434.9 528 320 528C205.1 528 112 434.9 112 320C112 205.1 205.1 112 320 112zM320 576C461.4 576 576 461.4 576 320C576 178.6 461.4 64 320 64C178.6 64 64 178.6 64 320C64 461.4 178.6 576 320 576zM280 400C266.7 400 256 410.7 256 424C256 437.3 266.7 448 280 448L360 448C373.3 448 384 437.3 384 424C384 410.7 373.3 400 360 400L352 400L352 312C352 298.7 341.3 288 328 288L280 288C266.7 288 256 298.7 256 312C256 325.3 266.7 336 280 336L304 336L304 400L280 400zM320 256C337.7 256 352 241.7 352 224C352 206.3 337.7 192 320 192C302.3 192 288 206.3 288 224C288 241.7 302.3 256 320 256z" />
        </svg>
      </div>
      <div class="text-sm prose min-w-0 w-full">
        {children}
      </div>
    </div>;
};

export const TroubleshootSolution = ({children}) => <>
    <hr className="my-3 w-full" />
    <details className="mt-3">
      <summary className="cursor-pointer font-semibold text-base mb-1">
        Solution
      </summary>
      <div className="mt-2 ml-4" data-component-part="step-content">
        {children}
      </div>
    </details>
  </>;

export const TroubleshootCause = ({children}) => <details className="mt-3 mb-2">
    <summary className="cursor-pointer font-semibold text-base mb-1">
      Cause
    </summary>
    <div className="mt-2 ml-4" data-component-part="step-content">
      {children}
    </div>
  </details>;

export const TroubleshootTitle = ({children}) => <>
    <p className="m-0 font-semibold text-xl leading-tight mb-2" role="heading" aria-level={3}>
      {children}
    </p>
    <hr className="my-3 w-full" />
  </>;

export const Troubleshoot = ({children}) => <div className="callout my-4 px-5 py-4 overflow-hidden rounded-2xl flex gap-3 border troubleshoot-admonition dark:troubleshoot-admonition" data-callout-type="troubleshoot">
    <div className="mt-0.5 w-4">
      <svg width="14" height="14" viewBox="0 0 640 640" fill="currentColor" className="w-4 h-4" aria-label="Troubleshoot">
        <path d="M541.4 162.6C549 155 561.7 156.9 565.5 166.9C572.3 184.6 576 203.9 576 224C576 312.4 504.4 384 416 384C398.5 384 381.6 381.2 365.8 376L178.9 562.9C150.8 591 105.2 591 77.1 562.9C49 534.8 49 489.2 77.1 461.1L264 274.2C258.8 258.4 256 241.6 256 224C256 135.6 327.6 64 416 64C436.1 64 455.4 67.7 473.1 74.5C483.1 78.3 484.9 91 477.4 98.6L388.7 187.3C385.7 190.3 384 194.4 384 198.6L384 240C384 248.8 391.2 256 400 256L441.4 256C445.6 256 449.7 254.3 452.7 251.3L541.4 162.6z" />
      </svg>
    </div>
    <div className="prose min-w-0 w-full">{children}</div>
  </div>;

This page includes common troubleshooting topics for Anaconda Platform (Cloud). If you are experiencing issues with conda, see the [Troubleshooting](/reference/troubleshooting) page for workarounds to common issues.

<Note>
  If you encounter an issue or bug that isn't covered on this page, you can ask for help in the [Anaconda community forums](https://forum.anaconda.com) or [open a support ticket](https://support.anaconda.com/hc/en-us/requests/new).
</Note>

<Troubleshoot>
  <TroubleshootTitle>
    ### Receiving a 403 Forbidden error from an Anaconda channel
  </TroubleshootTitle>

  <TroubleshootCause>
    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.<br /><br />

    The 403 error you are receiving may look like the following:

    ```sh wrap theme={null}
    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.
  </TroubleshootCause>

  <TroubleshootSolution>
    Run `anaconda token install` to issue and set a new token for yourself, then try again.<br /><br />

    If the **403 Forbidden** error persists, ensure you are not blocked by a Terms of Service violation by consulting our [Terms of Service error](https://www.anaconda.com/legal/terms/terms-of-service) page.<br /><br />

    If you believe you have been blocked in error, please [open a support ticket](https://support.anaconda.com/hc/en-us/requests/new?ticket_form_id=360000993773).
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Receiving a 429 error from conda
  </TroubleshootTitle>

  <TroubleshootCause>
    A 429 error message occurs when you need to register your conda client.
  </TroubleshootCause>

  <TroubleshootSolution>
    To clear the error and restore your connection, [register your conda client](/anaconda-platform/cloud/user/conda-registration).
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Environment creation failing due to strict policy filter
  </TroubleshootTitle>

  <TroubleshootCause>
    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.<br /><br />

    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.
  </TroubleshootCause>

  <TroubleshootSolution>
    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.<br /><br />

    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](/anaconda-platform/cloud/user/channels).<br /><br />

    With your quarantine channel created and added to your `.condarc` file, you can run the following command:

    ```sh theme={null}
    conda create --name <ENV_NAME> --channel <CHANNEL> --channel quarantine python=3.11 --dry-run
    ```

    <Comments>
      Replace \<ENV\_NAME> with a test environment name (this is not permanent).<br />
      Replace \<CHANNEL> with your channel name.
    </Comments>

    For example, if you are trying to test building an environment from the *snakes* channel, the command would be:

    ```sh Example command theme={null}
    conda create --name test_environment --channel snakes --channel quarantine python=3.11 --dry-run
    ```

    <Comments>
      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.
    </Comments>

    ```txt Example command return expandable theme={null}
    ## 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.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Error while loading conda entry point: conda-env-log
  </TroubleshootTitle>

  <TroubleshootCause>
    The `anaconda-env-log` package, used for environment logging, currently imports `is_conda_environment` from `conda.gateways.disk.test`. This was changed to `is_environment` in conda 26.3.0, so users with a conda version of 26.3.0 or later will see `Error while loading conda entry point: conda-env-log` after every conda command.

    This is a known issue and will be fixed in a subsequent release.
  </TroubleshootCause>

  <TroubleshootSolution>
    The workaround for this issue is to downgrade your conda version to 26.1.1.

    ```sh theme={null}
    conda install --name base conda=26.1.1
    ```

    To prevent conda from being upgraded again before the fix is released, you can also pin the version to your `base` environment's pinned file:

    1. Navigate to `<CONDA_INSTALL_FOLDER>/conda-meta`.

           <Note>
             Your conda install folder is typically in file locations like:

             * `C:\Users\<USERNAME>\anaconda3`
             * `~/anaconda3`
             * `/opt/anaconda3`

             You can also replace `anaconda3` with `miniconda3` in any of these paths.
           </Note>

    2. Locate the `pinned` file in your `conda-meta` folder or create a new file named `pinned` if it doesn't exist. The `pinned` file has no extension.

    3. Add `conda==26.1.1` to the pinned file.

    Once the fix is available, remove this pin and update conda.
  </TroubleshootSolution>
</Troubleshoot>