Getting Started 'Conda Workflow' tutorial - CondaSSLError

Getting Started
1

Unable to continue Conda Workflow tutorial due to an error when attempting to install packages as shown. I’ve also CondaSSLError: OpenSSL appears to be unavailable on this machine.

Will this be fixed in the near term?

(test1) C:\Users\name>conda install jupyterlab dask pandas hvplot
Collecting package metadata (current_repodata.json): failed

CondaSSLError: OpenSSL appears to be unavailable on this machine. OpenSSL is required to
download and install packages.

Exception: HTTPSConnectionPool(host=‘repo.anaconda.com’, port=443): Max retries exceeded with url: /pkgs/main/win-64/current_repodata.json (Caused by SSLError(“Can’t connect to HTTPS URL because the SSL module is not available.”))

2

Hello Amy_DMV.

A solution is given on the following site that has worked for several people reporting the same issue:

|> This is due to .dll error

go to location where you’ve install anaconda anaconda3>Library>bin. search and copy following dll files

libcrypto-1_1-x64.dll libssl-1_1-x64.dll

and paste to anaconda3>DLLs.

then restart your pc.

issue will get resolved.

Great! Works for me|

Have you tried this solution?

Kim
Anaconda

3

Hi Kim - YES! this worked very nicely. And to Mahesh for the winning solution! Thank you, thank you, thank you!!

4

I copied the files still getting this error: Collecting package metadata (current_repodata.json): failed

CondaSSLError: OpenSSL appears to be unavailable on this machine. OpenSSL is required to
download and install packages.

Exception: HTTPSConnectionPool(host=‘repo.anaconda.com’, port=443): Max retries exceeded with url: /pkgs/main/win-64/current_repodata.json (Caused by SSLError(“Can’t connect to HTTPS URL because the SSL module is not available.”))

5

This isn’t something that’s expected to be “fixed soon” on Conda’s side — it’s almost always a local environment issue on Windows.

CondaSSLError: OpenSSL appears to be unavailable means Conda can’t load the OpenSSL libraries it depends on to make HTTPS requests. In practice, this usually comes down to one of these issues:

Conda is being run from plain CMD/PowerShell instead of Anaconda/Miniconda Prompt
A conflicting Python installation is breaking PATH
The Conda install is corrupted or incomplete
The OpenSSL DLLs in Library\bin aren’t being picked up

The most reliable fix is typically: use the proper Conda prompt first, then clean up PATH conflicts. If that doesn’t resolve it, a clean reinstall of Miniconda usually fixes the problem immediately.

So no, it’s not really a “tutorial bug” or something you need to wait on — it’s a local setup issue.

If you’re hitting repeated environment issues like this while trying to build workflows or integrations, it can sometimes be easier to offload parts of the automation to managed cloud tooling instead of relying on local Python environments. For example, you can connect services directly using integrate clio without dealing with Conda or dependency setup at all.