SSL Proxy Errors When Installing Toolchain Manager

[zachwork]

I'm trying to install the toolchain manager on a new work computer and I'm running into issues that I think are related to my work's proxy.

I've tried following the steps from this QA but haven't had any luck.

How to use nRF Connect v2.0 behind corporate SSL proxy? - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

I've set the correct cafile path for yarn and I've tried disabling the "strict-ssl" setting all together and no luck.

Here is a copy of the error message that I get regardless of what settings I change.

I'm able to copy and paste that link into a browser and download the tar file without issue so I'm not sure why the nRF connect desktop isn't able to grab it. I have certificates registered with my OS, browser, nodejs, yarn, etc.

Anyone have suggestions on how to resolve the error?

[zachwork]

I know this is a very old thread but I wanted to ask for some more information to help fix the problem on my side. The Windows version of the tools seems to be returning a `curl/wget` error. Does the toolchain or suite of Nordic applications install their own version of these tools in their local environment?

My work has instructions for updating command line applications to work with our Proxy but I'm not sure where the tools are located in the install to make sure they are configured correctly.

[zachwork]

Follow on, is there a way to get the toolchain or nrf connect application to use the system versions of the tools instead of the versions that are installed alongside the toolchains?