SSL Proxy Errors When Installing Toolchain Manager

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?

Parents Reply Children
  • The root cause of the "access denied" error was the IT backup software attempting to back up the files while west was trying to move or delete them which caused the permission issue. Temporarily disabling the backup software allowed for a clean installation.

    Summary of answers:

    • Follow your company's internal documentation on adding the proxy certificates and settings to the host OS.
      • Try adding the custom certificates to the mingw64 folder "mingw64/ssl/certs" and launching from the "git-bash" application for that toolchain
    • Attempt to use a non-proxy controlled network when downloading/installing the repo
    • Make sure the folder the toolchain and SDKs are installing to are under your control and you have full permissions
    • Make sure antivirus or backup software is not actively uploading or inspecting the installation directory while west is installing
    • If VSCode or the GUI struggles to download the toolchain-manager attempt to use the nrfutil to install them.
Related