My institution disallows access to Anaconda repository servers (https://conda.anaconda.org) due to licensing fees. To work around this, I installed Miniforge and configured .condarc
to use only the conda-forge
and bioconda
channels (e.g., following instructions here). This setup previously worked fine, but now, with a fresh installation of Miniforge, I’m encountering issues where Mamba/Conda still attempt to access Anaconda’s servers, causing installation failures.
Steps taken and error encountered
- Installed Miniforge following standard instructions.
- Configured
.condarc
to use onlyconda-forge
andbioconda
:channels: - conda-forge - bioconda channel_priority: flexible
- Attempted to create an environment:
mamba create -n env_protocol -c bioconda -c conda-forge bc bowtie2 fastqc ipython parallel pbzip2 pigz r-argparse r-plotly r-ggsci rename samtools
- Received the following error, indicating an attempt to access an Anaconda repo:
Download error (35) SSL connect error [https://conda.anaconda.org/conda-forge/noarch/repodata.json.zst] Recv failure: Connection reset by peer
Despite explicitly setting up .condarc
, Conda/Mamba still defaults to https://conda.anaconda.org, which is blocked.
Request for assistance
- Are there specific settings needed to prevent Conda/Mamba from defaulting to Anaconda's servers?
- Are there alternative non-Anaconda mirrors that can be used in there place?
- Is there anything I'm missing here, or anything else you recommend?
Can post detailed command logs if needed—just let me know. Any help will be greatly appreciated.
Have you checked
conda config --show-sources
as suggested in the post you linked?Thanks, yes:
Looks like changing this may be worth investigating.
to your
.condarc
.With
channel_priority: strict
orchannel_priority: flexible
, I continue to encounter the same issue: