Conda Proxy Error Handling: Better error Message on 403 from Proxy #12111
Labels
backlog
issue has been triaged but has not been earmarked for any upcoming release
good first issue
great for new contributors, code change is envisioned to be trivial/relatively straight-forward
locked
[bot] locked due to inactivity
source::community
catch-all for issues filed by community members
stale::closed
[bot] closed after being marked as stale
stale
[bot] marked as stale due to inactivity
type::bug
describes erroneous operation, use severity::* to classify the type
Checklist
What happened?
I used a valid proxy setting in my environment. However, I got the error message from Anaconda:
I did not use a .condarc or .netrc file; proxy setting was done via environment variables.
After a lot of search, I found that the issue was that the proxy server returned a 403 error not because the username/password was wrong, but because conda.anaconda.org was not on the proxy's allowlist.
I think the error message is misleading, because to me it seemed like the error was the local configuration. I was not aware that conda had even tried to fetch data via the proxy, but I thought it has failed just reading the configuration. I think changing the error message to
Conda cannot proceed because it encountered a 403 Error from your proxy when fetching [URL]
would be much more helpful in debugging such situations thanConda cannot proceed due to an error in your proxy configuration
Conda Info
Conda Config
No response
Conda list
Additional Context
The error occurs when building an mlflow docker container for an mlflow model.
The whole thing is running in an extremely restricted internal network, where we are only allowed to access internet resources that are explicitly allowed. It would have been helpful to have a list of servers that need to be allowlisted for conda to work.
The text was updated successfully, but these errors were encountered: