I'm trying to create new environment using ArcPro 2.4 and also trying using command prompt but it shows error and that is.
Apologies.
Flag for you, just in case it had nothing to do with the recent My Esri notice.
I tried both approach using ArcGIS Pro and conda. They both show same error as described by Marc Graham
Even I tried to clone and also tried to create new environment
Understanding Conda | ArcGIS for Developers
Here under
ArcPro
I was also facing the same issue while doing it from Pro. Instead i completed this cloning by manually copy-past of arcgispro-py3 environment folder to clone folder path and then activated that cloned environment to install further modules. If there is some other technique, please let me know as this is just a solution work around. I don't think this is the right way to do it but it worked.
I tried this also but it has same issue while trying to install pkg
conda install -c pytorch -c fastai fastai=1.0.39 pytorch=1.0.0 torchvision
https://repo.continuum.io/pkgs/main/win-64/ There is a package list
https://anaconda.org/anaconda/repo And here
but
https://repo.anaconda.io/pkgs/main/win-64/
repo.anaconda.io’s server IP address could not be found.
Try:
How it can be resolved.
Kory Kramer (trying again)
Will hopefully put you in touch with the team,
You can have a try with
Esri Support | ArcGIS Technical Support and under Support Options, ... Request a Case
Lots of views to this post.
No one else is weighing in, so short of you installing what you need from one of the other channels, it is time for me to go shovel snow again.
Good luck
Technical Support would be a good option here. I did a quick search in their case database and it appears that while this error has been reported before, it sounds like it may have been network related (we were not able to reproduce such an error in-house).
Here is an explanation I found.
These are difficult to track down because they’re a) usually pretty transient and b) communicating between two environments we don’t control (the users and the Anaconda.org service). Anaconda.org is hosted on S3, and typically has decent reliability. There are a few potential causes, but I can’t point to one thing being the single cause. I think it’d be helpful working with a customer who has a persistent error and can reproduce it in that environment, and working backward from there. There are multiple possible failure points:
If that removes the issue, then the SSL verification is failing on their machine.
Hope that helps. Good luck!
.