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?

[Joakim Jakobsen]

Hi.

I've asked our developers about this. Hopefully they have some good advice on how to get around this.

Br,
Joakim

[XuLi]

Have you found the solution to solve the problem now? I am also facing the same issue. SSL connect error, and I downloaded the package .gz try to install it manually but it still failed, due to 

Error: Failed to install nrfutil-nrfutil-toolchain-manager-x86_64-pc-windows-msvc-0.14.1.tar

Caused by:
Package not found in registry

[Joakim Jakobsen]

Hi.

Apologize for the delay. Due to christmas vacation this has been delayed a bit.

I've created an internal ticket to our developers so that they can look at this. Most likely it's a proxy issue.

I'll get back with some more information.

Let me know if you have any more information to share, or if you manage to solve the issue.

Thanks,
Joakim

[Akshaya Balu]

Hi, I am also facing the same issue, any update regarding this

[Joakim Jakobsen]

Thanks.

I'll ask for an update.

Br,
Joakim

[zachwork]

Following up on this ticket as I am attempting to install the toolchain manager again on a new system at work and running into the same SSL certificate error. Has there been any update?

I'm using nRF Connect for Desktop v5.0.0.

Last time I was able to bypass this issue by using a network outside of work to install the toolchain manager but that isn't always an option.

It's important to note that I don't have this issue when installing any of the other tools such as the Power Profiler, or Bluetooth Low Energy, or Programmer. It only occurs with the toolchain manager and when installing toolchains.

[zachwork]

Actually do you know how the software under the hood is trying to pull the packages? Is it using curl or wget or something else entirely?

That might impact what additional environment variables I can set to let it know where to find the certificates.

This ticket might be OBE because the toolchain manager on my other system did mention that the IDE is not the recommended IDE and manager of the SDK toolchains. Should the IDE be used instead to download SDKs and toolchains instead of the toolchain manager?