Hi @JaredPilbeam2,
Sorry the accepted answer made no sense.
Sounds like you got a resolution though?!
Prior to the SSL error, did your initial clone attempts also fail while installing the package 'esri::jupyter_contrib_nbextensions-0.6.0-py_2'?, If so, do you have any insights on a root cause?
I had no SSL error's beyond the issues already outlined in this thread.
The "partial-clone-copy-and-paste-hack" solution that worked for me is ... a hack. I'd still be interested in understanding what the root cause is, though. I switch ArcGIS Pro licenses between two devices and have not upgraded Pro on my other device as I don't want the environment on that device to fall into the same state.
Reading through the log files myself and @JoelMcKechnie provided, it looks like there was a write failure while running a post-link script for that particular package. For some reason, it can't find the source file or directory it needs to write and/or doesn't have permissions to write it. This doesn't make sense to me: we're cloning a working environment, so if the source environment doesn't have the file, you'd think the source environment shouldn't work either. I ran the clone command as Administrator, so there should be no write permission problems. This write issue is why I went the copy-paste route following failed clone attempt.
The conda documentation says post-link scripts should be avoided whenever possible, so it's curious why they've been employed here. From the logs it appears it's primarily for validation purposes.
Maybe the way conda looks for packages is one avenue to explore as per this (old) Github Issues thread on post-link script errors? I can theoretically see how this could interfere with where conda looks for files during cloning. Could it be that where Anaconda, ESRI and jupyter are all at are not synced? Surely not...
I'm not overly familiar with how Anaconda as a package manager works, so lack the experience and context to guide and focus trouble shooting. I'm also conscious that my history of python environment and package installs - I'm not using virtual envs, they include jupyter and are not Anaconda - could be a source of conflict? Is that even possible?
Merry Christmas/Happy Holidays!