conda cannot reach the channel — network, proxy or certificate, not the package
An HTTP or SSL failure while fetching repodata.json means the request never got a valid answer. On institutional networks this is very often a proxy or TLS-inspecting firewall presenting its own certificate, which conda correctly refuses.
Test plain connectivity first (curl -I https://conda.anaconda.org/bioconda/). If your institution intercepts TLS, add its CA certificate to conda's trust store rather than disabling SSL verification — turning verification off makes every future install silently unverifiable.