This page details some common issues and their respective workarounds. For Anaconda installation or technical support options, visit our support offerings page.

403 error#


A 403 error 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:
        * 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:
  • 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)


  1. First, run the following to undo your configuration of Anaconda Professional:

    conda config --remove-key default_channels
  2. Next, install or upgrade the conda-token tool:

    conda install --freeze-installed conda-token
  3. 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.

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


After you have configured your .condarc for either Anaconda Professional or Package Security Manager (On-prem) , 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.


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

conda clean -i

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

Using Redis#


By default, Redis does not require a password. Not enabling a password requirement leaves your instance of Package Security Manager vulnerable.


Follow these steps to password protect your instance:

  1. In the installation directory, update config/nginx/conf.d/repo.conf to include the add_header directive somewhere in the server block:

    server {
        add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
  2. Create a directory called redis in the configs directory:

    mkdir -p config/redis
  3. Create a file called redis.conf inside config/redis with the following contents:

    requirepass "mypassword"
  4. Update the docker-compose.yml file of TE installation to mount this custom redis config:

        image: ${DOCKER_REGISTRY}redis-ubi:${VERSION}
        restart: always
          - ${BASE_INSTALL_DIR}/config/redis/redis.conf:/usr/local/etc/redis/redis.conf
        - /usr/local/etc/redis/redis.conf
    #  redis:
    #    image: ${DOCKER_REGISTRY}redis-ubi8:${VERSION}
    #    restart: always
    #    ports:
    #    - 6379:6379
    #    command:
    #    - /usr/local/bin/redis-server
    #    - --requirepass mypassword
    # If you use this alternative configuration, there's no need to create a config/redis/redis.conf file to mount in.
  5. Update REDIS_ADDR variable in .env file to include password:

  6. Restart docker-compose services so changes are picked up. You can do this using:

    docker compose up -d

Error message on initial login to Package Security Manager#

If you receive an error on your initial login to Package Security Manager and are unable to set your license, it is likely that you have forgotten to include a default user during your installation command, and your current user lacks the administrative permissions necessary to register your license.

To correct this issue:

  1. Log in to the Keycloak administrative console.

  2. Navigate to the dev realm.

  3. Select Users from the left-hand navigation.

  4. Create a user or select an existing user from the list to view their profile page.

  5. Select the Role Mapping tab.

  6. Click Assign role.

  7. Select the admin role, then click Assign.

  8. Return to Package Security Manager and log in as this admin user.

  9. Set your license.

Backup fails with exit status 1#

If you attempt to run the backup command and receive an error in dumping the repo database with exit status 1 returned by the command, complete the following procedure:

  1. Connect to your instance of Package Security Manager. If necessary, get help from your IT department with this step.

  2. Open your installation directory by running the following command:

    # Replace <INSTALLER_DIRECTORY> with the location of your file directory
  3. Open your docker-compose.yml file using your preferred file editor.

  4. Find the postgres: section of the file.

  5. Replace the following portion of the postgres: configurations:

      - "5432"

    With this:

      - "5432:5432"

    Here is an example of what your file should look like when you are finished:

  6. Retry the backup command.