Cause
.condarc
on either the Pro (legacy) or Business tier, in some cases you may be unable to install packages.Solution
conda-forge
and are receiving a 403 error, see Receiving a 403 error from hosted conda-forge instead.Cause
.condarc
file.Solution
Cause
Solution
conda-token
by running the following command:Cause
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.Solution
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:.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.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.quarantine
channel are the packages that need to be considered for exceptions in the policy filter.conda-forge
Cause
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:Solution
conda-forge
channel to your newly issued token, navigate to your organization’s Token Access page and click Sync token.